How to Upgrade Unsupported Windows 10 PCs to Windows 11 for Free (2025 Guide)

For millions of Windows 10 users, a significant deadline is rapidly approaching. Microsoft's planned end-of-support for Windows 10 on October 14, 2025, marks a turning point for anyone still relying on this enduring operating system. Unless you're prepared to pay for the Extended Security Updates (ESU) subscription, your PC will soon be left without crucial security patches. Yet a major obstacle stands in the way of a simple upgrade path: official Windows 11 compatibility requirements, which have left countless older PCs out in the cold.
Microsoft’s firm stance on minimum hardware—encompassing strict CPU lists, the necessity of TPM 2.0, and Secure Boot support—has stymied upgrade efforts on devices more than five or six years old. For those worried about investing in new hardware solely to keep receiving updates, there’s both good news and important caveats. Documented, widely used workarounds can give "incompatible" Windows 10 PCs a new lease on life with Windows 11, though the journey requires technical patience and a considered evaluation of risks.

Understanding Windows 11’s Hardware Roadblocks​

Microsoft’s reasoning behind its tight hardware requirements—particularly TPM 2.0 and Secure Boot—focuses on security and stability. The company claims these measures defend against sophisticated modern threats, minimize the risk of rootkit attacks, and ensure a consistent baseline experience for all users. However, these policies also mean that a vast number of otherwise performant PCs are excluded from the "official" upgrade path.
If you've ever attempted to update an older system to Windows 11 via Windows Update or the Installation Assistant, you've likely encountered an unapologetic error message: your CPU isn’t supported, or your PC lacks the necessary TPM module. The frustration grows when you realize that, for many such machines, performance and reliability are not at issue—the incompatibility is an artificial barrier.
While Microsoft has been steadfast about not relaxing these requirements, the community and certain open-source projects have continuously devised methods to bypass these checks. Importantly, the company has not, to date, actively blocked users from applying updates to "unsupported" Windows 11 installations—though stern warnings are provided throughout the process.

Who Should Consider Upgrading—And Who Should Not?​

It’s important to honestly assess your hardware before proceeding down the workaround route. PCs built for Windows 10, with UEFI firmware, Secure Boot support, and at least TPM 1.2, usually fare well with unofficial Windows 11 upgrades. However, if your system is over a decade old or lacks these baseline features, your time and effort are likely better spent on alternative operating systems or, for essential systems, new hardware. In particular, AMD-based systems from the early 2010s and earlier Intel machines may run into showstopping issues related to unsupported instruction sets.
Never attempt an unsupported upgrade on mission-critical hardware without a complete, restorable backup, and be aware: even if updates continue during the Windows 11 lifecycle, future versions may be less forgiving.

Option 1: The Registry Edit—Bypass CPU and TPM 2.0 Checks​

For many moderately “incompatible” devices—especially those with TPM 1.2 and UEFI firmware—a straightforward registry tweak can grant access to Windows 11 upgrades without purchasing new hardware.

Step-by-Step Guide​

1. Verify System Requirements​

Before making any changes, run msinfo32.exe on your PC. Check for:

• BIOS Mode: Should read “UEFI,” not “Legacy.” If it’s not, you’ll need to convert your system disk from MBR to GPT and enable UEFI mode in BIOS, which can be complex and risky.
• TPM Presence: Launch tpm.msc. If you see a TPM listed, even version 1.2 is sufficient for this method. Absence of a TPM (or one that is disabled) will mean this option is not viable.

2. Backup Your System​

Registry edits always carry risk. Ensure you have a recent full backup using Windows Backup, Macrium Reflect, or similar.

3. Make the Registry Change​

• Open Regedit.exe.
• Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
• Right-click “Setup,” select New > Key, and name it MoSetup.
• Right-click the new MoSetup key, select New > DWORD (32-bit) Value. Name it: AllowUpgradesWithUnsupportedTPMOrCPU
• Double-click this value and set the data to 1.

Your registry entry should look like:
Restart your PC to make sure the setting takes effect.

4. Download and Mount the Windows 11 ISO​

• Visit Microsoft’s Windows 11 download page.
• Scroll to "Download Windows 11 Disk Image (ISO) for x64 devices."
• Save the ISO. If you use English (UK), select English (United States) to avoid upgrade issues retaining your apps/data.
• Double-click the ISO file; File Explorer will mount it as a virtual DVD drive.

5. In-Place Upgrade via Setup.exe​

From the mounted ISO, run Setup.exe. You’ll be warned about incompatibility and updates possibly being unavailable. Accept and proceed.

• Keep everything: If you update from the same edition (Home/Pro), you can usually retain your apps, personal files, and settings—a vital distinction from clean installs.
• Full Upgrade vs. Clean Install: Choose accordingly; most readers will want to keep existing data.

Caveats with This Approach​

• This registry tweak no longer appears in current official Microsoft documentation, but was previously (archival sources confirm this) explicitly outlined by the company.
• While Windows 11 generally works well after such upgrades, some features (notably advanced security options like Device Guard, BitLocker in some configurations, and certain virtualization tools) may be unavailable.
• If you are upgrading to Windows 11, version 24H2 or later, your system must also support the SSE4.2 and PopCnt CPU instructions. This excludes most CPUs manufactured before 2013 (Intel) or 2013 (AMD), making this a hard stop for truly old hardware.

Option 2: The Rufus USB “No-Checks” Upgrade​

Suppose your system lacks any TPM, can’t set Secure Boot, or you’re running in Legacy BIOS mode and can’t switch to UEFI. The second, more radical method involves creating a bootable Windows 11 USB installer that disables compatibility checks using the free Rufus utility.

What is Rufus?​

Rufus is a well-established, open-source utility for creating bootable USB drives. From version 4.6 onwards, Rufus can automatically modify Windows 11 installation media to bypass hardware restrictions.

How to Use Rufus for the “Incompatible” Upgrade​

1. Gather Your Tools​

• Rufus (v4.6 or newer): Download from the official site.
• Windows 11 ISO: As before, download from Microsoft’s website.
• USB stick: At least 16GB; it will be completely erased during this process.

2. Create the Bootable USB​

• Open Rufus.
• Select your USB drive.
• Under “Boot selection,” choose “Disk or ISO image” and select your Windows 11 ISO.
• Click "Start."
• In the “Windows User Experience” dialog, select (at minimum) the checkbox to remove requirement for Secure Boot and TPM 2.0 (the dialog allows for several choices, including bypassing the online account requirement and more).
• Proceed, and Rufus will prepare a USB drive ready to install Windows 11 on nearly any PC.

3. Install Windows 11​

• Do not boot from the USB drive for an in-place upgrade—this would trigger a clean install, wiping your apps and data.
• Instead, open the USB drive in File Explorer on your existing Windows 10 installation, and run Setup.exe from there.
• Follow the prompts; again, accept compatibility warnings when they appear.

If everything aligns, you should reach the familiar Windows 11 upgrade screen and select how much you wish to preserve (files, apps, nothing).

Technical Limits and Reality Checks​

• CPU Instruction Set: As of the Windows 11 24H2 update, older CPUs lacking SSE4.2 and PopCnt instructions are permanently blocked—no workaround. This impacts pre-2013 AMD CPUs and pre-2010 Intel chips.
• Lack of UEFI/Secure Boot/TPM: Even with these checks bypassed, some future updates or builds may break key functions or further restrict legacy devices. Microsoft has occasionally tweaked the installer to detect known bypasses and forcibly block or degrade the user experience on unsupported setups.
• Unpredictable Updates: Windows Update may work, but future feature or cumulative updates could fail or revert your changes. While many users report reliable updating (citing at least two years of “unsupported” Windows 11 installs running with regular updates), this cannot be guaranteed.

Are There Legal or Support Risks?​

Microsoft's license terms leave unsupported installs in a gray area. Officially, upgrading to Windows 11 on hardware that fails the compatibility checker is “not recommended,” and you’ll receive a notification stating you are ineligible for updates or support. That said, there is currently no technical enforcement—your installation will activate against your Windows 10 license and receive regular updates, unless and until Microsoft changes its server-side policies.
Organizations should be especially cautious. Deploying Windows 11 on unsupported PCs could violate IT compliance policies and may lead to unanticipated liability or security risks in business or regulated environments.

Critical Analysis: Benefits, Risks, and Future-Proofing​

Notable Strengths​

• Extended Security for Free: For those reluctant or unable to purchase new hardware, these workarounds breathe new life into perfectly functional PCs, extending their secure use beyond the Windows 10 support deadline.
• No-cost Methods: Both options are free, widely documented, and foster digital sustainability by reducing needless electronic waste.
• In-place Upgrades Retain Data: Especially with the registry method, users can keep their apps, files, and settings intact, minimizing disruption.

Potential Risks and Downsides​

• Warranty and Support Voided: Microsoft does not promise technical support or compatibility fixes for devices upgraded by unofficial means. Users are on their own if major bugs or critical failures occur.
• Update Uncertainty: While updates currently work, this could change without notice. A “future-proof” guarantee simply does not exist for these systems.
• Feature Limitations: Some modern security and system features may be restricted, undermining the security benefits that Windows 11 was designed to deliver.
• Possible Instability: Unusual hardware, outdated drivers, or unsupported configurations may cause random crashes, BSODs, or sluggish performance.
• Legal and Organizational Compliance Questions: Although individual home users face minimal risk, corporations or regulated entities risk non-compliance.

Security and Compliance Reality Check​

Microsoft’s stricter Windows 11 baseline does provide tangible improvements in system resilience. TPM 2.0 and Secure Boot are especially formidable in fighting rootkits and firmware attacks, which are increasingly prevalent. Users bypassing these requirements miss out on these layers, making diligent personal security practices and up-to-date antivirus essential.

The Impact of the Windows 11 24H2 Update​

The late 2024 update to Windows 11, designated 24H2, notably tightened hardware checks, making SSE4.2/PopCnt CPU instructions strictly required. According to independent testing and Microsoft documentation, most mainstream Intel CPUs made after 2009 and AMD models from 2013 onward support these features. Systems older than this are now definitively blocked—even Rufus cannot circumvent this check.

Clean Install vs. In-Place Upgrade​

If you’re prepared to start fresh, booting directly from a Windows 11 installation USB (with or without Rufus tweaks) remains possible, provided your hardware meets the minimum requirements (especially TPM/Secure Boot). This skips the CPU check but does not bypass TPM or Secure Boot checks—an important nuance. Clean installs wipe all data, requiring you to reinstall applications and restore files afterwards.

What the Upgrade Warnings Actually Mean​

Each of the documented upgrade workarounds includes intimidating warning screens from Microsoft, suggesting future updates and security patches may be at risk. However, independent verification and direct communication from Microsoft representatives (citing resources like the Windows IT Pro Blog and support forums) confirm that, as of early 2025, PCs upgraded this way continue to receive monthly Patch Tuesday security updates and, for now, even feature upgrades. Microsoft reserves the right to change this at any time, so users must weigh the prospect of being abruptly cutoff.

Conclusion: Should You Upgrade an Unsupported PC?​

For home users on a tight budget, these free workarounds are a powerful means to extend the life of otherwise capable hardware beyond Windows 10’s retirement. Activity in enthusiast forums demonstrates that thousands of older PCs are running Windows 11 without issue, many for years now. So long as you’re willing to invest the time, create backups, and accept some degree of risk, the process is relatively straightforward.
That noted, you must approach unsupported upgrades with caution. Avoid deploying such installations in mission-critical or business settings. Recognize that future updates may not be assured and that loss of advanced security features could expose you to greater risks, especially if your computing involves sensitive financial, work, or personal data.
In summary: if security, support, and full compliance matter above all, replacement or official ESU subscription for Windows 10 is wisest. But if you’re a home enthusiast, hobbyist, or simply need another year or two from an aging PC, ZDNet’s two-pronged approach—registry edit for nearly-compatible PCs and Rufus for more deeply incompatible ones—offers a practical, no-cost upgrade route.
Stay proactive: keep system backups, monitor the Windows update landscape for changes, and always weigh the advantages of squeezing more value from old hardware against the inevitability of shifting software and hardware standards. And remember, the Windows ecosystem has always found ways to evolve with its users—even when official channels seem to say “no.”