Let's install Windows 11 on incompatible hardware

lafargeotte · Sep 21, 2022

At w

pietcorus2 said:
" I downloaded the ISO from Microsoft, mounted it and run Setup. Before proceeding I replaced the file with an empty dummy. "...........yep , open the appraiserres.dll with txt.exe , remove all the text in it , safe it .
This file is now empty , replace the original in sources ..............

hat point in the process did you replace the file.

spapakons · Sep 21, 2022

I will try again some other time. Unless I upgrade successfully at least 2-3 non-compliant computers, I would not dare try it on my main computer. Clean installation will probably work, but I certainly don't want to do all the trouble of backup/restore my data and reinstall all my applications again from start! I would rather try the upgrade on a virtual machine or a computer I wouldn't mind to format if something goes wrong.

spapakons · Sep 21, 2022

I just realized I tried the upgrade with the internet connected. Another poster mentioned that he disconnected from the internet before upgrading. I don't have time now, but I will retry without internet to see what happens.

pietcorus2 · Sep 21, 2022

Yes , no internet.........or you get driver-updates also , which you may not want...............

mccnavy · Sep 21, 2022

Depending on what the "incompabtibility" is for your system, I was able to get my wife's to update (using iso) after adding the CPUTPM update skip check to the registry.

wordsworth · Sep 21, 2022

Just finished successfully installing 22 H2 to the non-compatible system using the appraiserres.dll trick. First time I received a message that Windows could not discover the system specs; upon looking at the file I realized I'd misspelled the file when re-naming it as appraserres without the i as it does appraise the system not appras the system, LOL. All is well here anyway.

spapakons · Sep 22, 2022

I disabled Wi-fi , cleanef up the disk and tried again. Unfortunately it failed again with a message. I won't risk it to damage Windows. I will wait for a new update to increase the build number and try again some other day.

pietcorus2 · Sep 22, 2022

" some other day. "................right you are !
Why hurry while you can use this 21H2 untill next year October ?
By then we have another OS again............

spapakons · Sep 22, 2022

99.99% a clean installation will work, but I would rather avoid all that trouble.

pietcorus2 · Sep 22, 2022

" I would rather avoid all that trouble. "............yep , its not worth the stress , time and work ( at least ; for this upgrade ).........

Bree · Sep 22, 2022

wordsworth said:
upon looking at the file I realized I'd misspelled the file when re-naming it as appraserres without the i as it does appraise the system not appras the system, LOL. All is well here anyway.

It's an unintuitive spelling - I got it wrong three times in a row on one of my machines! :lmao:

lafargeotte · Sep 22, 2022

Bree said:
My non-compatible System Two is stewing at 11 Pro version 22H2, 22621.382 now, with the KB5017321 .521 CU consistently failing with error 0x800f0806.

This is by no means the first time an update has failed in this way, for 10 or 11. In my experience it seems to be specific to just the one particular update, a misconfiguration, or files missing at the server end. All other updates are unaffected. Since the ISO upgrade to 22H2 22621.382 I've already seen a sucessful KB5017026 .NET update and three Definition updates.

I'll leave it stewing like this to see if MS fix it at their end or, as is more usual, leave it as it is until it's superseded by a newer CU.

Did you resolve this?

wordsworth · Sep 22, 2022

Bree said:
It's an unintuitive spelling - I got it wrong three times in a row on one of my machines!

I had one slap to the forehead, but three I'd be getting a headache!

Bree · Sep 22, 2022

lafargeotte said:
Did you resolve this?

It's not for me to resolve, the fault seems to be with Microsoft on their update servers. I've tried everything possible at my end with no effect. All other updates are fine, so Windows Update appears to be fully working at my end.

The workaround is simple, just get the CU from the MS Update Catalog and do a manual install. I've done that for my other upsupported devices, but I'm leaving this one machine as it is to see if/when MS get round to fixing this at their end.

lafargeotte · Sep 22, 2022

Bree said:
It's not for me to resolve, the fault seems to be with Microsoft on their update servers. I've tried everything possible at my end with no effect. All other updates are fine, so Windows Update appears to be fully working at my end.

The workaround is simple, just get the CU from the MS Update Catalog and do a manual install. I've done that for my other upsupported devices, but I'm leaving this one machine as it is to see if/when MS get round to fixing this at their end.

I just wondered if it was anything to do with recovery partitions.

WAI · Sep 22, 2022

Is it me or did RuFus remove the bypass option bc I had to DL 3.18p where 3.20p didn't have it

Try3 · Sep 22, 2022

Bree said:
I have now successfully upgraded ... devices with a 22H2 ISO

Since I'm letting my only Windows 11 computer stew for a while, would you mind running
ReportOSVersion.bat post - TenForums
to check that it still works in 22H2 [as it did with 22H1]?

All the best,
Denis

Bree · Sep 22, 2022

Try3 said:
Since I'm letting my only Windows 11 computer stew for a while, would you mind running
ReportOSVersion.bat post - TenForums
to check that it still works in 22H2 [as it did with 22H1]?

Here you go.....