old user account keeps showing after autopilot

Matthew Jenkins 0 Reputation points
2026-07-07T14:56:39.03+00:00

the old user account keeps showing after autopilot has deployed. The primary user name has been removed. How do i get past this to continue with the build

Microsoft Security | Windows Autopilot
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-07-07T14:57:06.2566667+00:00

    For Windows Autopilot scenarios, an "old" user or owner can persist in a few different places even after deployment completes. The way to clear it depends on the join type and what exactly is still showing.

    1. If this is a Microsoft Entra join device and you want to reuse it for a new user
      Use Windows Autopilot Reset rather than a normal Windows reset or reimage:
    • Autopilot Reset:
      • Removes the device’s primary user (for remote Autopilot Reset).
      • Removes the device’s owner in Microsoft Entra.
      • Removes personal files, apps, and settings.
      • Reapplies the device’s original Autopilot settings.
      • Resets region, language, and keyboard to original values.
    • After Autopilot Reset completes, the next user who signs in becomes the new primary user and owner.

    This is the supported way to return a Microsoft Entra joined Autopilot device to a business‑ready state for a new user.

    1. If this is a Microsoft Entra hybrid join device
      Windows Autopilot Reset does not support Microsoft Entra hybrid join devices. In that case:
    • Perform a device wipe from Intune for the hybrid‑joined device.
    • Be aware that after a full device reset, it can take up to 24 hours before the device is ready to be deployed again. This can be expedited by re‑registering the device in Autopilot.
    • For reuse scenarios, consider the Windows Autopilot for existing devices workflow, which is designed to wipe and redeploy existing hardware.
    1. If the issue is that an old user/owner is still visible in Intune or Entra after reset
      For Microsoft Entra joined devices, a remote Autopilot Reset explicitly removes:
    • The device’s primary user (Intune).
    • The device’s owner in Microsoft Entra.

    After the reset, allow the next user to sign in through the Autopilot flow; that user will be set as the new primary user/owner. If the device is hybrid‑joined, use wipe + re‑registration as above.

    1. If the old account is a local or on‑premises AD account still appearing on the device
      In hybrid scenarios, if a local/on‑premises user object is still tied to the device and causing sign‑in or profile issues, the practical fix can be to:
    • Remove the old user object in on‑premises Active Directory and recreate it cleanly if needed.
    • On the device, clear any stored credentials (for example, in Credential Manager) that reference the old account.

    This approach has been used successfully when an old identity continued to appear or be used even after profile changes.

    Using the correct reset/wipe method for the join type and, for hybrid/on‑premises identities, cleaning up the old AD user object and stored credentials should allow the build to proceed without the old account reappearing.

    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.