Windows Device Setup Fails with “Setup Incomplete” Error

Question

Users are unable to complete the device setup process and receive a “Setup incomplete” error. The issue appears to be related to the device enrollment or configuration process. How can we troubleshoot the enrollment configuration and refresh the required settings to allow the device setup to complete successfully?

Answer 1

which screen does it die on, and is there an error code under it? if it's the enrollment status page, grab mdmdiagnosticstool.exe -area Autopilot -cab c:\temp\ap.cab from shift+f10 before anyone resets, then run Get-AutopilotDiagnostics -CABFile against it (Install-Script Get-AutopilotDiagnostics first). that shows which phase and which app or policy it was waiting on, which is faster than guessing at join state.

Answer 2

Hello George,

The “Setup incomplete” error usually means the device enrollment didn’t finish correctly. First, confirm in Settings > Accounts > Access work or school that the organization account is connected. If it isn’t, remove any stale device records from Azure AD and Intune, then re-enroll. If the account is present but Intune enrollment failed, run dsregcmd /status to check join status. If you see AzureAdJoined : YES but Intune MDM : NO, reconnect the account through ms-settings:workplace or trigger enrollment via Company Portal.

For Autopilot, make sure the device hash is registered and assigned to a deployment profile. If the profile is missing, reassign it and reset the device with systemreset -factoryreset. Also review logs under DeviceManagement-Enterprise-Diagnostics-Provider for errors like 0x80180018, which point to policy failures. Clearing the enrollment cache at C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\MDM and re-enrolling often resolves these.

In short, the fix is to ensure proper Azure AD join, Intune enrollment, and correct Autopilot profile assignment. Once those are aligned, the setup should complete without error.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HP.

Answer 3

Use this troubleshooting path for Windows device setup failures tied to enrollment or configuration:

1. Verify Intune enrollment prerequisites.
   • Confirm the affected user has a valid Intune license.
   • Confirm automatic MDM enrollment is enabled for the users who should enroll devices.
   • Confirm the device is running a supported version of Windows.
2. If enrollment is done through Group Policy autoenrollment, verify device join state.
   • On the device, run dsregcmd /status.
   • For Microsoft Entra hybrid join, confirm AzureAdJoined = YES and DomainJoined = YES.
   • Also confirm AzureAdPrt = YES in the SSO State section.
   • If these values are not correct, fix the hybrid join state first before retrying enrollment.
3. Check whether Intune is blocking Windows enrollment.
   • In the Microsoft Intune admin center, go to Devices > Enrollment restrictions.
   • Open the relevant device type restriction.
   • Select Properties > Edit next to Platform settings.
   • Make sure Windows (MDM) is set to Allow.
   • Save the change.
4. If users are setting up devices with Set up for work or school during OOBE and enrollment fails, check personal device restrictions.
   • This enrollment path can classify the device as a personal device.
   • If personal device enrollment is blocked, setup can fail with enrollment errors such as 80180014.
   • In the Microsoft Intune admin center, go to Devices > Enroll devices > Enrollment device platform restrictions.
   • Select Windows restrictions > Create restriction.
   • On Platform settings, set Personally owned devices to Allow.
   • Assign the restriction only to the users or groups that need personal Windows enrollment.
5. Refresh enrollment diagnostics during OOBE if the failure occurs in Autopilot or enrollment status processing.
   • Press Shift + F10 during OOBE to open Command Prompt.
   • Run:

          %windir%\system32\mdmdiagnosticstool.exe -area Autopilot;DeviceEnrollment -cab %temp%\autopilot-logs.cab
     

   • Review the generated CAB for Autopilot and DeviceEnrollment failures.
6. If the setup stalls during device preparation with timeout 0x800705b4, inspect client installation state.
   • Run:

          $key = 'HKLM:\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking\Device\DevicePreparation\PolicyProviders\ConfigMgr'
          Get-ItemPropertyValue -Path $key -Name InstallationState
     

   • Expected values:
     • 1 = Not installed
     • 2 = Not required
     • 3 = Complete
     • 4 = Error
   • If the state is not 3, review %windir%\ccmsetup\Logs\ccmsetup.log and confirm the device received CCMSetup.msi from Intune and full client content from the CMG.
7. Re-run setup after correcting the enrollment configuration.
   • For Windows 365 Cloud PCs, reset the Cloud PC after fixing the Intune or MDM configuration so setup runs again.
   • If setup still fails after the reset, open a support request.

This sequence addresses the main causes of setup-incomplete scenarios: missing licensing, disabled autoenrollment, incorrect Microsoft Entra join state, blocked Windows MDM enrollment, blocked personal device enrollment, and Autopilot/ESP timeout during client installation.

---

• Diagnose MDM enrollment
• Troubleshooting Windows device enrollment errors in Intune
• Unblock Windows "Set up for work or school" enrollment
• How to enroll with Windows Autopilot
• Troubleshoot Windows 365 Business Cloud PC setup issues