Updated PC from Win10 to Win11 on unsupported HW 5 months ago, windows update saying I have unsupported HW


E

epete

Active member
Local time
11:35 PM
Posts
7
OS
Windows 11,
I followed this video to update my PC to Win11


I have been through multiple iterations of Windows Update with no problems. Somehow Windows update wanted to install "Windows 11, version 24H2 (repair version)" and this update is now complaining my hardware does not support.

I am wondering if anyone else has experienced this and if there is a solution.
 

My Computer My Computer

At a glance

Windows 11,
OS
Windows 11,
epete said:
I have been through multiple iterations of Windows Update with no problems. Somehow Windows update wanted to install "Windows 11, version 24H2 (repair version)" and this update is now complaining my hardware does not support.

I am wondering if anyone else has experienced this and if there is a solution.
Click to expand...
Welcome to Eleven Forum.

I've not seen Windows Update spontaneously decide you need an in-place repair upgrade, on supported or unsupported devices. But I have deliberately started one on an unsupported device to "Fix problems using Windows Update". Using the workaround below it completed successfully.

Cumulative updates will install without hardware checks on unsupported devices. But an upgrade to 24H2, whether from 23H2 or a repair upgrade like this, will always check for hardware compatibility.

Run the registry commands from Option Three in this tutorial before letting Windows Update retry the upgrade.

www.elevenforum.com

Bypass Windows 11 System Requirements on Unsupported PC

This tutorial will show you how to bypass the Windows 11 CPU, RAM, Secure Boot, and TPM 2.0 system requirements allowing you to clean install or upgrade to Windows 11 on a unsupported PC that doesn't meet these requirements. Installing Windows 11 on a device that does not meet Windows 11...
www.elevenforum.com www.elevenforum.com
 

My Computers My Computers

System One System Two Other systems

  • At a glance

    Windows 11 HomeAMD Athlon Silver 3050U8GBRadeon Graphics
    OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23-R9VY
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD (from April 2026: 250GB EVO 850)
    Internet Speed
    150 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2, and 25H2 on 30th September 2025 through Windows Update by setting the Target Release Version for 25H2.

    UPDATE - 11 April 2026: due to mechanical deterioration this PC has been retired from active duty. The OS with all software and files has been migrated to my System Seven in 'Other systems' to carry on as my general purpose 'main machine'.

    I've now clean installed 25H2 and used Garlin's scripts to update Secure Boot to CA 2023 and revoke the PCA 2011 certificates. It's new role is to test secure boot issues.

  • At a glance

    Windows 11 ProIntel® Core™ i5-520M8GB(integrated graphics) Intel HD Graphics
    Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround.

    In-place upgrade to 22H2 using ISO and a workaround.
    Feature Update to 23H2 by manually installing the Enablement Package.
    In-place upgrade to 24H2 using hybrid 23H2/24H2 install media.
    Upgraded to 25H2 by Enablement Package.

    Also running Insider Dev, and Canary builds and Windows 10 as native boot .vhdx.
  • My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 1TB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.

    My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine. Updated to 25H2 on 30th September 2025.

    My SYSTEM SEVEN is a Lenovo Thinkpad T580, Intel Core i7-8650U, 16GB RAM, 512GB NVMe SSD + 2nd 512GB NVMe SSD, a supported device for Windows 11. This is my current general purpose 'main machine'. The installed Windows 11 Home from my System One has been migrated to this machine.
When Running Terminal (Admin); it didnt seem to like the first 3 commands that I pasted in.

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
The operation completed successfully.
 

My Computer My Computer

At a glance

Windows 11,
OS
Windows 11,
epete said:
When Running Terminal (Admin); it didnt seem to like the first 3 commands that I pasted in.

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
out-file : FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the
FileStream constructors that take an OS handle as an IntPtr.
At line:1 char:1
+ reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\App ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (:) [Out-File], NotSupportedException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\Users\Basement> reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
The operation completed successfully.
Click to expand...

I'm a newb here...and maybe you know this... but as a programmer, it appears that the command is complaining about your output from the reg process to NUL. So it's either a syntax error or it doesn't like the device name. Something like that.
 

My Computer My Computer

At a glance

Windows 11 Pro 24H2Intel Ultra 7 155H16gbIntel Arc integrated
OS
Windows 11 Pro 24H2
Computer type
Laptop
Manufacturer/Model
HP
CPU
Intel Ultra 7 155H
Memory
16gb
Graphics Card(s)
Intel Arc integrated
Hard Drives
SSD
epete said:
When Running Terminal (Admin); it didnt seem to like the first 3 commands that I pasted in.
Click to expand...
Levitate11 said:
as a programmer, it appears that the command is complaining about your output from the reg process to NUL.
Click to expand...
Correct, it is a syntax error. The reason is that @epete skipped the last part of instruction 1 from the tutorial:
"Open Windows Terminal (Admin), and select Command Prompt."

Redirection to NUL is valid syntax for a command prompt, but not in Powershell where you tried to run the command.

The 2>NUL is actually just there to keep the output tidy, it redirects any error output away from the screen. It's not strictly needed and can be left off the command if run in Powershell.
 

My Computers My Computers

System One System Two Other systems

  • At a glance

    Windows 11 HomeAMD Athlon Silver 3050U8GBRadeon Graphics
    OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23-R9VY
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD (from April 2026: 250GB EVO 850)
    Internet Speed
    150 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2, and 25H2 on 30th September 2025 through Windows Update by setting the Target Release Version for 25H2.

    UPDATE - 11 April 2026: due to mechanical deterioration this PC has been retired from active duty. The OS with all software and files has been migrated to my System Seven in 'Other systems' to carry on as my general purpose 'main machine'.

    I've now clean installed 25H2 and used Garlin's scripts to update Secure Boot to CA 2023 and revoke the PCA 2011 certificates. It's new role is to test secure boot issues.

  • At a glance

    Windows 11 ProIntel® Core™ i5-520M8GB(integrated graphics) Intel HD Graphics
    Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround.

    In-place upgrade to 22H2 using ISO and a workaround.
    Feature Update to 23H2 by manually installing the Enablement Package.
    In-place upgrade to 24H2 using hybrid 23H2/24H2 install media.
    Upgraded to 25H2 by Enablement Package.

    Also running Insider Dev, and Canary builds and Windows 10 as native boot .vhdx.
  • My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 1TB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.

    My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine. Updated to 25H2 on 30th September 2025.

    My SYSTEM SEVEN is a Lenovo Thinkpad T580, Intel Core i7-8650U, 16GB RAM, 512GB NVMe SSD + 2nd 512GB NVMe SSD, a supported device for Windows 11. This is my current general purpose 'main machine'. The installed Windows 11 Home from my System One has been migrated to this machine.
I was at the Redmond campus a few weeks ago and there was talk of starting to enforce Win 11 24H2 requirements by having WU check TPM/CPU before letting updates install.

Windows 11 on devices that don't meet minimum system requirements | Microsoft Support

Installing Windows 11 on devices that do not meet minimum system requirements is unsupported and is not recommended by Microsoft.
support.microsoft.com support.microsoft.com

learn.microsoft.com

Windows processor requirements Windows 11, version 24H2 supported Intel processors

This specification details the Intel processors that can be used with Windows 11, version 24H2 customer systems that include Windows products, including custom images.
learn.microsoft.com

learn.microsoft.com

Windows processor requirements Windows 11, version 24H2 supported AMD processors

This specification details the AMD processors that can be used with Windows 11, version 24H2 customer systems that include Windows products, including custom images.
learn.microsoft.com
 

My Computer My Computer

At a glance

Windows 11 Pro
OS
Windows 11 Pro
KevTech said:
I was at the Redmond campus a few weeks ago and there was talk of starting to enforce Win 11 24H2 requirements by having WU check TPM/CPU before letting updates install.
Click to expand...
I would assume the WU team isn't going to write their own TPM/CPU check from scratch, and will use the existing AppCompatFlags. If you were to disable the AppCompat scheduled task to refresh the keys, and clear them, WU wouldn't know the difference.

Of course, they could also make Update Medic protect the task from being disabled...
 

My Computer My Computer

At a glance

Windows 7
OS
Windows 7
KevTech said:
I was at the Redmond campus a few weeks ago and there was talk of starting to enforce Win 11 24H2 requirements by having WU check TPM/CPU before letting updates install.

Windows 11 on devices that don't meet minimum system requirements | Microsoft Support

Installing Windows 11 on devices that do not meet minimum system requirements is unsupported and is not recommended by Microsoft.
support.microsoft.com support.microsoft.com

learn.microsoft.com

Windows processor requirements Windows 11, version 24H2 supported Intel processors

This specification details the Intel processors that can be used with Windows 11, version 24H2 customer systems that include Windows products, including custom images.
learn.microsoft.com

learn.microsoft.com

Windows processor requirements Windows 11, version 24H2 supported AMD processors

This specification details the AMD processors that can be used with Windows 11, version 24H2 customer systems that include Windows products, including custom images.
learn.microsoft.com
Click to expand...

The problem with MS, and most large tech oriented companies, is that everyone there upgrades their hardware every 2 -3 years. If there's a forced update (like this suggestions) then it's "Oh well, guess we have to". Spending time on workarounds is never even considered. I used to work at a computer company... I know. I worked with MS internal people for a while and they are much more divorced from reality than most. They have no idea what it's like for many users/businesses. Please pass the Grey Poupon.

There's no reason they couldn't write workarounds i.e. "You lack _this_ so your system will run in reduced operation mode and a few things won't work for you. Here's a list". But they'd have to care. And they don't.

Code: 
</rant>
 

My Computer My Computer

At a glance

Windows 11 Pro 24H2Intel Ultra 7 155H16gbIntel Arc integrated
OS
Windows 11 Pro 24H2
Computer type
Laptop
Manufacturer/Model
HP
CPU
Intel Ultra 7 155H
Memory
16gb
Graphics Card(s)
Intel Arc integrated
Hard Drives
SSD
Hey guys. Thanks. I was unfamiliar with Windows Terminal so I did miss the step to select comand prompt. I have done so and all commands executed properly. I will try ine Windows Update now and see if that resolves my original issue.
 

My Computer My Computer

At a glance

Windows 11,
OS
Windows 11,
hmmm, this update (after running the commands above) said this... See attachment.
 

Attachments

  • w11update.webp
    w11update.webp
    18.9 KB · Views: 3

My Computer My Computer

At a glance

Windows 11,
OS
Windows 11,
You must log in or register to reply here.

Similar threads

Solved Upgrade from Win10 to Win11 23h2 using Rufus on unsupported hardware
Replies
16
Views
12K
antspants
antspants
Updates from Win10 to 22H or 23H directly fail to unsupported Hardware, 21H works fine
Replies
1
Views
2K
glasskuter
glasskuter

Latest Support Threads

Latest Tutorials

Back
Top Bottom