Solved In-place upgrade - Setup Self host crashes

POLYSIUS · Nov 19, 2023

POLYSIUS said:
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.

So, I have tried the Enablement Package, being already released as windows11.0-kb5027397-x64.cab in September!

It took 3 seconds, a reboot and the expected result is there.

BrianInEngland · Nov 19, 2023

POLYSIUS said:
So, I have tried the Enablement Package, being already released as windows11.0-kb5027397-x64.cab in September!
View attachment 78334

It took 3 seconds, a reboot and the expected result is there.

Cool, so I can use the (working) 22H2 ISO I have, replace the install.esd with the 22631.2715 one, and do a repair install

I have the Enablement pack downloaded if I need it after - I thought the new ISO automatically puts 23H2 on?

spapakons · Nov 19, 2023

Whatever works for everyone. Try the Enablement Package first and if it doesn't work use the ISO.

BrianInEngland · Nov 19, 2023

spapakons said:
Whatever works for everyone. Try the Enablement Package first and if it doesn't work use the ISO.

I'm already running 22631.2787 (updates through WU and the enablement came from there). That's why I don't understand why a 23H2 ISO won't run on a 23H2 system, but I can use an older 22H2 ISO.

spapakons · Nov 19, 2023

I just checked for updates, the official release build is 22531.2715 you probably have an Insider's version (Canary or Dev).

BrianInEngland · Nov 19, 2023

spapakons said:
I just checked for updates, the official release build is 22531.2715 you probably have an Insider's version (Canary or Dev).

Release Preview

BrianInEngland · Nov 19, 2023

What would likely happen if I tried this?

spapakons · Nov 19, 2023

This works on Windows 11 compliant systems only. Unsupported computers should not use it.

Ghot · Nov 19, 2023

BrianInEngland said:
What would likely happen if I tried this?

The UK would sink into the sea!

That's hard to answer. Sometimes, when dealing with MS and their updates, upgrades, whatever... things happen that we don't expect. You're asking us to predict the future on a computer we don't own or have in front of us.
A future from a company whose left hand doesn't know what the right hand is doing.

Try it and "see" what happens.
Then, when the next person asks, you can say: "The last time I did that, the UK sank into the sea", or whatever.

This is why we make those backups... so we can experiment.

BrianInEngland · Nov 19, 2023

spapakons said:
This works on Windows 11 compliant systems only. Unsupported computers should not use it.

I'm already running Windows 11 on a compliant system, I'm just wondering if this would work when the ISO doesn't

spapakons · Nov 19, 2023

Most likely yes. I could not upgrade from one Windows 10 version to a newer one time. Using the Upgrade Assistant completed the upgrade successfully. Go for it.

BrianInEngland · Nov 19, 2023

Now this is interesting. I did the 'fake' AppraiserRes.dll trick, replacing that file in the Sources folder with a blank/fake one.
It worked! I got as far as the 'Choose what to keep' screen where I could begin installation, I aborted there as I don't want to do it right now.

Ironic that my PC is hardware compliant (including TPM) but to get the 23H2 ISO to work I have to do the trick for a non-compliant install

The plot thickens, must be a bug relating to TPM checking. I'm using the AMD fTPM BIOS setting.

spapakons · Nov 19, 2023

Or simply some system files are 22H2, some are 23H2 confusing the compatibility check. Removing this check just ignored these differences and proceeded with the upgrade. Most of these files will be replaced anyway.

BrianInEngland · Nov 19, 2023

spapakons said:
Or simply some system files are 22H2, some are 23H2 confusing the compatibility check. Removing this check just ignored these differences and proceeded with the upgrade. Most of these files will be replaced anyway.

I tested twice just to make sure, I now have a 'proper' 23H2 ISO I can use to do a Repair install with

BrianInEngland · Nov 19, 2023

spapakons said:
Or simply some system files are 22H2, some are 23H2 confusing the compatibility check. Removing this check just ignored these differences and proceeded with the upgrade. Most of these files will be replaced anyway.

My 22H2 ISO also had the 'fake' Appraiser file, so I don't know if that's why that one worked and the 23H2 one didn't until I used the file.

Ghot · Nov 19, 2023

BrianInEngland said:
I tested twice just to make sure, I now have a 'proper' 23H2 ISO I can use to do a Repair install with

You have now been awarded, the...

spapakons · Nov 19, 2023

You earned yourself a "golden tofu", as we say in Greek for rewarding something not so important. That's a non-existing award for non-existing achievement.

Ghot · Nov 19, 2023

spapakons said:
You earned yourself a "golden tofu", as we say in Greek for rewarding something not so important.

It's all relative.

BrianInEngland · Nov 20, 2023

spapakons said:
You earned yourself a "golden tofu", as we say in Greek for rewarding something not so important. That's a non-existing award for non-existing achievement.

Well it was helpful to me, I solved a problem myself!

Almighty1 · Nov 20, 2023

BrianInEngland said:
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?

Not the same, even if all files are replaced, your existing registry is not replaced except for certain keys assuming we are not talking about apps and data.