New
#390
I got my volsnap.sys from the windows.old folder. That may make the difference. Not sure. Followed this guy's instructions to the tee. Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC Insider - Page 37 - Windows 10 Forums
Hot lead = Power cable wasn't seated all the way.
The old Acer finally finished and now thrashing about. Task Manager is like a blinking Christmas tree.
Sir, please let me ask some clarifying questions, especially as you have earlier shown that you have certain rules to determine who is a real Insider and who not, and the above quoted post of yours being clear continuation to that supremacy.
Windows Insider Build 16296 ISO, the last available at the moment for download at Download Windows 10 Insider Preview Advanced.
Do you mean that you laughed to all those users that had made the ISO of 16296 before the official ISO was released and clean installed using the self made ISO, thinking they were crazy, not real Insiders?
The day, the very moment the official ISO was released, was it OK according to you to do a clean install using this official ISO and remain a real Insider?
If you answered yes to both above questions, could you please explain what is the difference? Not being a real Insider, breaking against "Insider Rules" when clean installing today with self made ISO, but remaining "a real Insider" following the rules clean installing the very next day using an official ISO? Both, self made and official being of course the same.
Very sincere,
Kari
On skippy
always get error cx1900101
and volsnap.sys error
on fast
installed fine didn't even know it had installed on other machine over weekend
The apparent volsnap.sys error in my case was caused by a damaged MBR. Put install media in and choose no to upgrade, then choose repair and command prompt. Navigate to the install drive Windows/ system32 directory and type bootrec /fixmbr at the command prompt.
I fixed mine by using (activated) Easeus Partition Master from a separate Windows install.
Win 10 now reboots happily. Took me a fair while to find this solution for me. Windows crashes can sometimes damage the MBR.
Problem is I cannot even boot it from a USB drive with an ISO. I get a BSOD before the setup even runs. 17004 to exactly the same drive with the same USB drive in the same USB slot on the MOBO is fine. CHKDSK /f reported no errors at all and the drive shows as healthy in the event logs after booting up in 17004. I only have problems with this build and have done right from the outset. I have never had a W10 USB ISO cause a BSOD in the entire last 2 to 3 years of using W10.
Do you have a backup install CD to try if the USB ISO doesn't work?
Afraid not but there is clearly nothing wrong with the USB stick or the SSD as 17004 is fine. I also get exacty same result with an in-place upgrade either from the ISO or just through Windows Update. There is clearly something about this build my PC doesn't like. I suspect many others have the same issue. The question is why and while your problem might be MBR related I really find it hard to believe over 300 people are all having exactly the same issue and that is not related to the build when every other build works perfectly. I could go and find a CD tomorrow but given every other method of installation yields exactly the same result I see little value. Having said that any ideas are welcome but in all honesty I think there is a problem with the build that MS are just not owning up to.