Fix it now
0x80180022 during Autopilot enrolment means the device is running Windows Home, and the documented fix is to update it to Pro or higher. 0x800705b4 at “Securing your hardware” means self-deploying mode could not use the TPM: it needs a physical TPM 2.0, not a virtual one and not TPM 1.2.
winver
Get-Tpm
- Read the edition first. If it says Home, that is the answer for 0x80180022 and everything else here is irrelevant.
- Read
Get-Tpm. TpmPresent False, or a TPM reporting version 1.2, means self-deploying mode cannot work on this hardware. - If no TPM is reported at all, reboot into UEFI firmware settings and look for the security processor – it is often named for the chipset vendor rather than called TPM.
- Upgrade Home to Pro in place: Settings, System, Activation, then change the product key. Files and applications are preserved.
- Re-run enrolment or Autopilot provisioning only once the edition and the TPM are both correct.
Hyper-V and other virtual machines have virtual TPMs. Microsoft states these do not work with self-deploying mode, whatever version they report.
If provisioning completes you can stop here. If not, the next section covers the attestation failures that look identical from the screen.
Why it happens
Two different gates are being described here, and they fail at different points in the out-of-box experience. The edition gate is checked when the device tries to enrol: Microsoft’s Intune enrolment troubleshooting names “Autopilot device enrollment failed with error HRESULT = 0x80180022” with the cause “the device being provisioned is running Windows Home Edition” and the resolution “update the device to Pro edition or higher”. There is no policy, registry value or workaround; the edition is the gate.
The hardware gate is checked earlier, at the “Securing your hardware” step, and produces 0x800705b4. Microsoft’s documented requirements are precise. The device must have a physical TPM 2.0 chip – devices with virtual TPMs, including Hyper-V virtual machines, and devices with TPM 1.2 do not work with self-deploying mode. And it must run Windows 10 build 1709 or later, or build 1809 or later where Microsoft Entra hybrid join is used. Both conditions, not either.
Then there is attestation, which is where the confusion starts, because a device can have a TPM 2.0 and still fail. 0x81039023 and 0x81039024 are both TPM attestation failures during pre-provisioning or self-deploying mode, and Microsoft publishes a different remedy for each. 0x81039023 is fixed by applying the May 2022 cumulative update for Windows 11 21H2 (KB5013943) or later. 0x81039024 means known vulnerabilities were detected in the TPM, and the fix is a TPM firmware update from the PC manufacturer.
0x801c03ea is the one most often misread. In the Intune enrolment context it appears as “Registering your device for mobile management (Failed: 3, 0x801C03EA)” and Microsoft’s cause is a TPM chip that supports version 2.0 but has not yet been upgraded to 2.0 – firmware, not silicon. Microsoft names a second cause too: the same device sitting in two assigned groups with different Autopilot profiles. The Windows Hello error list gives the same value a different reading, “Server failed to authorize user or device”. Check both before assuming either.
The device is running Windows Home
You have this one if 0x80180022, and winver or Settings, System, About reports Home.
- Upgrade in place to Pro: Settings, System, Activation, then Change product key and enter a Windows 11 Pro key.
- Restart when prompted. Installed applications and user files are preserved.
- Confirm the edition with
winverbefore retrying enrolment.
Home cannot be made to join Entra ID or enrol in Intune. Time spent looking for a way round this is time wasted.
The TPM is not a physical 2.0
You have this one if 0x800705b4 at Securing your hardware, and Get-Tpm shows no TPM, a 1.2 TPM, or the machine is a virtual one.
- Run
Get-Tpmand record TpmPresent, TpmReady and the reported specification version. - If there is no TPM, check UEFI firmware settings for a disabled security processor and enable it.
- If the TPM is 1.2, or the machine is virtual, self-deploying mode is not available on it; use user-driven deployment instead.
- Confirm the Windows build meets the minimum: 1709 or later, or 1809 or later for hybrid join.
The TPM firmware has not been upgraded to 2.0
You have this one if 0x801c03ea, and the hardware is listed by the manufacturer as TPM 2.0 capable but reports 1.2.
- Check the manufacturer’s support site for a TPM firmware upgrade for that exact model.
- Read their notes on what the upgrade clears. Suspend BitLocker and confirm you hold recovery keys first.
- Apply the firmware, confirm
Get-Tpmnow reports 2.0, then retry provisioning.
Microsoft names a second cause for this code that costs nothing to check: the same device assigned two different Autopilot profiles through two groups. Decide which profile should apply and remove the other assignment.
Attestation fails on an up-to-date Windows 11 device
You have this one if 0x81039023 during the pre-provisioning technician flow or self-deploying mode.
- Apply the May 2022 cumulative update for Windows 11 version 21H2, KB5013943, or any later cumulative update.
- Reimage with current media rather than patching at OOBE where you can – the update has to be present before provisioning starts.
- Retry the technician flow once the device is on a current build.
The TPM has known vulnerabilities
You have this one if 0x81039024 during pre-provisioning or self-deploying mode.
- Visit the PC manufacturer’s website and obtain the TPM firmware update for that model.
- Suspend BitLocker and confirm recovery keys are held before applying it.
- Apply the update, then retry provisioning.
This code is the attestation service refusing a TPM it does not trust. It is not a Windows or Intune fault and no configuration change bypasses it.
Full reference
What each code is gating
| Code | Stage | Requirement it enforces |
|---|---|---|
0x80180022 |
Enrolment | Windows Pro edition or higher |
0x800705b4 |
Securing your hardware | A physical TPM 2.0, and Windows 10 1709+ (1809+ for hybrid join) |
0x801c03ea |
Registering for mobile management | TPM upgraded to 2.0; or a single Autopilot profile assignment |
0x81039023 |
TPM attestation | KB5013943 or later on Windows 11 21H2 |
0x81039024 |
TPM attestation | TPM firmware without the known vulnerabilities |
Checking the hardware properly
Get-Tpm
msinfo32
Get-Tpm gives you TpmPresent, TpmReady, TpmEnabled and the manufacturer version. msinfo32 tells you whether the machine booted in UEFI mode and whether Secure Boot is available, which matters because the same devices that turn out to have no usable TPM are often the ones still running in legacy BIOS mode.
Windows Home in an organisation
- Home cannot join Microsoft Entra ID and cannot enrol in Intune. That is the edition boundary, not a configuration choice.
- An in-place upgrade to Pro through Settings, System, Activation preserves installed applications and user files.
- Devices bought retail in a hurry are the usual source. Audit for Home before a management rollout, not during one.
- The upgrade has to happen before Autopilot provisioning, not during it. A Home device will not get past enrolment to be upgraded by policy.
Self-deploying mode versus user-driven
The TPM 2.0 requirement belongs to self-deploying mode, where nobody signs in and the device has to prove its own identity to the service. User-driven deployment does not carry the same hardware requirement, because a user authenticates instead. If the hardware genuinely cannot meet it – older stock, virtual machines, TPM 1.2 – changing the deployment profile is a supported answer rather than a compromise.
When the hardware and edition both check out
- Confirm the device is assigned exactly one Autopilot profile. Two profiles from two groups is a documented cause of 0x801c03ea.
- Confirm the profile has finished assigning: the device must show a deployment profile with status Assigned before OOBE is run.
- Read the Microsoft-Windows-User Device Registration Admin log on the device, which carries the HResult behind the OOBE screen.
- Check the Windows build against the documented minimum before blaming the TPM; a device on an old build fails the same way.
- For a batch failing together, check whether a firmware update went out to that model recently. Attestation failures cluster by hardware model, not by user.
When a licence is the actual fix
Windows Home cannot be made to join Microsoft Entra ID or enrol in Intune, and Microsoft’s own remedy for 0x80180022 is one line: update the device to Pro edition or higher. That is a Windows 11 Pro licence applied as an in-place edition upgrade, which keeps the user’s files and applications and takes a few minutes plus a restart. It matters most for organisations that bought consumer laptops in a hurry and now need them managed. Note what it does not fix: 0x800705b4, 0x81039023 and 0x81039024 are hardware and firmware problems, and no licence changes a TPM. Arco supplies Windows 11 Pro upgrade licences and can confirm which of your devices are actually on Home before you order, so you buy for the machines that need it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80180022 |
“Autopilot device enrollment failed with error HRESULT = 0x80180022” – the device being provisioned is running Windows Home edition; update it to Pro or higher. The underlying constant is MENROLL_E_PROV_CSP_MISC | Microsoft Learn |
0x800705b4 |
“Securing your hardware (Failed: 0x800705b4)” – self-deploying mode requires a physical TPM 2.0 (virtual TPMs and TPM 1.2 do not work) and Windows 10 build 1709 or later, or 1809 or later with Entra hybrid join | Microsoft Learn |
0x801c03ea |
“Registering your device for mobile management (Failed: 3, 0x801C03EA)” – a TPM chip that supports 2.0 but has not been upgraded to 2.0; Microsoft also names a duplicate Autopilot profile assignment. The Windows Hello error list gives the same value as “Server failed to authorize user or device” | Microsoft Learn |
0x81039023 |
TPM attestation failure on Windows 11 during the pre-provisioning technician flow or self-deploying mode; apply the May 2022 cumulative update for Windows 11 21H2 (KB5013943) or later | Microsoft Learn |
0x81039024 |
TPM attestation failure indicating known vulnerabilities were detected with the TPM; update the TPM firmware from the PC manufacturer’s website | Microsoft Learn |
Confirm the fix worked
winverreports Pro, Enterprise or Education rather than Home.Get-Tpmreports TpmPresent and TpmReady True with specification version 2.0.- The device shows exactly one Autopilot deployment profile, with status Assigned.
- The Windows build meets the documented minimum for the deployment mode in use.
- OOBE completes through Securing your hardware and Registering your device without an error screen.
Questions people ask about this
Can Windows Home be enrolled in Intune with a policy or a workaround?
No. Microsoft’s documented resolution for 0x80180022 is to update the device to Pro edition or higher. Home cannot join Microsoft Entra ID, and enrolment depends on that.
Will an in-place upgrade to Pro lose the user’s data?
No. Changing the product key through Settings, System, Activation performs an edition upgrade that preserves installed applications and user files. It needs a restart.
Can we use Autopilot self-deploying mode on virtual machines?
No. Microsoft states the device must have a physical TPM 2.0 chip and that devices with virtual TPMs, such as Hyper-V VMs, do not work with self-deploying mode. User-driven deployment is the supported route for those.
The TPM says 1.2 but the vendor advertises 2.0. What now?
That is exactly the case 0x801c03ea describes: the chip supports 2.0 but the firmware has not been upgraded to it. Get the firmware upgrade from the manufacturer, and suspend BitLocker with recovery keys in hand before applying it.
Is 0x81039024 something we can fix in Intune?
No. It means attestation found known vulnerabilities in the TPM itself. The documented fix is a TPM firmware update from the PC manufacturer; nothing in Intune or Windows bypasses it.
