Forum Discussion
Green Screen after Builder update. volsnap.sys
Ian,
Okay, long term, it might be a good idea to do a hd and RAM check, but since you have the log in screen, press the power icon on the log in display, you should get restart, hibernate, shut down, etc... Hold down shift WHILE selecting restart and keep the shift key held down until you get an optional menu (it may restart once to do this). Under advanced (I think - you might have to hunt down the structure a bit) there is a place where you can go to command line only to supercede any countdown to update. After locating an old volsnap.sys, *back up* your current volsnap and use this: http://www.winhelponline.com/blog/take-ownership-of-file-or-folder/ to take ownership of the file. Replace your volsnap.sys and cross your fingers. I hope this works for you and helps others. There of course, is more than one way to do this, but this is one route that may work best for you. If you have your disk encrypted, you might have more of a challenge to get this done (see Michelle's original post and subsequent thread on the release of build 17025 for details on how to get past that as well.).
EDIT ADD: volsnap is located under /windows/system32/drivers
Thank you,
Rob Milliken
Hi ?Rob,
I'm running a HP 250 G4 Notebook PC with a CPU 3700 1.60 GHz processor and 4Gb of RAM. I've tried for last few hours what you have suggested but trying the shift key is not working. This is a real pain as this is now a whole of this issue and I can't keep working from my iPhone and iPad as the Microsoft office App's are not great! This is now the third laptop that Microsoft have damaged and I'm getting really annoyed at their lack of support and customer service on issues like this. Not everyone has two machines or more lying around to have one as a back up in case issues like this arise. So, I'm at a lost on how to fix this laptop
Ian,
I agree with Kerry. Hopefully you have a BIOS that'll boot to a USB or DVD drive and can go that route. As I mentioned the other day, there is (thankfully) more than one way to do this. Do you have access to an alternate volsnap.sys so you can get it replaced? I would attach mine that fixed my situation (and anyone can feel free to do an anti-virus scan) but I am not sure if that violates some Windows copyright.
Sorry about the shift/restart issue - not sure why it doesn't work on your laptop. If you want to pursue this option again if the usb/DVD Windows 10 bootup doesn't help see this article: https://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10
I hope you get it working soon!
Thank you,
Rob Milliken
Hi Ian
I was where you are up until yesterday. I think you have to follow the instructions to replace the 17017 version of volsnap.sys with an older one. Since, like me, you can't get out of the reboot loop, you'll have to boot from a DVD or USB drive. Then find another version and replace it. As I said, this worked for me. If you don't have the resources, you'll have to get help. This situation shows why you only use Insider builds on a spare machine and not your main one.
Good luck,
Kerry
