Let's install Windows 11 on incompatible hardware

spapakons · Oct 4, 2024

Quick hack: Search Registry for the version string and then replace 23H2 with 24H2 to make others believe you got it working on unsupported systems.

Just kidding of course...

hsehestedt · Oct 5, 2024

spapakons said:
Just kidding of course...

I like it anyway

spapakons · Oct 5, 2024

Once I had installed Windows 7 32-bit at a rather old PC and wanted to post a screenshot of the System Properties window. However the CPU was unknown and it was described as Family X Stepping Y and such. I found the CPU string in Registry and modified to the actual Intel Pentium III 700MHz so it would appear in the screenshot. Of course after restart the value was reset to the original string.

spapakons · Oct 6, 2024

I tried to upgrade my Fujitsu Stylistic Q702 hybrid tablet/laptop (see specs here: STYLISTIC Q702 - Fujitsu Indonesia) from 23H2 to 24H2 but first attempt failed because empty disk space on C: was about 12.5GB. I then uninstalled some large applications I hadn't used for a while and managed to increase the free disk space to 26GB. I tried again, now it didn't fail yet, let's hope it will succeed. I did the same steps as for my main PC. That is disable all startup applications, all non-Microsoft services and most devices not needed for the upgrade (LAN, wireless, Bluetooth, sound etc). I then opened a Command Prompt as Administrator, patched Registry with the following code, switched to E: (the Windows 11 24H2 setup USB) and started the upgrade:

Code:

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\HwReqChk" /f /v HwReqChkVars /t REG_MULTI_SZ /s , /d "SQ_SecureBootCapable=TRUE,SQ_SecureBootEnabled=TRUE,SQ_TpmVersion=2,SQ_RamMB=8192,"
reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
E:
setup /product server

Since the USB was patched by Rufus, the "server" trick might not be necessary, but I did it to be on the safe side. Of course I am disconnected from the internet until it is finished. I will let you know if I succeed.

spapakons · Oct 6, 2024

24H2 issues in my main PC (2nd system specs): It seems after the upgrade or when I connected to the internet again, my USB drivers were replaced. This had as a result my wireless USB dongle was not detected properly and it had difficulty connecting to my Wi-Fi or not detected by Windows at all. Even while properly connected to my Wi-Fi, when I connected a USB flash drive on another USB port it might lose my wireless USB dongle. I went to Device Manager and manually replaced the drivers for each USB Host controller to the INTEL version from the list, not the Microsoft provided version or the generic one. After doing that I restarted and now my USB works as expected. So if you experience compatibility issues with some device after upgrading to 24H2, reinstall your drivers. Some of them most likely has been replaced with a not very good one.

spapakons · Oct 6, 2024

spapakons said:
Quick hack: Search Registry for the version string and then replace 23H2 with 24H2 to make others believe you got it working on unsupported systems.

Just kidding of course...

Windows 11 on Pentium IIIe 700 MHz 384MB RAM.jpg

Windows 11 24H2 on Pentium III! How did you know it is a fake screenshot? Damn! I forgot to replace the Windows 7 logo!

spapakons · Oct 6, 2024

I successfully upgraded my unsupported Fujitsu Stylistic Q702 hybrid tablet/laptop from Windows 11 Pro 23H2 to 24H2 For specs see my earlier post.

LittleJay · Oct 7, 2024

antspants said:
This worked for me for an in-place upgrade to 24H2.

Work around for In-Place Upgrade to help RUFUS created USB install.

Command prompt as admin

Copy & paste each line one at a time into command window, press enter.

Then whilst in Windows, run setup.exe from RUFUS 24H2 install USB

Click on each line to copy to clipboard.

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL

reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL

reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\HwReqChk" /f /v HwReqChkVars /t REG_MULTI_SZ /s , /d "SQ_SecureBootCapable=TRUE,SQ_SecureBootEnabled=TRUE,SQ_TpmVersion=2,SQ_RamMB=8192,"
reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1

These will be added to the next version of RUFUS

Issue performing in-place upgrade to Windows 11 24H2 · Issue #2568 · pbatard/rufus

Checklist I have been made aware that if my problem can be summarized as "I've created or tried to create a media using Rufus, and ...", and I am not including a log, this issue will be summarily c...

github.com

Thank you for this! was able to upgrade both my PC and Laptop.

spapakons · Oct 7, 2024

Yes! Microsoft tries to discourage us upgrade our unsupported computers, but I don't currently have money to burn to buy a new one, even refurbished (I want something good, not for Office work), so I would rather keep my current computer as long as possible. I think most of you reading this thread do as well.

spapakons · Oct 8, 2024

Compatibility report: In my main PC (2nd system specs) I have Open Shell and Explorer Patcher installed to customize appearance. I have set Windows 7 start menu and start button and a lighter blue shade than default for the taskbar in Open Shell. I have set Windows 10 (ExplorerPatcher) style for the taskbar and to ungroup the power-network-sound icons so I can customize them (if grouped the default icons show instead). I noticed that after the upgrade to 24H2 the taskbar color might change to the darker default blue shade when I open an application and can return to the lighter blue shade if I open another. Not always, but it happens. Also if I switch from one application to another or I open a new application, the search icon and the "change desktop" icon next to it might disappear from the taskbar. To bring them back, I open Explorer Patcher settings or Windows taskbar settings and temporarily change to search box and back to search icon. Since Open Shell is no longer supported, hopefully a newer Explorer Patcher version will fix that. Not big deal, but annoying if I want to search something and the search icon has disappeared.

Bree · Oct 8, 2024

Bree said:
I have just done an in-place upgrade of the 23H2 on my unsupported System Two to today's official release of 24H2. I used hybrid install media, a 23H2 install USB with sources\install.esd replaced with the one from a 24H2 USB, so that I could still use the appraiserres workaround.

All went smoothly......

...until today. The Patch Tuesday cumulative update repeatedly failed to install with various errors.

I tried many things to rectify this, including resetting Windows Update. I think it may have been DISM's /RestoreHealth command that finally fixed it.

WAI · Oct 8, 2024

Help...

antspants · Oct 8, 2024

WAI said:
Help...

I think you might have to be running those commands through a CMD window as admin not a Powershell window.
I believe I tried the same and got the same results last week.

garlin · Oct 8, 2024

You can run the same commands without the output redirection ("2 > NUL").

PowerShell has a different syntax for doing redirection. "NUL" is a reserved filename in Windows, going back to DOS days.

antspants · Oct 8, 2024

WAI said:
Help...

View attachment 111674

That’s the RUFUS reg fixes, yes? … CMD not Powershell. Or change them as Garlin said.

I posted a batch script for them.

WAI · Oct 8, 2024

Why? I did as told here

antspants · Oct 8, 2024

WAI said:
Why? I did as told here

View attachment 111676

But that’s in Powershell not CMD window as admin

garlin said:
You can run the same commands without the output redirection ("2 > NUL").

PowerShell has a different syntax for doing redirection. "NUL" is a reserved filename in Windows, going back to DOS days.

dacrone · Oct 8, 2024

just run the same command in the same window you have open there and stop after the /f

WAI · Oct 8, 2024

Ohh..... I got it

Edit: Nope hmm..... be easier if you'd create reg files

garlin · Oct 8, 2024

Some people are running Windows, where your console app is conhost.exe (or "old CMD") and some people run Terminal.

For most people, PowerShell is the default shell for Terminal but you can change the setting and return it back to CMD as the shell. If your command prompt is "PS", then you're running PowerShell.

Let's install Windows 11 on incompatible hardware

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Like a rolling drone.

My Computers

Well-known member

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Similar threads