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

epete · 2025-04-25T10:34:28-0400

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.

Bree · 2025-04-25T10:51:24-0400

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.

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.

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

epete · 2025-04-25T11:31:31-0400

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.

Levitate11 · 2025-04-25T11:40:10-0400

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.

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.

Bree · 2025-04-25T12:03:05-0400

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

Levitate11 said:
as a programmer, it appears that the command is complaining about your output from the reg process to NUL.

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.

KevTech · 2025-04-25T12:15:47-0400

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

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

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

garlin · 2025-04-25T12:27:53-0400

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.

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...

Levitate11 · 2025-04-25T12:43:09-0400

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

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

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

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>

epete · 2025-04-25T12:56:11-0400

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.

epete · 2025-04-25T13:07:09-0400

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

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

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Active member

My Computer

Active member

Attachments

My Computer

Similar threads