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

CountMike said:

That still doesn't explain by what definition is their "support" and sounds only as an excuse.

it is

Geeks, it's not so black and white.

I can understand that answer from Jason, it seems that he didn't check the whole chain of tweets about the issue where I made it quite clear that I had tried to resolve the hourly GSOD issue with clean install only after it was clear my 17017 was unusable after an in-place upgrade through Windows Update.

If I had only tested a clean install, not an upgrade install through WU, his answer would be valid: officially clean install scenarios are unsupported until they magically become supported the day ISO will be released.

Kari

f14tomcat said:

it is

That's what I though too. I come here with a problem and there's 10 people all over it, go "there" and barely a peep if any. Best "advice" was reboot or just some things that even birds on a tree know about.

Kari said:

No hostility intended. You openly told you laugh to issues your fellow members and Insiders are having. You have previously told us that real Insiders do not clean install.

I wanted to clarify this. An example: at the moment, according to you and I admit, Jason from Insider team, clean installing this 17017 is unsupported. But, one day in not too distant future Microsoft will release 17017 to Slow Ring and few days later ISO, at which point like magic clean installing 17017 becomes supported.

I cannot see the difference, how it suddenly changes from unsupported to supported without any whatsoever changes in build itself, no new code, no nothing.

And yes, I was very sincere in my previous post.

Kari

I have nothing against anyone making an ISO, its their choice.....but one should be prepared for unforeseen problems when doing an ISO on the latest released unverified Insider iteration.

Making an ISO halfway through the Update process, before restart, mays not be a complete Update.
Missing items could include drivers etc....see attachment posted a day ago of which I am fully in agreement with.

I made ISO out of any single build since it was possible. Some were used to update another computer or VM, some to force update when it wasn't possible another way and few were used for clean install. Saves a lot of time and internet bandwidth. Couple of times I did clean install to troubleshoot problems and than returned to previous build and updated it. Several times I gave it to some friends that didn't know how to do it or had too poor internet or a machine.

dencal said:

Making an ISO halfway through the Update process, before restart, mays not be a complete Update.
Missing items could include drivers etc....see attachment posted a day ago of which I am fully in agreement with.

Since I can say with confidence that I know how the upgrade process works and what is involved, I can also say that while creating an ISO from files in middle of the upgrade process which is missing something, then that ISO creation will fail and also the WU upgrade will fail.

All this means that the upgraded OS won't work if something is missing, no matter if you do it via an ISO or WU. Every single upgrade file is cataloged and using those lists and integrity checks makes it perfectly safe to create an ISO once all files has downloaded and are expanded into it's final state.

Basically, if clean installing from home made ISO does not work, then the upgrade via WU nor OOBE after an upgrade won't work either. It is just the way how the whole system works. Either you have all files, or you don't.

EVERYTHING needed for an ISO creation is included in the upgrade catalog files. If the files exist on your current machine they get copied from there, but if they don't, they get downloaded (this is usually only the files that are actually upgraded). Only thing we really need is the base Windows image, setup files, and WinRE (same as WinPE but with the recovery tools added).

HippsieGypsie said:

Sorry to see you're having so much trouble. I see you're able to take ownership of the file now. Just to be sure > You did delete the .old one once you imported the other, yes?

So far as I know, USB drives don't affect the outcome. Just secondary interior drives.

yes, I did delete old file. And as soon as I plug in my usb drives, the green screen appears. I am restoring my backup made from before I started this update and turn off my insider for a while on this computer. Unplugging my other ssd’s Made no difference. Plugging them back in made no difference. But something about my usb’s Makes a difference. I read something similar on MS help page. But they were saying removing usb drives gets rid of volsnap issue during install, which it did; however plugging back usb makes for green screen.
p.s. I do appreciate your help and other member help. That’s what the forum is for—not Fighting.