How do I update from 1809 to 1903 using an ISO on a USB?

Yeah, this is basic and I =think= I know what to do, but...assume and all that. :)

Going here: Create Bootable USB Flash Drive to Install Windows 10 it's pretty straightforward on how to create an install ISO. (I've used this technique before when doing reinstalls. Thanks.)

How would I use that ISO on a USB stick to perform an update from 1809 to 1903, and NOT do a repair install or reinstall?

Am I overthinking this?

(This is because the update, despite saying it's ready to be downloaded and installed, does not work. It rolls back to 1809. I've since updated my laptop's BIOS and have also been told installing from a USB is less likely to fail.)

Thanks,
Ken

iamc3k said:

How would I use that ISO on a USB stick to perform an update from 1809 to 1903, and NOT do a repair install or reinstall?

A repair install is just an 'upgrade' to the same version as you already have (1809 to 1809). The upgrade to 1903 from 1809 works exactly the same way.

There is (at present) a minor bug in the upgrade process for 1903, it cannot perform the upgrade if any usb drive is attached. This can make it awkward to upgrade using a usb! The simple workaround is to copy the install files from the usb to a temporary folder on the hard drive then start the upgrade from there.

When you say 'ISO on a USB stick' do you mean you have put the actual .iso file on a usb? Or do you mean you have made the bootable usb install media?

If you have copied the .iso file to a usb (which would have to be ntfs or exFAT formatted, it's too big for Fat32 to handle) then just copy the .iso file to the PC. Remove the usb then mount the ISO and run Setup.exe from the root of the drive to start the upgrade.

If you have a USB with the install media on it, then create a temporary folder on the PC's internal drive, copy all files and folders from the usb to the temporary folder. Remove the usb and run Setup.exe from that folder.


Should the upgrade still fail, upgrading from the ISO in this way provides two error codes: a result code and an extend code (unlike windows update or the update assistant which only give a result code). Note both codes, they can help to determine what caused the failure.

When you say 'ISO on a USB stick' do you mean you have put the actual .iso file on a usb? Or do you mean you have made the bootable usb install media?

I mean to use the Media Creation Tool from MS and create an ISO on a USB, as shown here: Download Windows 10 ISO File

Thanks for pointing out the USB issue. I'd forgotten about that. So, yeah, putting the ISO on the laptop instead of a USB would be a better idea!

Thanks.

Hi,
Yeah just copy and paste right click the iso and use mount
Right click setup.exe and run as administrator.
Wait.

Bree said:

A repair install is just an 'upgrade' to the same version as you already have (1809 to 1809). The upgrade to 1903 from 1809 works exactly the same way.

There is (at present) a minor bug in the upgrade process for 1903, it cannot perform the upgrade if any usb drive is attached. This can make it awkward to upgrade using a usb! The simple workaround is to copy the install files from the usb to a temporary folder on the hard drive then start the upgrade from there.

When you say 'ISO on a USB stick' do you mean you have put the actual .iso file on a usb? Or do you mean you have made the bootable usb install media?

If you have copied the .iso file to a usb (which would have to be ntfs or exFAT formatted, it's too big for Fat32 to handle) then just copy the .iso file to the PC. Remove the usb then mount the ISO and run Setup.exe from the root of the drive to start the upgrade.

If you have a USB with the install media on it, then create a temporary folder on the PC's internal drive, copy all files and folders from the usb to the temporary folder. Remove the usb and run Setup.exe from that folder.


Should the upgrade still fail, upgrading from the ISO in this way provides two error codes: a result code and an extend code (unlike windows update or the update assistant which only give a result code). Note both codes, they can help to determine what caused the failure.

Thank-you for the Excellent straight-forward instructions that include reasons WHY things are done the way they are. Going to "mount" and execute the Media Creation Tool ISO image now to upgrade from Windows-10 ver 1909 to whatever this new one is ....20H I think. Weird name compared to past versions of Win10.

AllenChicago said:

Thank-you for the Excellent straight-forward instructions that include reasons WHY things are done the way they are. Going to "mount" and execute the Media Creation Tool ISO image now to upgrade from Windows-10 ver 1909 to whatever this new one is ....20H I think. Weird name compared to past versions of Win10.

Thank you, I try to include 'why' in my replies as well as 'how', "teach a man to fish...." as the saying goes.

1909 was released in month 09 of year '19. For 20H2 onwards Microsoft have changed the naming convention to say which half of the year it was released, H1 or H2.

Microsoft said:

With this release, we will also simplify our approach to numerical versions for Windows and move to a format that represents the half of the calendar year in which the release becomes available in retail and commercial channels. Windows 10, version 20H2 is, therefore, “20H2” because it will be released in the second half of the 2020 calendar year.

Microsoft announces what is next for Windows 10 updates

Thank-you for explaining how the new W10 naming conventions will work.

I'm finding that as Windows-10 advances, my primary PC (2009 HP Pavilion) begins to show its age to a greater degree.

It really became obvious when my wife purchased a new HP Laptop 3 months ago with an SSD Drive.

After doing the W10 update to 20H2 earlier this week, my PC will not boot all the way into Windows, unless I try two times. The first time, it just hangs at the blue Windows logo, with no spinning dots or hard drive activity. Have to hold the power button down for it to shut down. Then press it again and the PC boots normally to Win10.

I'm sure there is help for this problem posted somewhere in the forum. TenForums has consistently come through time and time again.

Happy holidays Bree,

Allen in Chicagoland