Forum Discussion
MicrosoftWindows 10 Insider Preview Build 17025 for PC is now available! Let's get some RS4 on!
MicrosoftGood news! This was fixed in the 17025 build. The only external build that affected Fast users was 17017 (did not affect the 17025 build).
The bug is random as to when it hits the users, but they have to be on 17017 for it to hit.
Workaround here:
https://www.hanselman.com/blog/RecoveringFromTheWindows10InsidersFast17017VolsnapsysRebootGSODBSOD.aspx
Michelle,
Fantastic! Swift fix indeed! Yes, I had plenty of opportunity to send feedback to the Feedback Hub; every time this happened, notifications asked me to fill out why the computer reset - and I filled it out almost every time.
Thank you,
Rob Milliken
Michelle,
A similar technique worked for me and I am writing on a machine without trepidation that it'll be reset at any time. I did try something similar where I took my non-insider Windows 10 laptop volsnap.sys and overwrote my trouble insider machine. However, the tip to get it from windows.old solved it for me with the volsnap.sys dating from some time in September. There is more than one way to do this (why is it my Windows 10 DVD is always the one that ends up scratched/unusable - the old telephone book slogan comes to mind..) - myself I got ownership rights to the file and did a simple copy with Windows Explorer (the ownership rights is the big thing, other readers can find how to do this on the net - if troubles, I'll find the link again). Being able to copy over without having to get out of Windows 10 was more convenient. Anyway, I am updated now! I appreciate your and everyone's help on this and hope it resolves for other people!
Thank you,Rob Milliken
My update is that the solution from hanselman.com worked for me. I copied in a volsnap.sys from another machine using a USB drive, my PC finally booted and I was able to upgrade to 17025 and it seems to be working fine.
Thanks for everyone's help
