Fix it now
0x801c03f3 means Entra ID cannot find a device object for the machine being deployed, usually because it was manually deleted. 8018000A means the opposite: the device is already enrolled, by someone else. Both are record problems, and the order you clean them up in matters.
Get-WindowsAutopilotInfo -OutputFile C:\Temp\hash.csv
- For 8018000A, try the non-destructive fix first: on the device, Settings, Accounts, Access work or school, sign in as the account that enrolled it, remove the work or school account, then re-enrol.
- For 0x801c03f3, find the device in the Intune admin centre: Devices, Windows, Enrollment, Windows Autopilot, Devices, and search the serial number.
- Delete the device from Intune first. Then deregister it from Windows Autopilot. That is the documented order.
- Do not manually delete the Microsoft Entra device object. Microsoft warns this causes enrolment failures, because Autopilot depends on it. For hybrid joined devices, delete the on-premises AD computer object instead.
- Re-register the hardware hash, wait until the device shows a deployment profile with status Assigned, then run OOBE again.
Manually deleting the Entra device object is one documented way to produce the 0x801c03f3 this article is about.
If provisioning completes you can stop here. If not, the next section explains what each of these six codes actually points at.
Why it happens
Autopilot depends on three records staying in step: the hardware hash registered with the Windows Autopilot service, the Microsoft Entra device object, and the Intune device record. A reimage, a manual clean-up or a device that changed hands leaves them disagreeing, and the codes you get tell you which way they disagree.
0x801c03f3 is the missing-object direction. Microsoft’s Autopilot known issues describe it exactly: Entra ID cannot find a Microsoft Entra device object for the device being deployed, and this happens when the object was manually deleted. The remedy is to remove the device from Entra ID, Intune and Windows Autopilot and re-register it, which recreates the object. 8018000A is the other direction, MENROLL_E_DEVICE_ALREADY_ENROLLED: a different user has already enrolled the device in Intune or joined it to Entra ID.
The deletion order is the part people get wrong, and getting it wrong causes the failure. Microsoft’s registration overview is explicit: delete the device from Intune, then deregister it from Windows Autopilot. For Entra joined devices no further step is needed, and Microsoft says plainly “Avoid manually deleting the device from Microsoft Entra ID, as this can cause unexpected issues” and “The Windows Autopilot deployment process relies on the Microsoft Entra device object, and deleting it can cause enrollment failures.” For hybrid joined devices you delete the computer object from on-premises AD DS so it is not resynced – still not from Entra ID directly.
The three remaining codes are each their own fault, and none is a licensing or scope refusal. 0x8007064c is “The machine is already enrolled”. 0x80070774 is most commonly a hybrid Entra join deployment with Assign user configured in the Autopilot profile. 0x80180005 is MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR: a failure at the management server, such as a database access error.
Another account already enrolled the device
You have this one if 8018000A – “Something went wrong. The device is already enrolled” – on a machine that has been in service rather than a new one.
- Sign out of Windows and sign in with the account that enrolled or joined the device.
- Open Settings, Accounts, Access work or school and remove the existing work or school account.
- Sign out, sign in with the intended account, and enrol again.
Try this before any reset. 8018000A frequently appears on in-service machines holding live user data, and a reset erases it.
Resetting a device erases local data. On any machine that has been in use, back it up and confirm the user has nothing local before you reset, and treat the reset as the last option rather than step five.
The Entra device object was deleted by hand
You have this one if 0x801c03f3, logged as an HResult in the Microsoft-Windows-User Device Registration Admin log, on a device that was previously deployed successfully.
- Delete the device record from Intune: Devices, then select the device and Delete.
- Deregister it from Windows Autopilot: Devices, Windows, Enrollment, Windows Autopilot, Devices, select the device, Delete.
- Do not delete the Entra device object manually. For a hybrid joined device, delete the on-premises AD DS computer object so it is not resynced.
- Re-register the hardware hash and wait for the deployment profile to show Assigned before running OOBE.
Microsoft warns that skipping steps or removing records out of order results in orphaned records or unrecoverable devices. Work through them in the order above.
A stale enrolment is still on the machine
You have this one if 0x8007064c, typically on a cloned image or a machine that was enrolled before.
- Delete the Intune certificate issued by Sc_Online_Issuing from Certificates (Local Computer), Personal, Certificates.
- Delete
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OnlineManagementand all its subkeys. - Retry enrolment.
- If it still fails, delete
HKEY_CLASSES_ROOT\Installer\Products\6985F0077D3EEB44AB6849B5D7913E95and retry.
If this is appearing across a batch, the reference image was captured after enrolment. Fix the image rather than each machine.
Hybrid join with a user assigned to the Autopilot device
You have this one if 0x80070774 on a hybrid Entra join deployment.
- In the Intune admin centre open Devices, Windows, Windows devices, select the device, use the ellipsis and choose Unassign user.
- Wait for it to finish, confirm the hybrid Autopilot profile is assigned, then re-run OOBE.
- If it persists, check the Offline Domain Join Intune Connector server for Event ID 30132 in the ODJ Connector Service log, which points at OU delegation.
- Delegate Create and Delete computer objects, with Full Control, to the Connector’s computer account on the target OU.
Assign user performs an Entra join at the sign-in screen, which leaves the device unable to join the on-premises domain. It belongs to standard Entra join deployments, not hybrid ones.
The service itself failed the request
You have this one if 0x80180005, with no pattern by user, device or profile.
- Treat it as service-side: retry, and check the Microsoft 365 service health dashboard for Intune advisories.
- Collect evidence in case it persists:
MdmDiagnosticsTool.exe -area DeviceEnrollment -cab C:\Temp\mdm.cab.
Full reference
What each code points at
| Code | Published meaning |
|---|---|
0x801c03f3 |
Entra ID cannot find a Microsoft Entra device object for the device being deployed – the object was manually deleted |
0x801c03f2 |
Windows Hello key registration failed, ERROR_BAD_DIRECTORY_REQUEST: another object already has the same proxyAddresses value |
8018000A |
MENROLL_E_DEVICE_ALREADY_ENROLLED – a different user already enrolled or joined the device |
0x8007064c |
The machine is already enrolled: a previous enrolment, a cloned image, or a leftover account certificate |
0x80070774 |
Hybrid Entra join with Assign user configured in the Autopilot profile; or the Autopilot object’s associated Entra device was deleted |
0x80180005 |
MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR – a failure at the management server, such as a database access error |
The deletion order, in full
- Delete the device from Intune: Devices, select the device, Delete.
- Deregister it from Windows Autopilot: Devices, Windows, Enrollment, Windows Autopilot, Devices, select the device, Delete.
- For a Microsoft Entra joined device, stop. No further step is required, and manually deleting the Entra object causes enrolment failures.
- For a Microsoft Entra hybrid joined device, delete the computer object from on-premises AD DS so it is not resynced. Still do not delete the Entra object by hand.
- Re-register the hardware hash and wait for the deployment profile to show Assigned before touching the device again.
Duplicate directory attributes
0x801c03f2 belongs to a different investigation from the rest of this article. It is a Windows Hello key registration failure with the underlying error ERROR_BAD_DIRECTORY_REQUEST, and Microsoft’s description is specific: another object with the same value for the proxyAddresses property already exists. That is a duplicate attribute blocking directory synchronisation, not a missing device object. Microsoft also notes that where no sync conflict exists, the Mail or Email address in Entra ID and the primary SMTP address in the proxy addresses should match.
Collecting a hardware hash
Get-WindowsAutopilotInfo -OutputFile C:\Temp\hash.csv
Your hardware supplier can also provide the hash as a CSV at the point of purchase, which is the better route at any scale. Collecting it by hand at OOBE is fine for one or two machines and unmanageable for fifty.
Where to read the real reason
- Microsoft-Windows-User Device Registration, Admin log – carries the HResult behind an OOBE error screen, including 0x801c03f3.
- DeviceManagement-Enterprise-Diagnostic-Provider, Admin log – carries the MDM enrolment result and the Win32 code.
- The ODJ Connector Service log on the Offline Domain Join connector server – Event ID 30132 is Microsoft’s named signal that OU permissions are wrong.
MdmDiagnosticsTool.exe -area DeviceEnrollment -cab C:\Temp\mdm.cabfor a single collected package.
Names and paths that have changed
The Autopilot device list lives at Devices, Windows, Enrollment, Windows Autopilot, Devices. The node that controls which platforms may enrol is called Device platform restriction and sits under Devices, Device onboarding, Enrollment. If you are working from older notes that call it Enrolment restrictions and put the Autopilot list somewhere else, the notes are behind the portal.
When a licence is the actual fix
None of the six codes in this article is a licensing refusal, and cleaning up device records costs nothing. The licensing question sits one step to the side: the account signing in at OOBE does need a licence that includes Microsoft Intune, and Microsoft documents that case separately, with the message “This account is not allowed on this phone” and the instruction to assign a valid licence. If that is where you have actually landed, Microsoft Intune Plan 1 covers device enrolment and management standalone, and it is also bundled inside several Microsoft 365 plans – so check what you already own before ordering. Arco can tell you which of your existing subscriptions already carry Intune rights and supply Plan 1 only for the users who are not covered.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x801c03f3 |
Microsoft Entra ID cannot find a Microsoft Entra device object for the device being deployed, because the object was manually deleted. Deregister and re-register the device with Windows Autopilot to recreate it | Microsoft Learn |
0x801c03f2 |
Windows Hello key registration failed with ERROR_BAD_DIRECTORY_REQUEST: another object with the same proxyAddresses value already exists. A duplicate directory attribute, not a missing device record | Microsoft Learn |
8018000A |
MENROLL_E_DEVICE_ALREADY_ENROLLED – “The device is already enrolled”. A different user has already enrolled it in Intune or joined it to Entra ID | Microsoft Learn |
0x8007064c |
“The machine is already enrolled” – a previous enrolment, a cloned image of an enrolled machine, or the previous account’s certificate still present | Microsoft Learn |
0x80070774 |
Most commonly, hybrid Entra join with the Assign user feature configured in the Autopilot profile, which Entra joins the device at the sign-in screen and leaves it unable to join the on-premises domain. Second documented cause: the Autopilot object’s associated Entra device was deleted | Microsoft Learn |
0x80180005 |
MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR – “There was a failure at the management server, such as a database access error” | Microsoft Learn |
Confirm the fix worked
- The device appears once in the Windows Autopilot device list with a deployment profile status of Assigned.
- There is exactly one Intune device record and one Entra device object for that serial number.
- OOBE completes through device registration and enrolment without an error screen.
- For a hybrid deployment, the device has no assigned user on its Autopilot record.
- The Microsoft-Windows-User Device Registration Admin log records a successful registration rather than an HResult.
Questions people ask about this
Can I just delete all three records to start clean?
Only in the right order, and the Entra object is not one you delete by hand. Microsoft’s order is: delete from Intune, then deregister from Windows Autopilot. For Entra joined devices nothing else is needed; for hybrid joined devices delete the on-premises AD computer object. Microsoft warns that deleting the Entra device object manually can cause enrolment failures.
Do I have to wipe the machine to clear 8018000A?
No, and you should not start there. Microsoft’s documented fix is to sign in with the account that enrolled the device, remove the work or school account under Settings, Accounts, Access work or school, and enrol again. A reset erases local data and belongs last.
Is 0x8007064c an application install failure?
No. Microsoft documents it as “The machine is already enrolled”, caused by a previous enrolment, a cloned image or a leftover account certificate. The fix is to remove the Sc_Online_Issuing certificate and the OnlineManagement registry key, then re-enrol.
Why does hybrid join fail with 0x80070774 when the DC is reachable?
Because the most common documented cause is not connectivity. If Assign user is configured in the Autopilot profile, the device performs an Entra join at the sign-in screen and cannot then join the on-premises domain. Unassign the user first, before working through connector and OU permissions.
How long should I wait after re-registering a hash?
Until the device shows a deployment profile with status Assigned in the Autopilot device list. Running OOBE before that is the commonest reason a correctly re-registered device still fails.
