Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC Insider

magilla said:

There is something wrong with programming/code. Too many of us are having problems with page fault in nonpaged area BSOD and pointing to volsnap.sys. I am really pi**ed about this. I have spent last night and most of today getting one computer up and running and it isn't happening. I am now doing a clean, total install. I have also discovered that - once again - the wonderful world of MS has downloaded a video driver that will not allow my computer to come out of sleep mode -- this is on a working computer (HA HA)
Well, so much for the clean install on my other computer. It just BSOD'd with our favorite term!

Dude, relax, did you even know what insiders build is? you don't suppose to use this builds in "production" PCs, insiders builds is only for testers, this builds is only for people who want to test early builds of windows, and your PC may die in the process, if you don't like or even understand the danger, why are you using this builds?

If theres an error( like this ), wait for the patch or trick and move on, if you don't approve that, go to public builds

HippsieGypsie said:

Hi there, PaulLemonidis and Chazzo125. Welcome to Windows TenForums.

Please read back and you’ll see the fix. The volsnap.sys file was either corrupt or badly reworked/rewritten. Simply disconnect any interior secondary drive(s), let it update, replace the file with an older one, reconnect the drive(s), and you'll be good to go.

Thanks. Finally got there but not in quite the way you suggested but similar. There is defintely a problem with the volsnap.sys file in C:\windows\system32\drivers. Hopefully this may help others.

I extracted the ISO I have and put the entire contents in a folder called 17017 directly off the root of my SSD. I then unplugged my two external drives that I use for backup purposes. Now here is the intereting part. Those drives are both conencted using Esata so to the OS they appear as two extra internal SATA drives. Upon doing so I could upgrade fine. However, what I forgot was the second internal SATA HDD but the upgrade went fine nonetheless. However, upon plugging either of those two drives back in the machine refused to boot correctly and now presented me with a GSOD (was blue before). The error clearly stated volsnp.sys was the problem. I thus unplugged the drives and was able to boot up fine again. Upon doing so I copied across a copy of volsnap.sys from C:\windows.old\windows\system\drivers, overwriting the current one in C:\windows\system32\drivers. I am now able to plug those drives in and boot 17017 sucessfully. I think that is pretty positive confirmation there is a problem with volsnap.sys in 17017 and certain hardware configurations. Once again thanks for your help.

After numerous failed upgrades due to 0xC1900101, just wanted to report that if you're still on 17004 or earlier, you can also create an ISO of 17017, extract the contents to your harddrive and then mount install.wim using DISM and replace the volsnap.sys in the mounted wim's Windows\system32\drivers folder with the volsnap.sys from your current Window's folder. Then just run setup.exe from your extracted ISO folder. That finally worked for me.

Is anyone here using MPC-HC + madVR? I'm having some issues with it since I updated to this build.

pigpenz said:

On skippy always get error cx1900101and volsnap.sys error
on fast, installed fine didn't even know it had installed on other machine over weekend

Yeah, it looks like I did myself a huge favor by avoiding Skippy, and sticking with Active development!!!!