Windows 10: Announcing Windows 10 Insider Slow Build 17025 for PC

Were you successful with this?

 

All unplugged except Logitech Illuminated (corded) keyboard and G400 mouse. Same issue as before. Went to Insider settings and backed out until next Release. All back to normal on 17017 now. Tried 'Fix me' and same problem again.
Over time, each of the (3) desktop PC's has experienced one-or-more Pro Insider Update problems, while other (2) have not. Then seems to 'rotate' to another. ????? Perplexed that they run without issue, daily, then all Update, then random failure.
Over time, all get Updated, then fine until one like this.
Thank-you for suggestion. Maybe wait a day or so and try starting Pro Insider again ?

 

The other suggestions is to copy from one of your 'successfully installed' machines the volsnap.sys file and paste it to the machine giving you problems. The directory to find is windows/system32/drivers/volsnap.sys. On your 'donor' machine you need to take control (see Brink's tutorial for this) of the file, and same for the 'recipient' machine. You can do this while the machine is still in 17017. Also note that the recommendation of Microsoft is turn off 'restore points' My issue was USB drives that were plugged in. When I unplugged them, the install took place, but replacing the USB drives caused a BSOD pointing to volsnap.sys. After I replaced the volsnap.sys with one from working directory, the problem went away. Now, I don't have this problem in 17025. Good luck.

 

Download, install and ISO went quickly and without issue. Now time to see what I have and how well it works.

 

Terrific help ! Thank-you so much.
Will proceed and confirm ...

 

Oh well things going backwards,
got to 23% installing then swung straight back to prepairing.

NO warnings or error messages

View installed shows failed 0x8024200d
0x8024200D -2145116147 WU_E_UH_NEEDANOTHERDOWNLOAD The update handler did not install the update because it needs to be downloaded again.

bargain.


Roy

 

The change in the light effect known as "reveal" between build 17017 and 17025 is quite noticeable.

 

On heading line in task manager, startup, right click on it, and select command option. Then the executable is listed.

 

Installing now...

 

Don't know why or how but when I got home tonight my clean install of 16299 was installing 17017 again. It failed but offered me 17025 instead. After not restarting at the end of the install and then starting all over again (without downloading) and installing the system rebooted and I now have an updated 17025 and it put me back in the "Fast" Insider Lane. Hard to say what happened.

WEK

 

Seems more annoying than useful.

 

One thing I noticed was more restarts than usual. (But my Insider history only goes back 7 months.)

 

Had to abort the updates in Linux because the UPS suddenly went haywire and was acting like there was a power failure. Even if the VMs I can just recopy from Windows Server 2016 VMs. But I'm continuing with downloading on the physical Windows 10 and it going smoothly so far. I really hate hardware actually.

 

GSOD on 16299 boot up>>>> Image Restoration>>> then...

 

Can't find anything on the Net about that file. Might be a PUP attached/added in a download of another program you installed. Does it have anything to do with gaming or gaming sites? Do any of these look familiar?

twbguild.com - Bing

MS Controls some of the settings in Insider previews via Group Policy. Click on "View configured update policies" under that text for explanation.