Let's install Windows 11 on incompatible hardware

idgat · Sep 30, 2022

Just did a 2H22 clean install on a (not so old, but ....) non-compliant HP laptop

Created Macrium Reflect image of existing system
Then, with 2 tin foil hats on, ran AOMEI Backupper for another image, just in case

Downloaded
- Rufus 3.2
- Windows 11 2H22 ISO

Created boot Rufus USB, ticked Rufus offer of every option to bypass MS ersatz security pretences

Disconnected the internet

Installed W11, no probs ... until ....

Every drive/partition Win 11 can get its grotty little paws on was encrypted. Decryption (manage-bde etc) was possible, just a PITA to have to do.

Ran updates (incl KB5017321), next reboot, (error?) message = need to change your password – WTF! It was a local account installation, and there never is/was a password to change!!! And it wouldn't accept any change (I just used a random 1234 new password) because no original password existed to prove it was moi – as a consequence only a Cancel button was offered

Can't remember how I got around it, but eventually got it to accept blank field new password and I haven't been bothered by it since (Just waiting for another major update to see what some pretentious prat at Redmond adds to W11 to throw back in my face. It's a bloody good OS, I just wish they'd stop tinkering and tampering).

Running smoothly, updating as should, etc

EDIT : Can't see the point in the layout change of Task Manager. Someone at Redmond has too much time on his/her hands.

junglee · Sep 30, 2022

spapakons said:
You are little ahead of the general release. Remember that no update checks compatibility, they all download and install like if you have a compliant computer. Only upgrades to a newer version check compatibility and need replacing the appraiserres.dll file with an empty dummy to install.

Thank you for your extremely prompt reply. You might have read the excellent blog by Chris Hofmann on how to install Windows 11 on an unsupported PC at How to Install Windows 11 on an Unsupported PC. My Laptop fulfils all the parameters except for having a non-compliant CPU. This blog gives a registry hack to make the newer version update ignore the compatibility check for CPU and treat the PC as a regular PC. Additionally the blog has given a link to two files that can apply and un-apply the hacks when clicked. In that case the need for replacing the appraiserres.dll file with an empty dummy would not arise. What do you think?

spapakons · Sep 30, 2022

If you format your hard disk to install Windows 11 (clean installation), then you either use the Registry hacks, or a script (.bat file) that patches Registry automatically. A third workaround is to use a hybrid Windows 10/11 USB flash drive. This is a regular Windows 10 USB flash drive with the file \sources\install.esd or \sources\install.wim replaced by the respective file from the Windows 11 ISO. This has as a result to use Windows 10 installer that doesn't check any compatibility to install Windows 11 instead. If you create it in NTFS MBR Legacy BIOS mode it always works for any computer that can run at least Windows 8 64-bit (the CPU has the required instructions and the RAM is at least 1GB).

If you already have Windows 8.1 or 10 64-bit or Windows 11 installed and you want to upgrade to the same build (in-place upgrade, repair) or a newer version of Windows 11, then you need to replace the hidden file C:\$Windows.~BT\sources\appraiserres.dll with an empty dummy to bypass compatibility check before proceeding with the installation. To reduce the risk of anything interrupting the upgrade and fail, I disable all non-Microsoft services and startup applications, I disable Windows Defender or any other antivirus and also disconnect from the internet. In the first setup screen I choose NOT to run Windows Update during installation.

mackie · Sep 30, 2022

I just did an upgrade on this unsupported pc from 21H2 to 22H2.

I'm running multiple OS's on this pc and didn't want to have to go through the hassle of recreating everything all over again, so I did the upgrade
as described in the youtube video below. It was very easy.

On this old pc, it took 55 minutes, end-to-end.

When the install finished, I had 22H2 with OS Build 22621.525.

I clicked on WU and was offered (.NET) KB5017271 and (CU) KB5017389.

After they finished installing, I'm at OS Build 22621.608.

erpster4 · Sep 30, 2022

idgat said:
Downloaded
- Rufus 3.2
- Windows 11 2H22 ISO

when did you download the Windows 11 22H2 ISO, idgat? if you downloaded that ISO before Thursday Sept. 29, download it again because Microsoft quietly posted "refreshed" or re-released 22H2 ISOs that contain build 22621.525 instead of 22621.382 (ex. "original" 22H2 ISO > Win11_22H2_English_x64.iso; revised 22H2 ISO > Win11_22H2_English_x64v1.iso)

Bree said:
The oldest machine I have installed Windows 11 is my System Two in My Computers below, a Dell Latitude E4310. It is 12 years old, built in October 2010, and has a 1st gen i5 processor.

I do use it for Video calls, before upgrading from Win10 it was the only machine I had installed Zoom on. Now it's on Win11 22H2, 22621.521 it is still the only one I use for Zoom conference calls.

the 22621.521 build is now outdated, Bree
as the "revised" 22H2 ISOs contain build 22621.525; re-install using in-place upgrade with the newly revised 22H2 ISOs {seems MS publicly released 22H2 a little too prematurely on 9/20 with some serious bugs and had to post newly refreshed ISOs to resolve some of those problems}

Scott · Sep 30, 2022

mackie said:
and (CU) KB5017389.

After they finished installing, I'm at OS Build 22621.608.

Looks like that CU just came out today.

mackie · Sep 30, 2022

Scott said:
Looks like that CU just came out today.

I finished the upgrade a little over an hour ago. It sounds like it.

Bree · Sep 30, 2022

erpster4 said:
the 22621.521 build is now outdated, Bree

The only difference between 22621.521 and 22621.525 is just the one fix - and that's for an issue that only affects non-English installs. So not really an issue for me :wink:

Addresses localization issues for some setup files. These issues might stop you from creating installation media for non-English languages.

KB5019311 Cumulative Update for Windows 11 Build 22621.525 (22H2) - Sept. 27

September 27, 2022 - KB5019311 (OS Build 22621.525) Out-of-band For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. Note Follow @WindowsUpdate to find out when new content is published to the Windows release...

www.elevenforum.com

Anyway, that's academic now that both 22621.521 and 22621.525 are outdated :wink:

September 30, 2022—KB5017389 (OS Build 22621.608) Preview - Microsoft Support

support.microsoft.com

idgat · Sep 30, 2022

erpster4 said:
when did you download the Windows 11 22H2 ISO, idgat? if you downloaded that ISO before Thursday Sept. 29, download it again because Microsoft quietly posted "refreshed" or re-released 22H2 ISOs that contain build 22621.525 instead of 22621.382 (ex. "original" 22H2 ISO > Win11_22H2_English_x64.iso; revised 22H2 ISO > Win11_22H2_English_x64v1.iso)

the 22621.521 build is now outdated, Bree
as the "revised" 22H2 ISOs contain build 22621.525; re-install using in-place upgrade with the newly revised 22H2 ISOs {seems MS publicly released 22H2 a little too prematurely on 9/20 with some serious bugs and had to post newly refreshed ISOs to resolve some of those problems}

Also currently sitting on .521 Good enough for me at the moment, for the time being. I've actually got some work to do over the next couple days so not going to tempt fate with any update/upgrade. I was dead keen and-curious to tinker and tamper with 22H2 on this "non-compliant" device (HP laptop), but not so 4n4l as to want dot perfect version, at the moment.

idgat · Sep 30, 2022

Bree said:
Anyway, that's academic now that both 22621.521 and 22621.525 are outdated

September 30, 2022—KB5017389 (OS Build 22621.608) Preview - Microsoft Support

support.microsoft.com

LOL ... and by the time I/we get around to .608 it'll be time for .7xx to be released :eyeroll:

EDIT

Ooh, lookit the present those kind people at Microsoft just sent to me ...

2022-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5017389)
Downloading 21% (and counting)

Alexey2912 · Sep 30, 2022

@idgat , are you installing, using bypass TPM, secure boot in registry during install?

Thanks.

idgat · Sep 30, 2022

Alexey2912 said:
@idgat , are you installing, using bypass TPM, secure boot in registry during install?

Thanks.

Yep (at least I think so. I'm now doing other devices (some straight MCT, some Rufus bypassing) so my memory's getting a befuddled about what I did with what devices :boom:

Alexey2912 · Sep 30, 2022

idgat said:
Yep (at least I think so. I'm now doing other devices (some straight MCT, some Rufus bypassing) so my memory's getting a befuddled about what I did with what devices

Great, thanks for replying. Can one install W11 on a compatible system without secure boot, TPM etc. Any advantages?

Apologize, my own memory was full...MCT media creation tool....

Bree · Sep 30, 2022

Alexey2912 said:
are you installing, using bypass TPM, secure boot in registry during install?

there are no system checks for a CU, both supported and unsupported devices will be offered them in Windows Update, and will download and install them successfully.

It's only a feature update that checks hardware compatibility. Unsupported devices on 21H2 won't be offered 22H2, and if you try an in-place upgrade from 21H2 to 22H2 then you need to use a workaround, else that will fail on the system checks.

Alexey2912 · Sep 30, 2022

Bree said:
there are no system checks for a CU, both supported and unsupported devices will be offered them in Windows Update, and will download and install them successfully.

It's only a feature update that checks hardware compatibility. Unsupported devices on 21H2 won't be offered 22H2, and if you try an in-place upgrade from 21H2 to 22H2 then you need to use a workaround, else that will fail on the system checks.

Thanks @Bree , I was thinking that disabling TMP, secure boot on might have some advantages on my laptop?

WAI · Sep 30, 2022

Easy thing is to DL the image and with Rufus with the bypass and create a USB then when done double click on the setup file

spapakons · Oct 1, 2022

There is no need to download a newer 22H2 ISO and do an in-place upgrade just to get the latest build. All you have to do is install all the available updates from Windows Update. Much less risky and doesn't check compatibility on unsupported computers.

No there is no difference between installing "vanilla" (without any hacks) and applying the hacks on a compliant computer. The hacks bypass compatibility check, all components are installed in both cases, so performance and features available should be identical. I would use the hacks on a compliant computer only if I wanted to do a legacy installation instead of the default UEFI installation in order to avoid the multiple small partitions and maximize disk space on a small SSD.

junglee · Oct 1, 2022

erpster4 said:
when did you download the Windows 11 22H2 ISO, idgat? if you downloaded that ISO before Thursday Sept. 29, download it again because Microsoft quietly posted "refreshed" or re-released 22H2 ISOs that contain build 22621.525 instead of 22621.382 (ex. "original" 22H2 ISO > Win11_22H2_English_x64.iso; revised 22H2 ISO > Win11_22H2_English_x64v1.iso)

the 22621.521 build is now outdated, Bree
as the "revised" 22H2 ISOs contain build 22621.525; re-install using in-place upgrade with the newly revised 22H2 ISOs {seems MS publicly released 22H2 a little too prematurely on 9/20 with some serious bugs and had to post newly refreshed ISOs to resolve some of those problems}

Even 22621.521 was outdated weeks ago. The current version is 22623.730.

Bree · Oct 1, 2022

junglee said:
Even 22621.521 was outdated weeks ago. The current version is 22623.730.

Not for the General Availability Channel it isn't, that's 22621.608 now.
Your 22623.730 is the current build for the Insider Beta Channel.

enite · Oct 1, 2022

Hello guys and girls, I think I have a problem that nobody have before on upgrading Windows 11 21H2 to 22H2 on unsupported hardware. Dispite my efforts, I can't migrate to 22H2. I already backup and replace the appraiserres.dll with blank file or modify file from the youtube link of Mackie and unfortunately in both cases, I can't make it to the final screen. I can bypass TPM/CPU/Secure Boot incompatibility, I access the licence agreements but in the final screen, Windows says that they don't know if the computer can support 22H2. I also tried with Rufus but same issue. I check on few forums but I can't find the same issue (or, I didn't look this well ^_^ ). Finally, sorry for my poor english, I'm French (sorry about that too ^_^). Thank you, best regards :wink: