Solved In-place upgrade - Setup Self host crashes

BrianInEngland · Nov 18, 2023

I'm trying to do an in-place/repair using the latest ISO. It gets as far as the 'Please wait' stage after checking for updates, then crashes.
Error is showing as Modern Setup host stopped working.

This happened with the RP 22631.2361 ISO, I thought it would be fine with the 22631.2715 ISO.

ISO was downloaded using the latest MCT, using the EN-GB version.

POLYSIUS · Nov 18, 2023

Try to disconnect from Internet first.

BrianInEngland · Nov 18, 2023

POLYSIUS said:
Try to disconnect from Internet first.

Nope, no change.

BrianInEngland · Nov 18, 2023

Had this problem with .2361 and now .2715. The May ISO 22621.1702 works fine

Ghot · Nov 18, 2023

BrianInEngland said:
Had this problem with .2361 and now .2715. The May ISO 22621.1702 works fine

Might be easier to just do the .1702, then do updates, then do the Enablement package.

Or.... we could just go...

The Windows Updates are cumulative, so there shouldn't be more than about 3 updates.
Security, .NET Framework, and some Defender definitions.
And maybe good old KB4023057.

BrianInEngland · Nov 18, 2023

Ghot said:
Might be easier to just do the .1702, then do updates, then do the Enablement package.

Or.... we could just go...

View attachment 78247

The Windows Updates are cumulative, so there shouldn't be more than about 3 updates.
Security, .NET Framework, and some Defender definitions.
And maybe good old KB4023057.

Yeah a downgrade then upgrade! Weird that I'm running 23H2 but only a 22H2 ISO will work.

Are there likely to be any issues doing what you suggest?

Another idea I had would be to use a 22H2 ISO but replace the install.esd (or .wim) with the 22631.2715 one - would this work?

Any suggestions from @Brink ?

Ghot · Nov 18, 2023

BrianInEngland said:
Are there likely to be any issues doing what you suggest?

Not that I can think of.
Your ideas sound good as well.
I always try to keep things basic... but that's just me.

BrianInEngland · Nov 18, 2023

Ghot said:
Not that I can think of.
Your ideas sound good as well.
I always try to keep things basic... but that's just me.

I like the easy options too, but when they don't work a Plan B comes in useful...
I might try an in-place upgrade using my idea (switching the install.wim file with the newer one)

Ghot · Nov 18, 2023

BrianInEngland said:
I like the easy options too, but when they don't work a Plan B comes in useful...
I might try an in-place upgrade using my idea (switching the install.wim file with the newer one)

I've got my fingers crossed.

As long as you have a backup though... you can "try" whatever you like.

BrianInEngland · Nov 18, 2023

Ghot said:
I've got my fingers crossed.

As long as you have a backup though... you can "try" whatever you like.

Of course, regular backups using Macrium

The 'hybrid' ISO idea has been done using a Windows 10 image but with a Windows 11 install.wim as a way to bypass compliance checks. If I get chance to try it this coming week I'll post back here with the results

spapakons · Nov 18, 2023

BrianInEngland said:
Yeah a downgrade then upgrade! Weird that I'm running 23H2 but only a 22H2 ISO will work.

Are there likely to be any issues doing what you suggest?

Another idea I had would be to use a 22H2 ISO but replace the install.esd (or .wim) with the 22631.2715 one - would this work?

Any suggestions from @Brink ?

It makes sense. If you install the 23H2 Enablement Package, you are still in 22H2 with the 23H2 features enabled. Most system files don't change and have the 22H2 version mark. So you can upgrade/repair using the 22H2 ISO only, not the 23H2 one. If you have done a proper upgrade, that is you have run Setup from the 23H2 ISO, then the system files should have the 23H2 version mark, so you can do an in-place upgrade repair using the 23H2 ISO. Just have this in mind so you have the appropriate ISO handy. Of course after a repair with the 22H2 ISO you have to reinstall the 23H2 Enablement Package, or do q second upgrade using the 23H2 ISO to get 23H2.

POLYSIUS · Nov 19, 2023

My old workinghorse, a HP Z420 WS with TPM 1.2, a nonsupported CPU and SMBIOS 2.7 got a clean install in August.
I used a WIN 10 19045.3570 ISO and exchanged the install.wim from a 22621.1848.
The setup ran without any interruption. Today im on 22621.2715. Till now I didn't try the Enablement Package.

BrianInEngland · Nov 19, 2023

spapakons said:
It makes sense. If you install the 23H2 Enablement Package, you are still in 22H2 with the 23H2 features enabled. Most system files don't change and have the 22H2 version mark. So you can upgrade/repair using the 22H2 ISO only, not the 23H2 one. If you have done a proper upgrade, that is you have run Setup from the 23H2 ISO, then the system files should have the 23H2 version mark, so you can do an in-place upgrade repair using the 23H2 ISO. Just have this in mind so you have the appropriate ISO handy. Of course after a repair with the 22H2 ISO you have to reinstall the 23H2 Enablement Package, or do q second upgrade using the 23H2 ISO to get 23H2.

That makes no sense - how many users have gone from 22H2 to 23H2 using the enablement package?
What do you mean by 'proper' upgrade? A clean install?
Surely it's possible to go from 22H2 to 23H2 using a newer ISO?

Has anyone else encountered this?

spapakons · Nov 19, 2023

The 23H2 Enablement Package makes some changes, probably in Registry, enables the 23H2 features and switches to version 23H2. It doesn't replace all system files. A proper upgrade, that is to actually run Setup and go through all the process of replacing all the system files is different. Now it should make more sense to you.

BrianInEngland · Nov 19, 2023

spapakons said:
The 23H2 Enablement Package makes some changes, probably in Registry, enables the 23H2 features and switches to version 23H2. It doesn't replace all system files. A proper upgrade, that is to actually run Setup and go through all the process of replacing all the system files is different. Now it should make more sense to you.

So that's a clean install? I always thought an upgrade install replaces all the files anyway as it writes a new Windows image to the disk. I could try removing the enablement package and see if it runs the upgrade then

How is my issue different from going from Windows 21H2 to 22H2 using an ISO or from Windows 10 to Windows 11?

spapakons · Nov 19, 2023

A clean installation means to delete all your data and do a new Windows 11 system. A proper upgrade is to keep your data and applications and replace all system files. The Enablement Package changes the version without replacing all the files. I think the difference is clear.

Ghot · Nov 19, 2023

BrianInEngland said:
That makes no sense - how many users have gone from 22H2 to 23H2 using the enablement package?
What do you mean by 'proper' upgrade? A clean install?
Surely it's possible to go from 22H2 to 23H2 using a newer ISO?

Has anyone else encountered this?

@Bree did it with an ISO image and the Enablement Package

I just used the Enablement Package. Takes about 3-4 seconds.
23H2 was installed before the Enablement Package was released.
The EP just toggles the features in 23H2, to ON.

BrianInEngland · Nov 19, 2023

spapakons said:
A clean installation means to delete all your data and do a new Windows 11 system. A proper upgrade is to keep your data and applications and replace all system files. The Enablement Package changes the version without replacing all the files. I think the difference is clear.

It's clear but I'm running Setup from the ISO, it fails. I am actually trying to do what you describe but Setup crashes

spapakons · Nov 19, 2023

It fails because you are connected to the internet and a hidden compatibility check disrupts the upgrade. Try disconnecting from the internet during the upgrade.

BrianInEngland · Nov 19, 2023

spapakons said:
It fails because you are connected to the internet and a hidden compatibility check disrupts the upgrade. Try disconnecting from the internet during the upgrade.

Done that, didn't work. All I want to do is a Repair install using the ISO, something I've done many times before.
Run Setup.exe, wait 20-30 minutes, login again. Repair done. It's never failed me until I used 23H2 ISOs