Install Windows 11 on Unsupported PC Using Registry Keys

Windows 11 has strict system requirements (TPM 2.0, Secure Boot, and supported CPU models). If your PC doesn’t meet them, the official installer typically blocks the upgrade.

One workaround that’s been circulating for years is setting specific registry keys that tell the Windows setup engine to allow upgrades on unsupported hardware. This guide covers the keys, how to set them safely, and what to do when the installer still refuses.

As an Amazon Associate I earn from qualifying purchases.

Why registry-key bypass exists (and what it doesn’t fix)

The bypass works by changing values used by Windows Setup to decide whether it should enforce hardware checks. It can get you past the installer’s compatibility gate, but it doesn’t magically make unsupported hardware stable.

Also note the scope: these registry keys are meant to influence the setup process. They don’t enable TPM 2.0, don’t magically add Secure Boot, and don’t guarantee that every driver you’ll need exists for your specific platform.

Prerequisites before you change the registry

Do this before you touch HKEY_LOCAL_MACHINE. A wrong edit can break boot or setup behavior.

1) Confirm your current Windows version

Open Settings → System → About and note the OS build (example: Windows 10 22H2, build 19045.x). The steps below assume you’re starting from Windows 10 or Windows 11 (not Windows 7).

2) Back up what matters

• Create a full backup of your system drive (files + OS).
• If you use BitLocker, understand it may complicate clean installs after wiping disks.
• Export the registry key you’ll edit (or create a restore point).

3) Verify you’re logged in with an admin account

You need elevated permissions to write under HKLM. If the machine is domain-joined, Group Policy may override or restrict registry changes.

4) Have installation media ready

Prepare a Windows 11 installer USB using the official Microsoft tool or an ISO you trust. Common builds you’ll see today include Windows 11 23H2 and 24H2, but the bypass approach is broadly similar.

Registry keys required to allow upgrades on unsupported hardware

The bypass keys are created under a Setup-specific registry path. You’ll typically add a DWORD value named AllowUpgradesWithUnsupportedTPMOrCPU, and optionally BypassSecureBootCheck depending on what the installer complains about.

Registry path	Value name	Type	Data	What it helps with
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup	AllowUpgradesWithUnsupportedTPMOrCPU	DWORD (32-bit)	1	Bypasses CPU/TPM compatibility gate for upgrades
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup	BypassSecureBootCheck	DWORD (32-bit)	1	Attempts to bypass Secure Boot requirement

Important: The installer may still refuse due to other compatibility factors. Don’t assume these keys guarantee success on every unsupported configuration.

Step-by-step: set the registry keys

These steps assume you’re editing directly on the existing Windows installation you plan to upgrade.

1) Open Registry Editor as admin

1. Press Win + R.
2. Type regedit and press Enter.
3. Confirm the User Account Control prompt (click Yes).

2) Create (or open) the MoSetup key

1. In the left pane, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
2. Look for a subkey named MoSetup.
   • If it exists, click it.
   • If it doesn’t exist, right-click Setup → New → Key, name it MoSetup.

3) Add AllowUpgradesWithUnsupportedTPMOrCPU

1. Inside MoSetup, right-click the right pane → New → DWORD (32-bit) Value.
2. Name it exactly: AllowUpgradesWithUnsupportedTPMOrCPU
3. Set Value data to 1.

4) (Optional) Add BypassSecureBootCheck

1. Still inside MoSetup, right-click the right pane → New → DWORD (32-bit) Value.
2. Name it exactly: BypassSecureBootCheck
3. Set Value data to 1.

5) Restart before starting setup

Restart the PC. Setup reads these checks during installation. A reboot helps ensure the system sees the updated state cleanly.

Choose your installation method: upgrade vs clean install

The registry bypass is most reliably used for in-place upgrades because Windows Setup runs in a context where it can read those values from the current OS.

Clean installs can work, but they’re more sensitive to boot mode, partitioning (UEFI vs Legacy), and Secure Boot behavior.

Quick decision guide

• Upgrade (keep files/settings): Best chance that the bypass behaves as expected.
• Clean install (wipe drive): You may need extra steps (drivers, network setup, and boot configuration).

Upgrade path (recommended): install Windows 11 over the current OS

Use this path when possible because it keeps your current environment and reduces “first boot” surprises.

1) Start Windows 11 setup

1. Insert your Windows 11 USB or mount the ISO.
2. Open the media and run setup.exe.

2) Proceed through the prompts

1. On the initial screens, choose options like Keep personal files and apps when available.
2. Accept licensing terms.
3. If the installer still blocks you, stop and go to Common errors and what to try.

3) Confirm after the upgrade completes

After installation, go to Settings → System → About. Verify Windows 11 version/build and check for any “optional updates” or driver issues in Windows Update.

Clean install path: wipe and install Windows 11

Clean installs give you a fresh base, but they’re harsher on unsupported platforms. Do them only if you’re comfortable reinstalling drivers and apps.

1) Back up key data

For a clean install, your system drive will be wiped. Copy files to an external drive first.

2) Boot from the Windows 11 USB

1. Reboot and open your boot menu (often F12, Esc, or F9 on various vendors).
2. Select the USB entry.

3) Partition and install

1. Choose language/keyboard/region.
2. Click Install now.
3. If prompted for a product key, choose I don’t have a product key unless you have one.
4. Select the target drive/partition and proceed.

4) After install: install drivers immediately

Use your PC vendor’s support site or a reputable driver pack to install chipset, storage (RAID/AHCI drivers), and network drivers. Without network drivers, Windows Update may stall.

Common errors and what to try

Registry bypass failures usually fall into a few categories: wrong key location, wrong value type/name, Secure Boot/UEFI mismatch, or the installer using a different check path than you expected.

Error: setup says your PC doesn’t meet Windows 11 requirements

1. Confirm you edited HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup (not HKEY_CURRENT_USER).
2. Verify both DWORD values exist and are set to 1.
3. Confirm the names match exactly (spelling and capitalization don’t usually matter for DWORD names, but typos do).
4. Restart the PC, then re-run setup.exe.

Error: “This PC can’t run Windows 11” during the compatibility scan

Try running setup from within Windows (mount ISO → run setup.exe). If you launch setup in a way that behaves like a minimal installer environment, it may not see the registry changes the same way.

Error: stuck on “Getting updates” or repeated reboot loops

• Disconnect nonessential USB devices.
• Temporarily disable third-party antivirus during setup (re-enable afterward).
• Make sure you have enough disk space (at least 20–30 GB free is a safer minimum for upgrades; clean installs still need space for updates).

Error: Wi‑Fi/Ethernet doesn’t work after install

• Download chipset + network drivers on another machine and move them via USB.
• If you can’t get online, use Windows Update later after drivers are installed.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Hardware edge cases (TPM, Secure Boot, CPU support)

Unsupported does not always mean “works perfectly with no issues.” Here’s how the common requirement areas tend to affect outcomes.

TPM 2.0 missing

Some systems emulate TPM in firmware. Setup bypass can allow the install, but driver and security components may behave differently. Expect to troubleshoot BitLocker/credential flows if you rely on them.

Secure Boot disabled (or not supported)

If Secure Boot is disabled, UEFI firmware and boot configuration matter a lot. The bypass may let setup proceed, but booting and updates can behave unpredictably when Secure Boot is off or unsupported.

CPU not officially supported

Even when the install completes, you may hit performance quirks, missing microcode optimizations, or older instruction-set assumptions. Monitor CPU usage after install and plan for driver updates.

Security and reliability considerations

Bypassing hardware checks means you’re accepting risk you otherwise wouldn’t. Common impacts include reduced driver compatibility and a larger chance of feature limitations.

At minimum, consider disabling any “experimental” Windows features until you confirm stability, and keep regular backups—especially after the first week of use.

Alternatives that avoid bypassing checks

If you’d rather not rely on registry bypass behavior, these options can reduce risk.

Upgrade within the supported hardware envelope

If you have access to a supported machine, use it to evaluate Windows 11 behavior, then replicate software configurations later.

Use the official supported upgrade path

For borderline cases (for example, Secure Boot can be enabled in BIOS but isn’t currently), check firmware settings first. Enabling Secure Boot and switching to UEFI can remove blockers without bypass keys.

Consider a lightweight Linux distribution

If your goal is a functional modern desktop rather than Windows 11 specifically, a Linux option may deliver stability with less hardware friction.

Final Thoughts & FAQ

Registry keys can help you get past Windows 11’s installer hardware checks, but they’re not a guarantee of smooth operation on every unsupported PC. Treat it like a controlled risk: back up first, install methodically, and be ready to troubleshoot drivers and boot behavior.

If you decide to proceed, use the exact registry values under HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup, restart, then run setup.exe from Windows for the highest success rate.

Which registry values matter most?

AllowUpgradesWithUnsupportedTPMOrCPU set to DWORD 1 is the primary key. BypassSecureBootCheck set to 1 is commonly added when Secure Boot is the blocking message.

Do I need these keys for a clean install?

Not always. Clean installs can fail before they read those registry settings (because there’s no “current OS setup context” the same way). If the installer blocks you during clean install, you may need to instead adjust BIOS/UEFI settings or use a different installation approach.

Will this keep working after the upgrade?

Usually, yes—the system will boot and run Windows normally. The registry keys are mainly relevant to Setup’s compatibility gating during installation, not ongoing OS operation.

Is it safe to remove the registry keys after installation?

Often it’s unnecessary. If you want a clean state, you can remove them after a successful install, but do so only if you have a backup/restore plan in case something unexpected changes.

What if setup still refuses after setting the keys?

Re-check the exact registry path and value type (DWORD 32-bit), confirm the values are set to 1, reboot, and rerun setup.exe from the mounted ISO/USB. If the error specifically mentions Secure Boot or partitioning mode, verify BIOS boot mode (UEFI) and try the clean install only after driver planning.

Bottom Line

Using registry keys to bypass Windows 11 hardware checks can be a practical way to get an upgrade installer to proceed on unsupported systems—but it doesn’t remove the underlying realities of TPM, Secure Boot, and CPU compatibility. Plan for the possibility of driver hiccups, feature limitations, and a bit more troubleshooting after the install is done.

If you follow the safe workflow (backup first, set the exact DWORD values under HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup, reboot, then run setup.exe), you’ll give yourself the best odds of success. And if it still fails, don’t just keep iterating blindly—use the error message as your guide and consider a firmware fix (like enabling Secure Boot/UEFI) or a different installation strategy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.