New
#90
Here also error 0xc1900101 fast Build 17025, but not in build 17017
So it can be false.
https://www.google.nl/search?q=0xc19...or+Build+17025
I will do a extended Disk Cleanup in 17017 and after reboot try 17025 again.
ok installed fine on three machines,
was able to add a second usb WD Mybook and didn't get any ?SOD with volsnap.sys error
so far.
I didn't have any problems with the volsnap.sys file until I tried to do the update. I even unplugged all USB devices except for the mouse. Most of my attempts green screened around 80% of preparing to install. I made the ISO and as soon as I'm done making the wim file I'm going to hit restart and see what happens.
In Donna's post re Volsnap she also mentioned that
It occurs when system restore is active, try turning Off and deleting any restore points.
Roy
Once I saw this thread, I read most of it, and then tried to update. But every time I hit update, it told me that my system was already updated. Right when I started to get annoyed, I looked down and saw it was already on 17025. Lol. Sooooooo, I guess I can say that it was a seamless upgrade for me, as I didn't even know it had already upgraded.
But everything is still running very well, and I haven't found any problems. It's very fast, and everything snaps up as quick as I click it. I test everything I see others complaining about, and don't have any of those problems so far. I even turned my sys restore back on for os drive, and no problems at all.
I don't know what was causing my problem with volsnap.sys. I unplugged all USB devices except my mouse and I stopped using system restore a few builds back. There was something in this build that trying to access volsnap.sys. All I know is that I had to fix the problem so I could install the fix for the problem. :)
17025 is finally installed on my desktop. Seems to be running smooth. Now I need to plug in all my USB devices.