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

CountMike · 16 Oct 2017

So, what is official way to drop out of Insider program (even temporarily), switching to normal version still means new, clean install ?

magilla · 16 Oct 2017

HippsieGypsie said:

Did you two find a fix for this? I'm getting the same. Is this related to dual booting?

No, still no fix; I gave up for several hours — my Sanity needed a rest.

AndreTen · 16 Oct 2017

CountMike said:

So, what is official way to drop out of Insider program (even temporarily), switching to normal version still means new, clean install ?

Did you click on that "Stop Insider Builds"... If you're on RS4 it's a bit more complicated

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

CountMike · 16 Oct 2017

No, I didn't click it, it depends on what happens if/when I do. I'm on 17004 right now, can't install 17017 but my other computer updated fine from 16299.15. I was thinking that dropping out of Insider would bring me to that version and after official update tomorrow to go back to Insider program which should start with at least 17017.
So if I click on Stop, what happens ?

boaterva · 16 Oct 2017

So, on my 'can't get 17017 at all' issue (can't see the Insider options), I had to remove the VM from the domain to get rid of the GPO. Then I had to re-register my account as an Insider account. Then I got all the options. I can't tell if it's the GPO or the re-register that really fixed it...

Once I get 17017 downloaded, I'll put it back in the domain and see if it still works.... At this point, who knows, looking at all the 17017 issues!

WEKJR · 16 Oct 2017

AndreTen said:

Did you click on that "Stop Insider Builds"... If you're on RS4 it's a bit more complicated

I ended up delaying Insider Builds for seven days and will see what happens. (after reinstalling 16299.15)

WEK

AndreTen · 16 Oct 2017

CountMike said:

No, I didn't click it, it depends on what happens if/when I do. I'm on 17004 right now, can't install 17017 but my other computer updated fine from 16299.15. I was thinking that dropping out of Insider would bring me to that version and after official update tomorrow to go back to Insider program which should start with at least 17017.
So if I click on Stop, what happens ?

It's no easy way out of 17xxx builds. postpone updates for a few days, that's all.

I was on 16299.15 and failed to update. Clicked on all that buttons, no big deal - they'll ask again

cyberrufus · 16 Oct 2017

I ended up hiding 17017 from WU. Seemed like the easiest solution until or if a fix is available.

CountMike · 16 Oct 2017

AndreTen said:

It's no easy way out of 17xxx builds. postpone updates for a few days, that's all.

I was on 16299.15 and failed to update. Clicked on all that buttons, no big deal - they'll ask again

I already postponed all updates for 7 days and may have to do it again, it's just that it would have been nice if it would have dropped me to normal build and try 17017 over it. I have full MR backup of this one so I may install 16299 and 17017 over it but it would take time. I have ISO of each one.

Tony K · 16 Oct 2017

magilla said:

No, still no fix; I gave up for several hours — my Sanity needed a rest.

Yes, I can see where it would drive one nuts. From the Feedback Hub a couple of hours ago by Steve K:

With any internal HDD connected or enabled on the system 17017rs_prerelease repeatedly fails to install. GSOD indicated page fault and volsnap.sys as problems. After disconnecting said other internal HDDs 17017 installation completed successfully. Reconnecting drives produced the same GSOD. Renaming the 17017 version of volsnap.sys to volsnap.old and copying the previous version from the windows.old directory solved the problem: all drives visible/no GSOD. You have to change the permissions on the 17017 volsnap.sys to rename it to old.

Which means > He disconnected internal drive(s), installed the update, rename volsnap.sys to volsnap.old and copying the previous version from the windows.old (or from wherever), then reconnect the internal drive(s).

I'm going in. Wish me luck.....