TPM_E_BAD_ATTRIBUTES (0X80280042) – NV area attributes conflict fix

You're trying to enable BitLocker, or maybe run a secure startup check, and bam — error 0X80280042. The message says TPM_E_BAD_ATTRIBUTES – The NV area attributes conflict. I know this error is infuriating because it can pop up after a firmware update, a motherboard swap, or even a clean Windows install.

What's actually happening here?

The TPM (Trusted Platform Module) has a small storage area called NV (non-volatile) memory. This area has rules — attributes — that tell the TPM who can read or write to it. When you get this error, it means the attributes saved in the TPM don't match what the system or software is asking for. Think of it like a locked drawer where the key doesn't fit anymore.

This tripped me up the first time too. It's not a hardware failure most of the time. It's a mismatch between the TPM's stored data and what the OS expects. This can happen after updating your motherboard BIOS, switching from UEFI to Legacy mode, or even after a Windows Feature Update.

The fix: Clear the TPM and start fresh

Before you do anything else, back up your BitLocker recovery keys if you use BitLocker. You can find them in your Microsoft account at account.microsoft.com/devices. Without those, clearing the TPM will lock you out of encrypted drives.

1. Open Windows Security – hit Start, type "Windows Security", and open it.
2. Go to Device Security (on the left menu).
3. Under Security Processor, click Security processor details.
4. Click Security processor troubleshooting.
5. Click Clear TPM. You'll see a warning — agree to it.
6. Restart your PC. The TPM will be reset by Windows during boot.

That usually fixes it. But if you can't do it from Windows (maybe you're stuck at the login screen), you can clear it from the BIOS.

Alternative: Clear TPM from BIOS

1. Restart your PC and enter BIOS. Usually it's F2, Del, or F10 during boot. Check your motherboard manual.
2. Look for a Security or Advanced tab.
3. Find TPM or Trusted Computing settings.
4. Select Clear TPM or Factory Reset TPM.
5. Save and exit. Let Windows boot normally.

If clearing the TPM doesn't work

Sometimes the error sticks because the TPM firmware itself is buggy. Check your motherboard manufacturer's website for a TPM firmware update. For example, on many Ryzen boards, AMD released a TPM firmware update in 2022 that fixed attribute conflicts on Windows 11. On Intel systems, look for a BIOS update that includes TPM fixes.

Also, run this command in an elevated Command Prompt (right-click Start, choose Command Prompt Admin or PowerShell Admin):

wmic /namespace:\\root\cimv2\security\microsofttpm path Win32_Tpm get *

Look for IsEnabled_InitialValue and IsActivated_InitialValue. If either is FALSE, you need to enable the TPM in BIOS. Go back to BIOS and set TPM to Enabled and Activated.

Still failing? Check these

If you've cleared the TPM, updated the firmware, and enabled it fully, but still get 0X80280042, then:

• Reset your BIOS to defaults – a misconfigured Secure Boot or UEFI setting can mess with TPM attributes. Load optimized defaults in BIOS.
• Run the TPM diagnostics tool – download the TPM MMC snap-in (part of RSAT). Open tpm.msc and check the status. If it says "Not supported", your TPM might be disabled or broken.
• Check for a hardware TPM module – some desktop motherboards use a removable TPM chip. If yours is seated badly, reseat it. For laptops, it's usually soldered on.

A quick last resort: if you're on Windows 11 and this happened after a major update, try rolling back the update. Go to Settings > Windows Update > Update history > Uninstall updates. Remove the latest update and restart.

I've seen this error clear up after one or two restarts after the TPM clear. Don't panic — it's almost never a dead TPM.