Categories About Us Contact Us Become a Member

How to fix the Windows 11 setup error 0x80888002

This setup error means Windows 11 could not confirm your PC is eligible, often because TPM or Secure Boot is not detected, or it cannot tell whether there is enough space. Jump to your situation below or work through the methods in order.

By Neeraj Singh ~6 min Updated Jun 2026 88% found this helpful
Error message
0x80888002. We couldn't determine if your PC is eligible to run Windows 11. Try again later.
Summary

Setup error 0x80888002 appears during a Windows 11 upgrade or install with a message like we couldn't determine if your PC is eligible or that it cannot tell whether there is enough space. It is a readiness and compatibility block: the eligibility check could not confirm that TPM 2.0 and Secure Boot are present, that the CPU qualifies, or that there is sufficient free space. It often hits when those features are disabled, when running setup from an awkward source such as a mounted ISO, or when a previous TPM-bypass tweak confuses the newer check. The fix is to enable TPM 2.0 and Secure Boot, confirm free space, and run the upgrade from a clean, freshly downloaded ISO or the Installation Assistant. On genuinely unsupported hardware, the documented registry bypass is the only way through, with Microsoft's unsupported caveat.

What this error means

Before installing, Windows 11 confirms the PC is eligible, the right TPM, Secure Boot, CPU and enough space. 0x80888002 means that confirmation did not complete: the check could not get a clear yes, so setup stops rather than continue on an unknown system.

That uncertainty usually comes from TPM or Secure Boot being off or not detected, from a space check that cannot read the drive, or from running setup in a way the check does not expect, such as a mounted ISO or after a registry bypass left things in a half-state. Clearing those up lets the check complete.

Common causes

TPM 2.0 or Secure Boot is disabled or not detected.
The eligibility check cannot confirm enough free space.
Setup is run from an awkward source like a mounted ISO.
A previous TPM-bypass tweak confuses the newer check.
The CPU is not on the supported list.
A corrupt or outdated installer.
Expert insight

“0x80888002 is setup throwing up its hands and saying I cannot tell if this PC is allowed. Most often that is because TPM or Secure Boot is off, so it cannot tick those boxes, or it cannot read the free space. I enable TPM and Secure Boot, make sure there is plenty of room, and then run the upgrade from a fresh ISO rather than some mounted virtual drive, which the check dislikes. If the hardware is genuinely unsupported, the registry bypass is the only door, and you accept Microsoft's caveat going in.”

How to fix it

Method 1

Enable TPM 2.0 and Secure Boot

1Enter the UEFI firmware and enable the TPM (listed as Intel PTT or AMD fTPM) and Secure Boot.
2Both are required for Windows 11, and a disabled TPM or Secure Boot is the most common cause.
3Save, boot back into Windows, and check again.
Method 2

Confirm there is enough free space

1Make sure the system drive has well over the minimum free (at least 64 GB capacity, with plenty free for the install).
2Clear space with Disk Cleanup if it is tight.
3The check can fail if it cannot confirm enough room.
Method 3

Use a clean, fresh ISO or the Assistant

1Download a fresh Windows 11 ISO or the Installation Assistant from Microsoft.
2Avoid running setup from an old mounted virtual drive, which the eligibility check handles poorly.
3Run setup.exe from the freshly mounted media.
Method 4

Run PC Health Check to see which test fails

1Install and run Microsoft's PC Health Check app and choose Check now under Windows 11.
2It names the specific requirement that fails, TPM, Secure Boot, the CPU, RAM or storage.
3Fix the named item rather than guessing.
Method 5

Bypass on unsupported hardware (with caveat)

1If the hardware is genuinely unsupported but you accept the risk, the documented bypass sets a registry value for the upgrade:
HKLM\SYSTEM\Setup\MoSetup
AllowUpgradesWithUnsupportedTPMOrCPU = 1 (DWORD)
2Microsoft warns unsupported PCs may not be entitled to updates. See our This PC can't run Windows 11 guide for the full method.

0x80888002 means setup could not confirm eligibility, so enable TPM 2.0 and Secure Boot first, then make sure there is ample free space and run from a fresh ISO rather than a mounted virtual drive. The registry bypass is only for genuinely unsupported hardware, and it carries Microsoft's no-updates-entitlement caveat.

Frequently asked questions

What does Windows 11 error 0x80888002 mean?
It means setup could not determine if your PC is eligible for Windows 11, usually because TPM 2.0 or Secure Boot is not detected, or it cannot confirm enough free space.
How do I fix 0x80888002?
Enable TPM 2.0 and Secure Boot in UEFI, confirm the drive has plenty of free space, and run the upgrade from a freshly downloaded ISO or the Installation Assistant rather than an old mounted drive.
Why does the install source matter?
The eligibility check handles mounted virtual drives poorly and can fail to read them. Running setup from a fresh ISO or the Installation Assistant avoids that confusion.
I already bypassed the TPM check, why this error?
A previous registry bypass can leave the newer eligibility check in a half-state. Re-running from a clean ISO, or applying the current documented bypass, resolves the conflict.
Can I install on unsupported hardware?
Yes, with the documented registry bypass, but Microsoft warns unsupported PCs may not be entitled to updates. Weigh that before proceeding.
Is my hardware definitely unsupported?
Not necessarily. Run PC Health Check to see whether it is a disabled TPM or Secure Boot, which is fixable, versus a genuinely unsupported CPU.

Still not working?

If 0x80888002 persists with TPM and Secure Boot on and a fresh ISO, the setup logs under C:\$WINDOWS.~BT\Sources\Panther record which eligibility test failed. Read that to target the exact block. You can also submit your error to us for a tailored fix.

Was this fix helpful? Thanks for your feedback!