Forum Discussion

uzairahmad's avatar
uzairahmad
Copper Contributor
Mar 25, 2026

Windows Autopilot Hybrid Join failing with OOBE error 80004005

Hello everyone,

We’re facing a consistent issue with Windows Autopilot user‑driven Microsoft Entra hybrid join where devices are provisioned using a Hybrid Join Autopilot profile, but Hybrid Join does not complete.

 

Setup (High level)

  • Windows Autopilot (user‑driven)
  • Autopilot profile: Microsoft Entra hybrid joined
  • Only one Autopilot profile
  • Domain Join profile configured (domain + OU)
  • Entra Connect: Hybrid Join + device writeback enabled
  • Intune Connector for Active Directory installed and healthy
  • MDM auto‑enrollment enabled

 

Issue

During Autopilot OOBE, the device frequently shows:

“Something went wrong”
Error code: 80004005

Despite this, Autopilot continues and completes.

 

Resulting Device State

After provisioning:

  • Device appears in Entra ID as Microsoft Entra joined (not Hybrid)
  • Device is enrolled into Intune and shows compliant
  • Device‑scoped Intune MDM policies do not apply
  • dsregcmd confirms Hybrid Join never completed

 

Understanding So Far

From correlating the OOBE error, dsregcmd output, and final device state:

  • Hybrid Join starts but fails mid‑process
  • Windows does not roll back provisioning
  • Device falls back to Entra ID Join
  • Join type is finalized for that run
  • Resetting without fixing the root cause repeats the behavior

This explains why devices look healthy but are not Hybrid Joined and why device‑based policies don’t reflect.

 

Questions

  1. Is 80004005 during Autopilot OOBE a known indicator of Hybrid Join / Offline Domain Join failure?
  2. Is fallback from Hybrid Join → Entra ID Join expected when Hybrid Join prerequisites fail?
  3. Once a device ends up Entra joined, is wipe + reprovision the only supported recovery after fixing the root cause?
  4. Public Wi‑Fi / offsite scenario:
    Has anyone successfully completed Hybrid Autopilot using pre‑logon VPN / device tunnel (Always On VPN, GlobalProtect, AnyConnect, etc.) to provide DC line‑of‑sight?
  5. Which logs are most useful to confirm the exact failure point (ODJ, dsreg, Intune Connector, ESP)?

 

Thanks in advance for any insights or field experience.

Autopilot
Intune

1 Reply

  • Equebal's avatar
    Equebal
    Copper Contributor
    Mar 26, 2026

    Error code 0x80004005 is a generic “Unspecified Error” in Windows, typically caused by permission issues, blocked file access, or network errors. Please review the article below to verify whether the Intune Connector server has the required access for computer account creation. While the article addresses a different scenario, the reference logs may still help in identifying the root cause.

    Could you also confirm whether this issue is occurring across all devices or only randomly? Additionally, how many Intune Connector servers are present in your environment?

    https://techuisitive.com/how-to-fix-autopilot-error-80070002/