OK, five days of fighting and I finally gave up.
A recap:
Got a refurbished Asus laptop on Friday evening. Restored a 17004 Macrium image, everything OK. Just an hour after restoring the image, 17017 was released. Upgrade 17004 to 17017 went smoothly although it took some time.
After the upgrade, I got a GSOD an hour after boot, then again a GSOD an hour after reboot:
After some more GSODs, each 60 to 65 minutes after boot, I gave up and tried clean installing 17017. The same continued, cldflt.sys causing a GSOD always 60 to 65 minutes after boot.
Tried to take cldflt.sys from 17004, replacing the one in 17017 with it. No more GSODs but otherwise I pretty much bricked the laptop. OneDrive, all Office applications and Microsoft apps stopped working:
Decided to restore 17004 image and skip 17017, but only an hour after doing it, I just couldn't let it go and started testing. In past few days I've only been clean installing, upgrading, restoring an image and so on. I've tested all possible scenarios I could think of:
- Upgrade 17004 to 17017
- Clean install 17017
- Clean install 15063, upgrade to 17017
- Run SFC and DISM countless times trying to repair Windows
Whatever I do, whatever scenario to get 17017, I will get GSOD 60 to 65 minutes after boot, never less than 60 minutes never more than 65 minutes. Like a clockwork. Faulting driver every time cldflt.sys. Laptop works perfectly, Windows has no issues, then an hour after boot, a GSOD.
There's a limit in how much you can continue testing. At least I have this limit and I reached it today. I will totally forget 17017 and hope this issue is not present in next builds.
I made a new 17004 deployment image this afternoon and finally now, almost midnight on Wednesday I am in peace (and in pieces!). I have a fine tuned 17004 up and running in satisfying way, I have totally forgotten 17017.
Kari