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

HippsieGypsie said:

What the hey. Everything went fine, went to reboot, it said it installed update 100%, and then a BSOD. It rebooted, tried again, started typing this post, then a GSOD. Never had this happen before. Must be my turn for carnage. What a fine welcome home. LOL.

Well, welcome to never ever land. Hope you have better luck than many of us have.

magilla said:

The computer affected is an AMD but not that old. Of The two that had no problem one was AMD RYZEN AND ONE A VERY OLD LAPPY Intel FROM Vista era. The install downloads and phase one installs; after the restart, the next phase runs, then goes to enter the final phase of install and that’s when I have the BSOD and message. Is that what you get also @AndreTen?
i have also tried an iso install and a clean install with same issue.

Uhm, sorry about this. Was thinking we all get same error at the same point. It was suspicious, that some of you got time to boot from USB and get to the new system.

For me, error occurs right after restart. Maybe 5 seconds of dots in circle. And then reboot and back to old build really quick, like there was nothing to delete... (SSDs could make that hard to evaluate...)

Kari said:

Took cldflt.sys from build 17004 Hyper-V Vm, booted to Command Prompt, replaced both instances of it (\drivers and \WinSxS). I would like to say that this error message shown after booting back to desktop is definitive proof about cldflt.sys being for OneDrive Files on Demand:

Attachment 158299

No more GSOD since doing the above but Onedrive, OneDrive for Business and all Office applications not working. Alternatives being going back to 17004 or accepting a GSOD every hour in 17017, I am at the moment building a 17004 deployment image in Hyper-V, then wiping the HDD and deploying it.

It's past 1 AM here, seems this will be a long night. For once it's a positive thing to be an insomniac :)

Kari said:

No more GSOD since doing the above but Onedrive, OneDrive for Business and all Office applications not working. Alternatives being going back to 17004 or accepting a GSOD every hour in 17017, I am at the moment building a 17004 deployment image in Hyper-V, then wiping the HDD and deploying it.

It's past 1 AM here, seems this will be a long night. For once it's a positive thing to be an insomniac :)

But now how to re-link onedrive? Full reinstall?

AndreTen said:

Uhm, sorry about this. Was thinking we all get same error at the same point. It was suspicious, that some of you got time to boot from USB and get to the new system.

For me, error occurs right after restart. Maybe 5 seconds of dots in circle. And then reboot and back to old build really quick, like there was nothing to delete... (SSDs could make that hard to evaluate...)

Interesting — i Thought it would be at or near same point, too.

magilla said:

But now how to re-link onedrive? Full reinstall?

No, of course it will work again after I have finished building 17004 install image and deployed it. Kind of clean install but it makes the whole thing easier when I do everything ready in Hyper-V, booting a VM to Audit Mode then customizing to my liking, installing all software and so on, then capture the image with DISM, add all drivers to image and finally deploy it.

Final result is a clean install, the big difference to normal clean install being that installation will be completely "hands free", automated taking just a few minutes longer than normal clean install but at first boot to desktop Windows is fully updated, all device drivers installed, all my usual user accounts created, theme and stuff customized and all software installed.

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.

FWIW: Here's my VM-WIN10PRO-17017 running for 17hrs:





Good luck solving your issue Kari!


Cheers