TPM_E_NO_WRAP_TRANSPORT (0x8028002F) fix for real

Cause 1: TPM in a bad state after BIOS update or reset

This is the most common reason I see this error. The TPM chip gets confused after a BIOS update, a motherboard change, or a TPM reset. Had a client last month who updated their Dell BIOS and next boot BitLocker threw this exact error. The TPM was still there, but it lost its session management tables. The wrapped transport session part is just TPM jargon for "I can't start a secure link with the OS."

Fix 1: Clear the TPM from Windows

1. Open Windows Security (search in Start menu).
2. Go to Device Security > Security processor details.
3. Click Security processor troubleshooting.
4. Under Clear TPM, hit Clear TPM. You'll need to restart.

This wipes the TPM keys. If you use BitLocker, make sure you have recovery key saved first. After reboot, Windows reinitializes the TPM fresh. That usually resolves the wrapped transport error.

Fix 2: Clear TPM from BIOS

If Windows Security won't open or the TPM is locked, do it from BIOS. Restart and mash F2 (or Del, Esc, depending on your brand) to enter BIOS setup. Look for TPM or Security Chip settings. Usually under Advanced or Security tab. Find Clear TPM or Reset TPM. Save and exit. Boot into Windows and check if the error is gone.

On HP business machines, I've seen this setting under Security > TPM Embedded Security > Reset TPM. On Lenovo ThinkPads it's under Security > Security Chip > Clear Security Chip. On Dells, it's TPM 2.0 Security > Clear.

Pro tip: If you clear the TPM and BitLocker asks for a recovery key, and you don't have it, you're locked out of your drive. Always backup that key before messing with TPM. I've had to rebuild a client's entire file server because they skipped this step.

Cause 2: TPM firmware bug or outdated version

Some TPM chips have known firmware bugs. Intel PTT (Platform Trust Technology) on certain Skylake and Kaby Lake boards had this issue. The firmware didn't handle transport sessions properly. If clearing TPM only fixes it temporarily, the firmware is the root cause.

Fix: Update TPM firmware

1. Check your motherboard or laptop manufacturer's support site for a TPM firmware update. It might be labeled as "TPM update" or "Intel Management Engine firmware."
2. Download and run the update tool. Usually it's a Windows executable that updates the firmware via the driver. Reboot after.

For Dell systems, go to Dell Support, enter your service tag, and look under Drivers & Downloads > Security for "TPM 2.0 Firmware Update." For HP, check SoftPaq downloads with "sp" number. For Lenovo, use Lenovo System Update tool.

If no update exists, your TPM firmware might be too old. In rare cases, replacing the motherboard is the only fix. But I've only seen that on ancient hardware from 2016.

Cause 3: TPM driver corruption or missing

Windows TPM driver can get corrupted after a major update. I saw this after a Windows 10 22H2 feature update that broke the TPM base driver. The error popped up when trying to use BitLocker or Windows Hello for Business.

Fix: Reinstall the TPM driver

1. Open Device Manager (right-click Start menu).
2. Expand Security devices.
3. Right-click Trusted Platform Module 2.0 (or 1.2) and select Uninstall device. Check the box that says "Attempt to remove the driver for this device" if it appears.
4. Reboot. Windows will auto-reinstall the driver.

If that doesn't work, download the TPM driver from your manufacturer's site. For Intel, it's usually part of the Intel Management Engine driver package. For AMD, it's in the chipset driver.

Alternative fix: Use DISM to restore driver health

DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

Run these commands as Admin. Then restart. This fixes system file corruption that might affect the TPM driver.

Quick-reference summary table

If none of these work, try a full TPM reset from the BIOS (disable TPM, save, reboot, re-enable TPM). That deep-cleans the chip. Last resort: replace the motherboard or TPM module. But I've only needed that once in five years.