Skip to main content

How To Install Windows 11 on Unsupported Hardware

By Michał

If you have a computer with unsupported hardware, you cannot upgrade to Windows 11 through Windows Update. However, Microsoft left a loophole open but made no official mention of it. He left this option to organizations and people who will knowingly install this system on incompatible hardware. To install you need to use a bootable USB drive or ISO file to manually install/update.

Note that while Windows 11 can be installed on unsupported hardware, Microsoft is not obligated to provide security or driver updates. You do this at your own risk and there is no guarantee that your system will be stable and will have compatible drivers.

As a reminder, when the hardware is incompatible, we will receive this information when installing the Win11 system:

Error - This PC doesn't meet the minimum system requirements to install this version of Windows.

To install Windows 11 on an unsupported PC, use these steps:

  1. Start the PC with the Windows 11 USB Flash Drive

  2. Press any key to continue.

  3. Use the Shift + F10 keyboard shortcut to open Command Prompt.

  4. Type the regedit command and press Enter:
    Command Tool


  5. Navigate the following path:
    HKEY_LOCAL_MACHINE\SYSTEM\Setup
  6. Right click on theSetup key, select New and then the Key option.
    Right click on the Setup key and add new Key option


  7. Name this key LabConfig and press Enter.

  8. Right click on the LabConfig key, select New, and then the DWORD (32-bit) Value option. Do this twice and name the keys appropriately:
    • BypassTPMCheck
    • BypassSecureBootCheck
    • BypassRAMCheck (optional, rarely useful but in the next point it will be included)

  9. Double click the newly createded keys and set their value from 0 to 1.
    Values of BypassTPMCheck, BypassSecureBootCheck, BypassRAMCheck keys


  10. Close registry tool and continue installation process

Installing Windows 11 on incompatible hardware is possible and not difficult. It is enough to add some information to registry at the installation stage and the system should install without any major problems. Just remember that the more incompatible the hardware, the greater the likelihood of later problems, e.g. with component drivers.

Labels:

Comments

Post a Comment

Popular posts from this blog

PowerShell Permanently Clear History

By Michał
PowerShell has a command to clear the command history like Clear-History. However, it is independent of the host and must be deleted separately. This information is especially important when you need to use a command with your password (in command).  How to permanently delete PowerShell history? The entire history of the commands you use in PowerShell is saved to one file. To fully delete the history, all you need to do is ... delete the file. Usually the file is located in AppData, but you can check the exact path with the command which will display the full path. PS C:\> (Get-PSReadlineOption).HistorySavePath ### result C:\Users\geekitsupp\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt After deleting this file, all history of commands executed in PowerShell will be deleted. Clear-History or [Microsoft.PowerShell.PSConsoleReadLine]::ClearHistory() command doesn't permanently delete history. They can only delete ...
Post a Comment
Read more

How to use Test-NetConnection in PowerShell

By Michał
In the latest versions of Windows, the client and telnet service are not installed by default. They are available as installable functions. Unfortunately, turning on telnet often requires a restart computer. The connection test can be performed with the ping command, but does not perform any tracing or port testing. In most network problems we need to use ping command with tracert. Also telnet for check for open ports. PowerShell Test-NetConnection The Test-NetConnection command is the successor to Test-Connection but provides more information. Let's do a simple test to Google: PS C:\> Test-NetConnection 8.8.8.8 ComputerName : 8.8.8.8 RemoteAddress : 8.8.8.8 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.1.10 PingSucceeded : True PingReplyDetails (RTT) : 9 ms The command returns a lot of information, usually this is enough to find a network problem (if any). It will display the interface, source I...
Post a Comment
Read more