When Insider build upgrade fails - A Workaround

fdegrove said:

Hi,
@Fafhrd :

I am on ethernet only and it still borked again and again. As said, a clean install got me through it but that also threw runtime errors. It works but it's abloody shame MS even dared to release this. They love our anger about it. Wow.
What's their next step ? I wonder.

Cheers,

Exactly the same as Wynona noted - failed upgrade on ethernet, - in her case, on a machine upgradeable in a reproducible manner when connected only by WiFi.

Kari said:

I disconnect Ethernet cable every time I start an upgrade, also now with my failed 16215 upgrade. WiFi is usually always disabled, only used on laptop when away from home where no wired connection is possible.

Thanks - noted.

Kari said:

They have done it, several times. Build 16215 seems to have quite a many issues but that, too belongs to this being Insider. Microsoft is testing and fine tuning the feature upgrade delivery system as much as we are testing how those builds they deliver work. I for sure miss ESD upgrades but things evolve, Microsoft has decided it's UUP now.

Insider Preview ISO images are available for those wanting a slower pace. Build 16193 is at the moment most recent ISO made available at Download Windows 10 Insider Preview Advanced.

Kari

I know that they have, I also have no interest in build 16193 as I used it when it came out. How can insiders or anyone test the features of a build that will not install for over 1/2 of the people trying to use it? This is the first of all of the builds I have installed that failed to do so. I started with the 2nd. Build. It fails at the same point every time. They will come out with a workable build soon, most likely before Friday.

Kari said:

No, the files are there even when upgrade fails.

That being said, I naturally assume that any Insider makes an ISO even before restarting to upgrade, when upgrade files have been downloaded. If upgrade then fails the ISO is already there.

I have not made a copy every time there is a new build...only randomly. I can see now why I should take the time to make them every time!

Thanks for getting back to me...I will try this workaround later and let you know if I have any troubles that I cannot figure out how to fix!

Danny R

Kari said:

I could not disagree more! Following your logics when my PC crashes and wont start, I should just use it as paperweight and buy a new one, not even trying to troubleshoot and see if I can fix it because it's not my job.

Why did you make 16215 ISO? It's not your job to do install media, with your logics. You should switch to Slow or Release Preview rings and only use ISO images released by Microsoft.

Your logics, if applied to us all would make sites like Ten Forums without a purpose. Replies to any issue would be something like "Don't ask us, wait Microsoft to fix it! It's not your nor our job to troubleshoot issues".

Kari

I posted that the installed failed many times using an ISO, now why would it install using and ISO made from your Tutorial. On several of the failures I was left with nothing n-NO OS. Just 2 partitions that would not boot. Without the use of a Macrium Reflect Boot Disk and an image I would have been without a PC. Going forward, if it does not install then I will just move on. My PC is 8 years old and uses Sata II and USB II and it is NOT support Miracast. So maybe this is the reason. I will find out when a new build is released. Thank you for your input.

Kari,

I am very certain I used the same name as you did in the tutorial when renaming the ISO which is W10PRO.ISO but when I am trying to enter Mount-DiskImage C:W10PRO.ISO powershell says it cannot find the file.

How do I back out of the installation to verify the name and exact location of the ISO I created?

Thanks,

Danny R

If you are already OOBE screen, press WIN + E to open File Explorer, browse to find your ISO.

In Welcome to Windows 10 screen, exit PowerShell mode with command exit, type dir C:\*.iso /s and press Enter to search C: drive for all ISO files. Replace C: with actual drive letter if you saved your upgrade ISO on another drive.

To exit without upgrade, just close Command Prompt, select your region and click Yes (normal OOBE screen), or click Next (Welcome to Windows 10 screen).

Kari said:

If you are already OOBE screen, press WIN + E to open File Explorer, browse to find your ISO.

In Welcome to Windows 10 screen, exit PowerShell mode with command exit, type dir C:\*.iso /s and press Enter to search C: drive for all ISO files. Replace C: with actual drive letter if you saved your upgrade ISO on another drive.

To exit without upgrade, just close Command Prompt, select your region and click Yes (normal OOBE screen), or click Next (Welcome to Windows 10 screen).

I was on the Welcome to Windows 10 screen. The only thing I could do was open an elevated command prompt which gave me the message Directory not found when I typed dir C:\*.iso /s. When I exited the command prompt all I could do was let it finish installing Windows 10 which left me right back where I started with Build 16199.

The iso file was in C: labeled WIN10PRO.ISO so I didn't forget the name...it was just not being recognized for some reason.

Should I try again or has Microsoft put out a new build at this point?

I think a new build will be released this week, but of course we can never be sure until it really happens.

This is an academic enquiry, not important to any critical system, perhaps only of interest for those who attempt to run Windows 10 on vintage devices.
I have a hard-to-upgrade old laptop which has only ever managed an upgrade from Windows 7 Pro x86 to build 10586, will not upgrade to newer builds (U/G from 7 or 10), nor will it clean install, nor in-place repair upgrade, since it seems to have intrinsic problems with Windows 10 Setup.

The Windows 7 upgrade appeared disastrous at first with IRQ conflicts causing system interrupts to use 100% CPU, which were solved by disabling the WiFi adapter.

It will install Windows 10 (any builds tried so far) by applying a windows image (WIM or ESD) using DISM, Imagex, or Wimlib-Imagex, and proceeding thru the OOBE.

It will run "Windows 10 to Go", on "inferior" (not MS Certified) USB sticks of any build up to 15063 (none later yet tested).

Wishing to attempt an upgrade from build 14393 to 15063, I attempted the method in this thread, overnight, because any operation involving setup takes a long time with this machine.

I carried out instructions as far as 16)

The upgrade was unsuccessful and left me at a boot menu with setup or Windows 10 as an option.

Selecting setup, it proceeded to rollback the upgrade, and when I returned some time later I am on the region screen of the setup program for 15063. Calling up the command console with Shift F10, it shows:

Code:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

c:\Windows\system32

I guess I am still in sysprep - I've gone blank - how do I get out of this, and boot back to the old windows?

Kari said:

I think a new build will be released this week, but of course we can never be sure until it really happens.

Silly me forgot the backslash in between the drive letter and file name! I didn't get the regions screen; I got the Welcome to Windows 10 screen and at the final reboot the whole thing failed.

I will wait for Microsoft to sort it out after all...

Thanks anyway...

Danny R