Announcing Windows 10 Insider Slow Build 17025 for PC Insider

Some things are not working, none of things in right click Start menu are not starting.

HippsieGypsie said:

Initializing....

So that was it with volsnap. Interesting.

God I hope so! Two computers updated without problems thus far. Hope the issue Kari was having has been solved. My lappy is still chugging away downloading and doing first phase install. Is this a snap or what?

Kari said:

I don't know if I should laugh or cry!

I had to skip 17017 because it gave me GSOD always 60 to 65 minutes after boot due cldflt.sys. Enabled updates / upgrades again to get 17025 but my machine started to download 17017 instead.

It seems that to get 17025 I have to install 17017 first, which then makes it impossible to get 17025 because this machine requires a few hours to prepare and initialize upgrade but my machine would crash with GSOD always one hour after boot and new try.

I’m so sorry you are still having your cldflt.sys problem. Just posted I hope your issue was resolved with this release.

doubtingtom37 said:

Build 17017 was installed and was working fine. Initiated Build 17025 and system is now in endless 'greenscreen' / restart cycle. (2) other desktop PCs updated with no issues. Same network, similar config.

StopCode: PAGEFAULT IN NONPAGED AREA
What failed: volsnap.sys

Dunno how to get out of this loop now !

PLZ Help with way to clear system from this endless cycle !

Try unplugging any usb devices that are plugged in—and SD cards.

magilla said:

Try unplugging any usb devices that are plugged in—and SD cards.

Hmmmm.. Will do.....
THX!

magilla said:

I’m so sorry you are still having your cldflt.sys problem. Just posted I hope your issue was resolved with this release.

I got this issue now solved, a full cleanup and a couple of restart, WU is preparing 17025 as we speak :)

My recipe for a complete PC cleanup:

• Step 1: Run extended cleanup from Command Prompt as told in Option Two in Brink's excellent tutorial: Open and Use Disk Cleanup in Windows 10 Performance Maintenance Tutorials
• Step 2: Boot to Command Prompt, remove all leftovers in Windows\SoftwareDistribution

Kari said:

I got this issue now solved, a full cleanup and a couple of restart, WU is preparing 17025 as we speak :)

My recipe for a complete PC cleanup:

• Step 1: Run extended cleanup from Command Prompt as told in Option Two in Brink's excellent tutorial: Open and Use Disk Cleanup in Windows 10 Performance Maintenance Tutorials
• Step 2: Boot to Command Prompt, remove all leftovers in Windows\SoftwareDistribution

Just deleting content of SoftwareDistribution (in Windows) and couple of restarts did the trick for me (as stated before) :)

Kari said:

I got this issue now solved, a full cleanup and a couple of restart, WU is preparing 17025 as we speak :)

My recipe for a complete PC cleanup:

• Step 1: Run extended cleanup from Command Prompt as told in Option Two in Brink's excellent tutorial: Open and Use Disk Cleanup in Windows 10 Performance Maintenance Tutorials
• Step 2: Boot to Command Prompt, remove all leftovers in Windows\SoftwareDistribution

@Kari, glad to know your on the way. I’ve used this similar approach before too.

AndreTen said:

Just deleting content of SoftwareDistribution (in Windows) and couple of restarts did the trick for me (as stated before) :)

Not for me, I was offered 17017 whatever I did.

Had a nice nap. The first VM is now making the ISO. Started a second VM, which is nested inside of a shared ESXi6.5 Server VM.
This VM asked me to verify my identity which only required for me to input my password for the MSA. After I did it reverted to the Slow ring but I changed that to Fast Active and is rapidly downloading 17025 now. Now I'm opening my third VMware VM which is a 17017 Enterprise edition. Microsoft is solicitously inquired why this VM shut down suddenly but hey I forgot. Changing the active hours (amusing that it thinks I actually have regular working hours) to expire at 8 PM so I have a chance to make a `7025 ISO. After these VM I have a VB (lastest version 5.2.0) VM to upgrade. Then its time to copy this data to my Windows Server 2016 and finally tackle the physical machine. Looking forward to purchasing a Ryzen system early next year - AMD is just starting to pump out these CPU's in greater numbers.