Fixing Windows 11 Entra ID Join Error 80190190 After a Lost Intune/Entra Registration⌗

I recently ran into an odd but increasingly common issue on a Windows 11 laptop that had previously been:

  • Intune enrolled
  • Microsoft Entra ID joined
  • Fully managed and working as expected

For reasons that weren’t immediately clear, the device had fallen out of Entra ID and was now operating purely as a local account machine. No Azure AD/Entra join, no MDM enrolment, and no access to organisational resources.

When attempting to re-join the device to Entra ID, Windows returned the following error:

Something went wrong. Confirm you are using the correct sign-in information and that your organization uses this feature… Error code: 80190190.

This post documents the root cause and the surprisingly simple registry fix that resolved it.

Symptoms⌗

  • Device previously Entra-joined and Intune-managed
  • Device now shows local account only
  • Attempting Access work or school → Connect → Join this device to Microsoft Entra ID fails
  • Error shown: 80190190
  • No meaningful server message or correlation ID

This error is frustrating because it looks like an authentication or tenant issue, but in this case the problem was entirely local to the device.

Root Cause⌗

The issue was caused by a leftover configuration in the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments

Inside one of the enrolment GUID keys was the value:

MmpcEnrollmentFlag = 2

This flag indicates a special or incomplete MDM enrolment state, which prevents Windows from performing a normal Entra ID join.

In short:

  • The device thought it was still partially enrolled
  • Entra ID join logic therefore refused to proceed
  • Windows surfaced the generic 80190190 error instead of a clear explanation

The Fix⌗

Setting the flag back to 0 immediately resolved the issue and allowed the device to join Entra ID normally.

Steps⌗

  1. Open Registry Editor as Administrator

  2. Navigate to:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments

  3. Locate the subkey containing:

    MmpcEnrollmentFlag

  4. Change the value to:

    0

  5. Close Registry Editor

  6. Retry Join this device to Microsoft Entra ID

The join completed successfully, and the device re-enrolled into Intune without further issues.

Why This Happens⌗

Although Microsoft doesn’t document this flag in detail, scenarios that can leave devices in this half-enrolled state include:

  • Interrupted Intune unenrolment
  • Device reset without proper removal from Entra ID
  • Tenant switching or Autopilot reassignment
  • Manual registry or profile cleanup
  • MDM migration between tenants

Windows keeps historical enrolment artefacts, and occasionally these block re-registration rather than being safely ignored.

Safer Alternatives Before Editing the Registry⌗

In production environments, I’d normally attempt:

  • dsregcmd /status to confirm join state
  • dsregcmd /leave followed by reboot
  • Removing old Work or School accounts
  • Deleting stale device objects in Entra ID
  • Running Intune device cleanup scripts

However, in this case none of those cleared the hidden enrolment flag.

The registry edit was the only effective fix.

Final Thoughts⌗

This is a great example of how:

  • Entra/Intune failures often present as cloud or authentication errors
  • The real cause can be a tiny local configuration artefact
  • A single DWORD value can block the entire device lifecycle

If you hit error 80190190 when re-joining a previously managed Windows 11 device, check the Enrollments registry key before spending hours chasing tenant or licensing problems.

Hopefully this saves someone else the same troubleshooting rabbit hole.

If you manage Microsoft 365 or Intune environments and enjoy practical fixes like this, keep an eye out for more field notes soon.