Share via

Enrolling a new laptop in our environment but does not allow to enroll - error code 80004005

Ankur Chandel 5 Reputation points
2026-01-16T00:43:22.32+00:00

Tried registering the device gets an error message 80004005.

The hardware hash key upload was completed successfully but stil the issue persists

Azure IoT Operations
Azure IoT Operations

Azure IoT Operations is a set of modular services enabled by Azure Arc.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Leonardo Mariano Côco 155 Reputation points
    2026-01-16T01:07:17.22+00:00

    Hi Ankur — 80004005 is a very generic Windows enrollment/Autopilot error, and the hardware hash upload being “successful” doesn’t guarantee the device is actually ready to enroll.

    The most common reasons I’ve seen for this are:

    1. The device is already registered somewhere else

    It may already exist in Autopilot (or even in another tenant). Search the device by serial number in the Autopilot devices list. If it’s duplicated/stale, remove it and re-import.

    Autopilot profile / assignment hasn’t applied yet

    After import, it can take time for the device to get a profile. Confirm the device shows an assigned profile (not “Not assigned”) and that the group assignment is correct.

    MDM/Intune enrollment is blocked

    Check the user has the right Intune license, MDM user scope includes the user, and enrollment restrictions/device limit aren’t blocking Windows enrollment.

    If you want to narrow it fast, reply with:

    Is this Windows Autopilot + Intune?

    What join method (AAD join / Hybrid / Azure AD registered)?

    Where exactly does it fail (OOBE, Company Portal, “Access work or school”)?

    With those 3 details, it’s usually possible to pinpoint the exact cause in one step.Hi Ankur — 80004005 is a very generic Windows enrollment/Autopilot error, and the hardware hash upload being “successful” doesn’t guarantee the device is actually ready to enroll.

    The most common reasons I’ve seen for this are:

    The device is already registered somewhere else

    It may already exist in Autopilot (or even in another tenant). Search the device by serial number in the Autopilot devices list. If it’s duplicated/stale, remove it and re-import.

    Autopilot profile / assignment hasn’t applied yet

    After import, it can take time for the device to get a profile. Confirm the device shows an assigned profile (not “Not assigned”) and that the group assignment is correct.

    MDM/Intune enrollment is blocked

    Check the user has the right Intune license, MDM user scope includes the user, and enrollment restrictions/device limit aren’t blocking Windows enrollment.

    If you want to narrow it fast, reply with:

    Is this Windows Autopilot + Intune?

    What join method (AAD join / Hybrid / Azure AD registered)?

    Where exactly does it fail (OOBE, Company Portal, “Access work or school”)?

    With those 3 details, it’s usually possible to pinpoint the exact cause in one step.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.