Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC Insider

Fabler2 · 15 Oct 2017

Fabler2 said:

DISM restore health has fixed it for now. System file checker found nothing.

Well here I go again although have rebooted and restarted multiple times previously but not today. Same problem, start, cortana, action centre, photos not working. This is the state my desktop landed in and apologies for the photo quality had to use my phone to take a shot,

Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC-2017-10-15.png

Took a while to get to this state. Note that start is open and settings is trying to open and action centre is open. Tried a shutdown when it was available but got error Task Host Windows. Task Host is stopping background tasks. (Microsoft\Windows\Plug and Play\ device install reboot required.)

What? Haven't installed anything. Restart did not fix it until I ran DISM again and rebooted.

Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC-second-dism.png

Opening task manager and selecting file and pressing CTRL key while clicking on 'Run new task' is a godsend :)

Cliff S · 15 Oct 2017

New game when your bored, and you have an insider VM and semi annual channel(formerly Current Branch) host.

Ask Cortana sumptin' and see which is faster & gives the better answer:)

17017 got it, 16299.19 choked

Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC-image-005.jpg

slicendice · 15 Oct 2017

Still after 4h45minutes I have had no issues with stability. CMD output redirection to any other place than root of C-drive does however not work.

Here is a list of everything driver and service related that is running on my VM: list_of_drivers.txt

M4v3r1ck · 15 Oct 2017

Kari said:

As promised @Slice & Dice:

I started video capture 60 minutes after last GSOD. If you can use a minute of your valuable time, here's the proof:

Like clockwork: I will get a GSOD (BSOD) 60 to 65 minutes after boot, every time, always due cldflt.sys.

I just changed my VMware Fusion VM-WIN10PRO-17017 to never fall asleep. I'm curious if your issue - depending on the used drivers of course - will occur in my VM!

Keep you posted Kari! [emoji41]

Cheers

magilla · 15 Oct 2017

f14tomcat said:

Take ownership and rename it cldflt_old.sys, then copy.

I cannot take ownership. When I try, it just will not change to permit any other ownership. Weird. But, the issue is I have even tried to do a full clean install and get the same issue. A full install should ignore what is there and overwrite everything. The install does the same thing, goes so far, then the error message from volsnap.sys appears. That is what those of us who are having this issue are experiencing.

Cliff S · 15 Oct 2017

magilla said:

I cannot take ownership. When I try, it just will not change to permit any other ownership. Weird. But, the issue is I have even tried to do a full clean install and get the same issue. A full install should ignore what is there and overwrite everything. The install does the same thing, goes so far, then the error message from volsnap.sys appears. That is what those of us who are having this issue are experiencing.

Have you tried Shawn's tool>: Add Take Ownership to Context Menu in Windows 10 User Accounts Tutorials

slicendice · 15 Oct 2017

This issue you are having is clearly related to the file system in some way. Try disabling all file system related protections from BIOS/UEFI, disable any AV then also run a full scandisk on C-drive.

volsnap.sys and cldflt.sys are both related to the FileSystem and Volumes.

Let's see if that gets rid of this issue....

cereberus · 15 Oct 2017

Kari said:

Yes. I've also tried 17017 repair intall from ISO.

Ok- silly question (actually questions are not silly, only answers). Have you looked in Task Scheduler for any clues?

slicendice · 15 Oct 2017

cereberus said:

Ok- silly question (actually questions are not silly, only answers). Have you looked in Task Scheduler for any clues?

I was thinking the same.

Also check any indications of FltMgr.sys crashing or stopping suddenly. cldflt.sys depends on this files system service.

AndreTen · 15 Oct 2017

slicendice said:

This issue you are having is clearly related to the file system in some way. Try disabling all file system related protections from BIOS/UEFI, disable any AV then also run a full scandisk on C-drive.

volsnap.sys and cldflt.sys are both related to the FileSystem and Volumes.

Let's see if that gets rid of this issue....

My short summary about that issue:

Can only talk about volsnap.sys connected errors (reboot error after first restart...)
Was trying to eliminate possible causes with:
- uninstalling any third party SATA drivers (Intel ...)
- disabling any security software (including WD)
- uninstalling Macrium (had recent problems with removable drives)
- updating system to .19 (from .15)
- removing all hidden devices in Device manager
- you name it

Ended with messed EFI partition after 7th or 10th upgrade (EFI partition suddenly got letter and showed in Explorer

)

Back in RP build atm and intended to stay 'till the new build. (Sorry TC, won't play with copying old volsnap.sys, because i have no time left..)