Windows Autopilot Setup Fails After Motherboard Replacement

Owatari, Fumitaka 0 Reputation points
2026-09-07T07:50:19.6466667+00:00

Issue Description After a motherboard replacement, the PC was reset, but the Windows Autopilot initial setup cannot be completed.

Error Code 80180014

Microsoft Security | Windows Autopilot
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-09-07T07:50:38.16+00:00

    Error 0x80180014 after a motherboard replacement is typically resolved by removing the old Windows Autopilot/Intune device state and then redeploying the device.

    Use this path:

    1. In the Microsoft Intune admin center, go to: Devices > Windows > Enrollment > Windows Autopilot > Devices.
    2. Select the affected device.
    3. Select Unblock device.
    4. Redeploy the Windows Autopilot deployment profile.

    Also verify that Windows MDM enrollment is allowed:

    1. In Intune admin center, go to: Devices > Windows > Enrollment > Enrollment options > Device platform restriction.
    2. Open All Users under Device type restrictions.
    3. Go to Properties > Edit next to Platform settings.
    4. Confirm Windows (MDM) is set to Allow.
    5. Repeat for any other enrollment restrictions that apply to the device’s assigned groups.

    Because the device had a motherboard replacement, Autopilot profile application can also fail after the hardware change. If the device shows Fix pending or Attention required in Windows Autopilot devices, the supported fix is to deregister and re-register the device.

    For a supported motherboard replacement scenario where the NIC card, HDD, and WLAN remain the same, the recommended sequence is:

    1. Deregister the damaged device.
    2. Replace the motherboard.
    3. Capture a new hardware hash.
    4. Re-register the repaired device.
    5. Reset the device back to OOBE.
    6. Run Windows Autopilot OOBE again.

    If the motherboard replacement included a system state where the motherboard has an enabled TPM and a second network interface that was not replaced with the motherboard, that scenario is not recommended because it can break the Windows Autopilot experience and make the device ID unstable.

    If the failure happens during pre-provisioning, collect diagnostics from the error screen:

    • Windows 10: select View diagnostics.
    • Windows 11: press CTRL+SHIFT+D and select Export Logs.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.