Avatar of Wilf
Wilf
Flag for Canada asked on

Update windows 10 1809 to 1909

I am trying to upgrade Windows 10 1809 computers to 1909.  I will list the methods  used, but I always get the attached error.

First try was to check for updates to make sure that 1809 was up to date, and it is
Second - downloaded the creation tool for 1903.  The computer is connected to a Windows 2016 server and the user has administrator authority
The error appeared during the setup
Third, ran the three DSM health commands no errors indicated
Fourth Did clean boot with same results
Fifth Used a DVD with 1903 installed on it to do an in place install.  Same results
Sixth ran the update trouble shooter could not find a problem
Seventh Logged in as local user and tried 1903 from the DVD
Eighth - Used a DVD with 1909 on it and tried the in place install with the same results.

 I would like to avoid doing a clean install and setting up the 10 computers on the network again

There are 15 computers on the network, and one of them did go from 1809 to 1909 using the in place method
error-install.png
Windows 10InstallationWindows OS

Avatar of undefined
Last Comment
Wilf

8/22/2022 - Mon
Cliff Galiher

Remove any and all removable media (USB drives, SD cards, etc.). There is a known block to orevend removable drive corruption during upgrades.  At first glance that looks like what you are hitting.
arnold

What is the environment made of?
From the same source you got version 1909, get the update assistant to confirm you do not have a device that might be ..

If you are in an AD environment, test the following
Create a new local account on a test system.
Logoff, login with the local account.
Disjoin from the domain, rejoining the workgroup
Reboot, login, try the inplace upgrade.
See what happens.

If completes, rejoin domain.
Wilf

ASKER
There are no usb or card readers on this machine.  I used the DVD instead of a usb for that reason

Will try the new user as soon as I can get back on the machine
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
arnold

New user, disjoining domain is only needed if computer member of AD domain.

Check whether there is done software deployed on others not deployed on the one.

Checkhealth, clean....
Sam Simon Nasser

why not using the windows update/ to upgrade from 1809 to 1909?
try using WSUS offline http://download.wsusoffline.net/ and only check windows 10, to download its latest updates.
nobus

⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Wilf

ASKER
Same results with new user and disjoined from the domain.  I have had the same results when just doing the download from Microsoft to the computer.  I will try once more to run the DSM commands.  Same results the last time I ran them.
ASKER CERTIFIED SOLUTION
kenfcamp

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
arnold

Scanned through the link Kenfcamp provided. is the current version up to date with updates? Do you check/allow the install to check for updates? if so, do not allow check for updates.

Get the update assistant:
https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

dism /online /cleanup-image
/CheckHealth
/scanhealth
/restorehealth


Are these system upgraded from 7/8/8.1
make model of workstation?
Available disk space?
Wilf

ASKER
880GB free of 930 GB
the computers are 3 years old and came with windows 10 installed
They are custom built work stations with Asus mother boards, intel i7 6700 CPU8 gigs ram
will re run the dism options  error 87
log file attached
dism.log
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
arnold

You do not seem to be providing one of the three additional parameter to /cleanup-image included in my post.
/checkhealth
then
/scanhealth
then
/restorehealth

all three are the parameter as to what you want the /cleanup-image to do.
Wilf

ASKER
it fails on checkhealth.  I had been running these as separate commands
Wilf

ASKER
last post should be fails on cleanup-image
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
arnold

you need need to run
dism /online /cleanup-image /checkheatlh
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restoreheatlh

as the complete command.
error 87 means the dism command was not complete.
Wilf

ASKER
Got it.  Here is the log, if that would be helpful
dism.log
arnold

I did not need the log unless the output from the command indicated an error that interferred with things.
run sfc /scannow
the other option is to go through dism offline and repair clear the windows OS image.

There is something on the system but it is not clear. earlier events included references and errors with oemx.inf file .
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Wilf

ASKER
I ran sfc/scannow, and it found errors.   It was on an AD, so now logged in as new user as suggested,  and trying the re install without checking for updates.   Will post as soon as its finished.   One other station installed ok with local user.  Windows is allowed to do updates and I scan for updates prior to installing 1909
Wilf

ASKER
Thank you everyone for taking time to comment.  The items from Arnold did show some errors, but it was the multiple ID issue that once completed, allowed the updates to work as they should.  They even updated without disjointing the domain or logging in as single user.

Thank you all again