Avatar of BGFSmurf
BGFSmurfFlag for United Kingdom of Great Britain and Northern Ireland asked on

Windows 10 Upgrade Fails at Various Percentages.

Hello,
I am trying to upgrade Windows 10 Enterprise from 1703 to 1809 using SCCM Current branch on Surface Pro 4 and Surface Pro 5.
I have just published the upgrade to a collection which will then appear in Software Center "Updates".
The update is received and installed and you then get prompted to reboot.
Once rebooted the upgrade hangs on around 75% or 79%. The upgrade never completes and you have to power off\on and Windows remains on 1703.
Some upgrades have worked and have successfully completed, but it seems I have a batch that has issues.

I have tried the following:
1. Increased the maximum runtime to 240min (Made no difference)
2. Installed the latest Surface Pro driver and firmware pack (Made no difference)
3. Ran Microsoft Fix it tool which did delete the MS update datastore and created a new one (Resolved the issue on a few but not all – Not a solution)
4. Ran Setup.exe from the VLSC Windows 10 Enterprise iso. Same issue gets stuck around 75% or 78%.


I have attached the setuperr.log and a screenshot of the error which presented with running setup.exe from the iso.

Be grateful for any help.

Thanks
Matt
When running Setup.exe from ISOsetuperr.log
* upgrade 1809Windows 10Windows OS* configuration managerSCCM

Avatar of undefined
Last Comment
BGFSmurf

8/22/2022 - Mon
Jane Updegraff

Sometimes when the c:\users folder can't be moved it's because there is a disallowed username in the users folders somewhere. Are there any user profiles with a really long or weird names (with unusual characters for instance)? It also happens when there is not enough disk space to copy from the old users folder to the new users folder so make sure you are not close to running out of disk space before you start the upgrade process.
ASKER
BGFSmurf

Hi Jane, Currently have 148GB free so I don't believe it's disk space. I have just checked Users and looks fine. Only have a few profiles each with firstname.surname - Looks fine. We do have a desktop.ini file located in c:\users but I don't think that will be the cause. Thanks Matt
John

it seems I have a batch that has issues.

Also, you appear to have done the steps in the troubleshooter including deleting what you can from  C:\Windows\SoftwareDistribution\Download.

Try updating all the drivers - particularly BIOS and chipset (done via Windows on a Surface).
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Jason Johanknecht

Can you try creating USB media with the media creation tool for v1809 and upgrade them that way?
ASKER
BGFSmurf

Hi Jason, The media creation tool doesn't work with Enterprise - Gives an error.

Thanks
Matt
ASKER
BGFSmurf

Update
I am testing with running setup.exe directly from the 1809 Enterprise ISO.
On one test machine, this failed yesterday with an error 0xC1900101 - 0X4000D - Screenshot attached.
Today, I have run setup.exe again, exactly the same and this time the upgrade completed to 1809!

I have no idea why.
Any thoghts?
1809Error.PNG
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
John

Running Setup from the ISO file starts the Repair from the very beginning including Firmware and all other drivers. That may be the reason here
ASKER
BGFSmurf

Hi John,
Little confused by your comment. We don't allow machines direct access out to WU. All updates come from SCCM. At present we are not pushing any Surface firmware. Do you have any KB's that describe the process you mentioned? Thanks Matt
John

There were issues beginning around V1703 that caused errors when trying to run the repair from the Media Creation Link. That happened to me. I saw another user running from setup. I tried it and it worked.

This is now how I suggest all users run the Windows 10 Repair
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER
BGFSmurf

Just to be clear, the setup.exe was run directly from the 1809 Enterprise ISO. As far as I know this doesn't repair anything. The process checks to see if the upgrade can be run, i.e disk space available and gives an option if you want to keep data etc.
Also I am only trying it this way to see if it's more reliable than using SCCM. The bottom line is I need to use SCCM as we have lots of Surfaces around the UK.

Thanks

Matt
John

You should call Microsoft Hardware Support at this point. If the Firmware and Driver updates were successful, then the Feature Update should work. I don't know any other way but to run from Setup but Microsoft may know
aravind anche

Are there any errors in log files?
setuperr.log
setupact.log
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER CERTIFIED SOLUTION
BGFSmurf

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question