October 14, 2025 — the day Microsoft officially ends free security updates for Windows 10 — is fast approaching. After that date, millions of PCs still running the decade-old OS will be sitting ducks for cyberattacks unless their owners pay for Extended Security Updates or finally make the jump to Windows 11. But Microsoft’s strict hardware requirements — TPM 2.0, Secure Boot, UEFI, and a whitelist of supported CPUs — block many otherwise capable machines from upgrading through official channels. That doesn’t mean you’re stuck. Two practical, widely tested workarounds let you bypass those checks and perform a free in-place upgrade, preserving your apps, settings, and files. They aren’t sanctioned by Microsoft, and they come with real trade-offs, but for those determined to squeeze more life out of aging devices, they’ve become essential knowledge.

This guide combines steps, risks, and troubleshooting gleaned from community experience and technical deep dives. It reflects the latest hurdles Microsoft introduced in Windows 11 version 24H2 — including new CPU instruction requirements that even the workarounds can’t circumvent — and the matching countermeasures built into tools like Rufus 4.6. Here’s everything you need to know to upgrade your “incompatible” Windows 10 PC.

Why the Workarounds Are Necessary

Microsoft drew a hard line with Windows 11’s system requirements. Officially, you need an 8th-generation Intel Core processor or newer (or AMD Ryzen 2000 series and above), UEFI firmware with Secure Boot capability, and TPM 2.0. That left out many PCs sold just a few years before Windows 11 launched, even those that perform perfectly well under Windows 10.

The end of Windows 10 support on October 14, 2025, adds urgency. After that, only those who enroll in the consumer Extended Security Updates (ESU) program will receive critical and important security patches — and that program expires on October 13, 2026. For home users unwilling to pay a recurring fee or migrate to an entirely new PC, the upgrade workarounds are the only path to a still-supported Windows version.

Microsoft has also tightened the screws with each feature update. Windows 11 24H2 introduced a hard requirement for the POPCNT and SSE4.2 instruction sets in the CPU. That effectively bans truly ancient processors — roughly Intel chips older than 2009–2011 and AMD models older than 2013 — from booting the latest builds, even with bypasses. But for the vast majority of Windows 10-era PCs, these workarounds still succeed.

Two Upgrade Paths at a Glance

Before diving in, pick the method that matches your hardware:

  • Option 1: Registry Edit (AllowUpgradesWithUnsupportedTPMOrCPU)
    Ideal for systems that already use UEFI, have Secure Boot support, and at least have TPM 1.2 enabled. This tweak lets you run Setup from within Windows and keep everything intact.
  • Option 2: Rufus Utility
    For older PCs lacking TPM, stuck in Legacy BIOS/MBR mode, or when direct setup fails. Rufus creates a USB installer that automatically suppresses compatibility checks. Requires Rufus 4.6 or later for 24H2 upgrades.

If your CPU lacks SSE4.2/POPCNT support, neither method will get you to a bootable 24H2 installation. In that case, consider ESU or a lightweight Linux distribution.

Prerequisites: Know Your Hardware

Check these four items before you start; they dictate which option works and prevent heartache later.

  • BIOS Mode (UEFI vs. Legacy): Open msinfo32.exe. If “BIOS Mode” says “Legacy,” Option 1 won’t work unless you convert your disk to GPT and enable UEFI — a separate, daunting process. Option 2 can handle legacy, but a clean install might be simpler if you’re not attached to your apps.
  • TPM Status: Run tpm.msc. A TPM 2.0 is ideal, but even TPM 1.2 meets the minimum for the registry trick. Many Windows 10 PCs shipped with TPM disabled in firmware; enter your BIOS/UEFI settings to turn it on. If no TPM exists at all, only Option 2 works.
  • CPU Instruction Support: Use CPU-Z or HWiNFO to confirm your processor supports SSE4.2 and POPCNT. Without them, 24H2 will blue-screen during boot. This is a physical barrier no software workaround can break.
  • Free Disk Space: Windows 11 demands 64GB, but real-world upgrades often succeed with 30GB or more. Clear out junk if necessary.

Back up your data and create a full system image. “If you lose everything because you skipped this step,” warns veteran Windows reporter Ed Bott, “you’ll have only yourself to blame.” A recovery USB with your current Windows 10 is also wise.

Option 1: The Registry Edit That Skips CPU and TPM Checks

This method is the least invasive and keeps your applications and personal files. It works only when you run Setup from within your existing Windows 10 session — booting from USB won’t honor the key.

Step 1: Add the Magic Registry Key

Open Registry Editor as Administrator. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup

If MoSetup doesn’t exist, right-click Setup, choose New → Key, and name it MoSetup. Inside that key, create a new DWORD (32-bit) Value named AllowUpgradesWithUnsupportedTPMOrCPU. Double-click it and set the value data to 1. Restart your PC.

This tweak was once documented by Microsoft itself; the company scrubbed its support page in late 2024, but the key still works. It tells Windows 11 Setup to ignore the CPU whitelist and accept TPM versions as low as 1.2.

Step 2: Grab the Windows 11 ISO

Go to Microsoft’s official download page and choose “Download Windows 11 Disk Image (ISO) for x64 devices.” Save the multi-gigabyte file to your Downloads folder. If your Windows 10 language isn’t English (United States), be careful: choosing the wrong language version during setup can prevent the “Keep personal files and apps” option from appearing. Users running English (UK) or other regional flavors should select “English (International)” to avoid this pitfall.

Step 3: Mount and Run Setup

Double-click the ISO to mount it as a virtual drive. Open that drive and launch Setup.exe. A warning dialog will appear, menacingly telling you that your PC doesn’t meet requirements and you may not receive updates. Accept it. When prompted, select “Not right now” for updates to avoid a common error where Setup prematurely quits. Then choose the “Keep personal files and apps” option and let the upgrade run. It may take an hour or more, with several reboots.

Afterward, visit Windows Update to fetch the latest patches and check Device Manager for missing drivers. Many older machines need manual driver downloads from the manufacturer’s website.

Option 2: Rufus — The All-in-One Bypass Tool

Rufus, the free open-source utility for creating bootable USB drives, added sophisticated Windows 11 bypass features starting with version 4.6. It automates not only the registry tweak but also the replacement of the appraiserres.dll compatibility check file and other modifications. Use this route when your PC has no TPM, runs Legacy BIOS, or resists the simpler registry method.

Step 1: Prepare the Ingredients

Download the latest Rufus (4.6 or newer) and the Windows 11 ISO from Microsoft. You’ll also need a USB flash drive of at least 16GB — Rufus will wipe it clean.

Step 2: Configure Rufus

Launch Rufus as Administrator. Select your USB drive, then under “Boot selection” pick the downloaded ISO. The “Partition scheme” and “Target system” should mirror your current setup: GPT for UEFI systems, MBR for Legacy BIOS. Click Start.

A “Windows User Experience” dialog appears. Check the top box: “Remove requirement for 4GB+ RAM, Secure Boot, TPM 2.0, 64-bit CPU, etc.” This selects the full hardware bypass. You can also customize local account setup and region options if desired. Click OK to confirm.

Rufus will write the USB and inject the bypasses. This can take several minutes.

Step 3: Upgrade From Within Windows

Crucially, do not reboot and boot from the USB. Instead, open the finished USB drive in File Explorer and double-click Setup.exe. Just as with Option 1, accept the compatibility warning and choose “Not right now” when asked about updates. Proceed with the in-place upgrade. If you encounter an “unsupported operation” error, retrying and selecting “Not right now” for updates has proven effective.

Rufus cannot overcome the SSE4.2/POPCNT barrier. If your ancient CPU is missing those instructions, the 24H2 installation will ultimately fail to boot, even if the setup process completes.

The Risks You’re Accepting

These workarounds put you in unsupported territory. Microsoft’s official stance is that such configurations may not receive all future updates and that you assume all risk. So far, security updates have arrived for unsupported hardware, but the company could change that at any time. For businesses or anyone dealing with sensitive data, running Windows 11 without TPM or Secure Boot undermines critical security features like virtualization-based security and memory integrity.

You’re also on your own for drivers. Wi-Fi, audio, and graphics on older machines sometimes behave erratically under Windows 11, and manufacturers aren’t rushing to release fixes. Test everything after upgrading, and be prepared to roll back if essentials break.

Finally, future Windows 11 feature updates may introduce new barriers. The 24H2 instruction set requirement blindsided many who had successfully upgraded earlier versions. If your hardware is barely squeaking by, start budgeting for a replacement within a year or two.

Troubleshooting Common Upgrade Hiccups

  • Setup.exe quits early with error 0xC1900101 or similar: Often a driver conflict. Try disconnecting nonessential USB devices and running Setup again. The “Not right now” update setting also helps.
  • “An unsupported operation was attempted”: This error, reported with Rufus media and 24H2 ISOs, is dodged by choosing “Not right now” for updates at the start of Setup.
  • Black screen after first reboot: Boot into Safe Mode, uninstall graphics drivers, and let Windows Update fetch a compatible version.
  • Rollback fails: If Windows 10 restored itself, check the setupact.log in C:\$WINDOWS.~BT\Sources\Panther for the reason. Disk space or incompatible software are common culprits.

Always have your backup and recovery media ready. If the upgrade bricks the system, you can restore the disk image and try again or retreat to Windows 10.

A Growing Toolkit for a Shrinking Window

Community ingenuity has kept these workarounds alive and evolving. When Microsoft pulled the registry documentation, forums preserved it. When 24H2 broke existing bypasses, Rufus developer Pete Batard shipped a setup.exe wrapper to counteract the changes. As one forum poster noted, “These approaches let many otherwise ‘incompatible’ Windows 10 PCs move to Windows 11 while preserving apps and files — but they carry important caveats about security updates, stability, and future feature upgrades.”

The message is clear: For home users who can’t afford a new PC today, these methods offer a realistic, free bridge into the Windows 11 era. But they are just that — a bridge. Prepare, verify your hardware, and always have a fallback plan. With careful execution, you can defy Microsoft’s official compatibility list and keep your old machine secure for a couple more years.

Looking for more detailed walkthroughs? Ed Bott’s comprehensive guide at ZDNET (updated regularly since 2022) and the Rufus GitHub release notes are excellent references.