Win 7 x64

I use vbootctl.exe to mount .vmdk (I find it way better then Vmware own solution) - so no vbootldr involved

I got caught by the 12F BSOD by version 1.0 expiry date on the 15th Feb

So today I upgraded the driver (twice, by hand & vbootctl update current)

Each time on reboot I get BSOD in vbootstor.sys address: FFFFF88001159451 base at FFFFF88001158000 DateStream 4d6213bf

The bold entries are each time different, DateStream is each time identical

sebus

Un-install / re-installed vbootstor.sys with devcon

Makes no difference, same BSoD

sebus

Sorry for the problem, we made a mistake to bsod host system, it was supposed to do that only for vhd booted systems. Future version will never bsod hosts, we fixed that.

Can you disable vbootstor service? Reboot, then run:

Vbootctl update current

For vmdk, we did fix a bug yesterday, nit sure if to do with this error

admin wrote:
Sorry for the problem, we made a mistake to bsod host system, it was supposed to do that only for vhd booted systems. Future version will never bsod hosts, we fixed that.

Can you disable vbootstor service? Reboot, then run:

Vbootctl update current

Nobody really reads any more!?

I did specifically state in first post:

So today I upgraded the driver (twice, by hand & vbootctl update current)

It is already latest 1.1 version & YES it does BSoD the host ONLY (I do not use any VM on this host)

sebus

I did read your post, I was refering to the expiry BSOD, which should not occur from v1.1, was a mistake on v1.0.

Then I tested on several amd64 machines here, we couldn't get any BSOD, so can't reproduce.

Can you check c:\windows\system32\drivers\vbootstor.sys? Is that indeed the newest version?