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

Kari said:

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:

Tweet

— Twitter API (@user) View on Twitter

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:

Tweet

— Twitter API (@user) View on Twitter

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.

Tweet

— Twitter API (@user) View on Twitter

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

You with cldfit.sys and me and others with volsnap.sys. I’m like you, I can’t leave it alone. I just did another suggested solution and screwed things up again. I swore yesterday I was not going to touch this build again. But here I go again.

Holy Cow! You guys are really unfortunate with 17017. [emoji44]

M4v3r1ck said:

Holy Cow! You guys are really unfortunate with 17017. [emoji44]

Some sure seem to be luckless - Once I got rid of Acronis True Image I've had no issues at all.

Fixed my problem with the Windows Store by renabling the Windows Firewall and running the foloowing highly intutive command from an elevated command prompt The other apps seem OK now

$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest

M4v3r1ck said:

Holy Cow! You guys are really unfortunate with 17017. [emoji44]

I'm not having any problems with 17017 at all.

Wynona said:

I'm not having any problems with 17017 at all.

I meant Kari and Magilla in the first place, but many others having issues as well. [emoji4]

Cheers

My other desktop PC updated from 16299.15 to 17017 using self made ISO is working perfectly but this one absolutely refused to update from 17004 although I made ISO on it after it downloaded alright. Now when I downgraded this PC with 17004 to FCU and set everything up to work flawlessly, I'm going to make another MR backup and try to update it to 17017 and see what happens.

pigpenz said:

Kari...surprised some one didn't jump on you for not knowing what beta testing is

What?

Pigpenz... surprised someone didn't tell you what beta testing / Windows Insider program is. As you clearly have not a faintest clue what it is, let me explain it to you. Maybe you can learn something new.

It means testing and reporting. When bugs found or the software / OS you are testing becomes unusable, you'll report all bugs and errors you've found. In my case I reported everything that happened, starting from clicking this notification every time after Windows had rebooted after every GSOD and leaving feedback using the official Feedback Hub:



I also used official Windows Insider social media channels to report my issues, this chain of tweets is a good example: Kari on Twitter:

In addition, as a member of Ten Forums, the best available source of Windows 10 Insider information and support on the whole Interwebs, I reported about my issues in this thread which is dedicated to build 17017 and its issues, posting about everything that happened.

You seem to think that testing Windows Insider builds means that you install them and then if any issues you just remain silent and wait for the next build. For me, and for most of our members and fellow Insiders it means testing and reporting.

Please do not hesitate to ask if you still don't understand this about testing Insider builds.

Kari