I got a new PC. It’s shiny. I want it to work. I try to set up Windows Autopilot. Boom. Error. Something about TPM. I stare at the screen. I feel like a dog chasing its tail. Why is this happening? I just want to get to work. Let’s talk about what’s going on. I’ll keep it simple. Imagine you’re trying to open a locked door. You have the key. The lock is new. But the door won’t budge. That’s what this feels like. The key is your PC’s TPM chip. The door is Windows Autopilot. The lock? That’s the attestation process.
What’s the Problem?
- You get a TPM check error happens on new 2025 PCs.
- You’re using Windows Autopilot.
- The error pops up during pre-provisioning.
- Microsoft knows about it. They’re working on it.
I read a note from Joe Parker. He said, “If you are seeing Autopilot errors on new 2025 PCs related to TPM attestation with pre-provisioning flows, Microsoft is aware of this and is working on it.” That’s straight from the source.
Why Does This Happen?
TPM stands for Trusted Platform Module. It’s a chip. It keeps things safe. It checks if your PC is real and secure. Windows Autopilot uses it to make sure your computer is legit before setting it up. But some new PCs use a stronger key called RSA 3072EK. It’s like using a super-strong padlock. Sometimes, the system can’t handle it. The attestation fails. You get the error.
Microsoft has a support article about this say, “TPM attestation isn’t working for TPMs which use high-range RSA 3072EK.” That’s the technical bit. But all you need to know is: the new lock is too strong for the current key-checker.
What Can You Do Right Now?
Here’s what you can try:
- Check for Updates: Sometimes Microsoft releases a fix. Go to Windows Update. Smash that “Check for updates” button.
- Try Manual Provisioning: If Autopilot fails, set up the PC manually. It’s not ideal, but it gets you in the door.
- Contact Support: Open a ticket with Microsoft. Tell them you have a 2025 PC with a TPM attestation error. Mention RSA 3072EK.
- Bookmark the Support Article: Microsoft updates these pages. Keep an eye on the official support article about TPM attestation and RSA 3072EK.
- Join the Conversation: Tech forums are buzzing. Other people have the same problem. Sometimes, someone finds a workaround before Microsoft does.
What Not to Do
- Don’t reset your PC over and over. It won’t help.
- Don’t try to downgrade your TPM. That’s risky and unnecessary.
- Don’t blame yourself. This is a Microsoft issue.
Microsoft is working on a fix. They know it’s a problem. They want to solve it. It might take a little time. In the meantime, keep your system updated. Watch for news. Stay connected with IT forums. If you need screenshots or step-by-step guides, Microsoft’s support site is your friend. Search for “TPM attestation isn’t working for TPMs which use high-range RSA 3072EK.” Save that link. Check it often.