Vista boot error after KB943899 update install

[d.chatten]

I installed the KB943899 update through Windows update and on rebooting i am being told that Windows wasn't shutdown properly (strange), so i chose to boot Windows normaly but then i get told that a file is missing ir corrupt, the file is C:\Windows\system32\drivers\volsnap.sys, no matter what i do i can't get the system to boot.

My only option was to restore my system with a backup i created using Acronis True Image.

Has anyone else had any issues after installing the KB943899 update for Vista?

Thanks!

 

[d.chatten]

I've got the same problem. Installed the automatic updates last night and now my system won't boot into windows. I get the windows loading bar then the screen just goes black

Greeeeat update

I found that "GameJackal 3.0.0.0 beta2" was causing the issue, if i uninstall GameJackal the update would install without issue, also, i found that if i disable my CD/DVD ROM drives in "Device Manager" the update would also install without issue.

 

[d.chatten]

i take it you have tried booting into safe mode or last know good?


this might help
http://vistasupport.mvps.org/windows_vista_repair_options.htm

I never use safe mode unless i have to, this is because it only takes 3-4 minutes to restore my system from an ATI backup image.

"My only option was to restore my system with a backup i created using Acronis True Image."

You could have used a "system restore point" if you could notget into safe mode to do this, you can boot from the installation DVD and perform one there, ny slectin recovery.

This is of course tha tyou have not turned to option off

As said above, i can restore my system in 3-4 minutes from an ATI backup image and the system is exactly as it was before the error, not pot luck like when you use system restore.

 

[d.chatten]

i cant find this update in the ones installed on my vista machine yesterday, nor does a google or a search on support.microsoft.com for KB942899 bring back any valid windows patches..

This is because the update is KB943899, and not KB942899, and also the fact that i had put a two where there should have been a three in the first line of my of my first post, sorry about that, all sorted now.