Is your Windows 11 PC stuck in a deployment limbo, refusing to proceed with Autopilot? You’re not alone. Windows Autopilot is a revolutionary cloud-based deployment service, but when it fails, it can leave IT administrators and users staring at frustrating error screens. This comprehensive guide will walk you through a step-by-step diagnostic and repair process to get your Autopilot not working issue resolved and your devices provisioned seamlessly.
We’ll go beyond basic checklists. This article draws from real-world IT administration experience and deep-dives into the underlying technology, providing not just solutions but the why behind them. You’ll learn to think like a support engineer and tackle everything from simple misconfigurations to complex network and hardware issues.
Understanding Windows Autopilot: A Quick Refresher
Before we fix it, let’s briefly understand what we’re fixing. Windows Autopilot is Microsoft’s modern solution for deploying and pre-configuring Windows devices. Instead of manually imaging each laptop, Autopilot uses a unique device fingerprint (hardware hash) registered in Microsoft Intune. When a user signs in with their corporate credentials on a fresh Out-Of-Box-Experience (OOBE), Autopilot fetches the deployment profile and configures the device automatically.
A failure typically manifests during OOBE with errors like:
- “Something went wrong. Try again.”
- “We can’t connect to your organization’s server.”
- The device simply loops back to the initial setup screen.
- It gets stuck on “Setting up a few more things for you” or similar.
Step-by-Step Troubleshooting: Diagnosing & Fixing Autopilot Failures
Follow this structured approach. Start from the top, as these are the most common and easily resolved issues.
Step 1: The Foundation Checks (Device & Registration)
Often, the problem is at the very beginning.
1. Verify Device Registration in Intune:
- Navigate to the Microsoft Intune admin center.
- Go to Devices > Windows > Windows enrollment > Devices.
- Search for the device by serial number. Is it listed? Its Autopilot state should be “Assigned” with a valid profile.
Fix: If the device is missing, the hardware hash wasn’t uploaded correctly. You must re-register it. Boot the device to a working Windows OS, run PowerShell as Administrator, and use the Get-WindowsAutopilotInfo script (from the PowerShell Gallery) to extract and upload the hash again.
2. Confirm Profile Assignment:
- In the same Intune Devices list, click on the problematic device.
- Check the Assigned profile. Is it the correct one? Does the profile have all necessary configurations?
Fix: Ensure the profile is assigned to the right Azure AD group containing the device or user. Review the profile settings for any conflicts or misconfigured policies.
Step 2: Network & Connectivity Diagnostics
Autopilot is cloud-driven. No internet = no deployment.
3. Check Internet Access During OOBE:
- The OOBE screen requires a Microsoft Entra ID (formerly Azure AD) connection. On the “Let’s connect you to a network” screen, ensure you’re connected to a network that allows access to essential Microsoft endpoints.
Fix: Use a wired Ethernet connection if possible to rule out Wi-Fi driver or certificate issues. If using corporate Wi-Fi that requires a pre-login (captive portal), this will block Autopilot. Devices must be on an open network or one where the connection is automatically granted.
4. Validate Required URLs are Accessible:
The device must reach specific Microsoft endpoints. The most critical ones are:
login.live.comlogin.microsoftonline.comenterpriseregistration.windows.netdevice.login.microsoftonline.com*.manage.microsoft.com
Fix: Provide this list to your network team. Ensure these URLs are not blocked by firewalls or proxies. For a complete list, refer to Microsoft’s official documentation on Network configuration requirements for Microsoft Intune.
Step 3: Intune & Azure AD Configuration Audit
The back-end settings must be perfect.
5. Review Enrollment Restrictions:
- In Intune, go to Devices > Windows > Windows enrollment > Enrollment Restrictions.
- Check the default or targeted restrictions. Is Windows (Autopilot) allowed? Is the correct platform (Windows 10/11) selected?
6. Verify Azure AD Join Permissions:
- In the Microsoft Entra admin center, go to Users > User settings.
- Review Restrict access to Azure AD administration portal – this should not block user enrollment.
- More importantly, go to Devices > Device settings. Ensure Users may join devices to Azure AD is set to All or a appropriately scoped group.
Fix: Adjust these settings. A common mistake is having too restrictive Azure AD join settings.


Step 4: Advanced & Hardware-Specific Troubleshooting
If the basics check out, dig deeper.
7. Check for Time Synchronization:
An incorrect system time can break SSL certificate validation, halting the cloud handshake.
Fix: In OOBE, you can’t easily change time. If you suspect this, boot from a local admin account (if available) and sync time, or ensure the device’s BIOS time is correct.
8. Remove Conflicting Local Policies or Old Images:
If the device was previously used or imaged with other tools, residual configurations can interfere.
Fix: Perform a clean Windows 11 installation using the latest Microsoft Media Creation Tool. This ensures no legacy Group Policies or scripts remain. Then, trigger Autopilot again.
9. Driver and TPM Issues:
- Network Drivers: Lack of native drivers for Wi-Fi/Ethernet in the Windows 11 base image can prevent connectivity. This is prevalent on newer or custom hardware.
- TPM: Autopilot can require a functioning TPM (Trusted Platform Module) for certain authentication scenarios.
Fix:
- For driver issues, use a USB Ethernet adapter with native Windows drivers or inject necessary network drivers into your Windows image beforehand.
- For TPM, enter the device BIOS/UEFI and ensure TPM 2.0 is enabled and cleared.
Step 5: Leveraging Logs for Deep Forensics
When all else fails, the logs tell the story.
10. Collect and Analyze Autopilot Diagnostics Logs:
During OOBE, you can press Shift + F10 to open a Command Prompt.
- Navigate to:
cd C:WindowsProvisioningLogs - The key file is AutopilotDDSZTDFile.json. View it with
notepad AutopilotDDSZTDFile.json. - Look for clear error messages, HTTP status codes (like 403 Forbidden, 404 Not Found), or failed steps.
11. Use the Client Analyzer Tool:
Microsoft provides a powerful, web-based Microsoft Intune Management Extension (IME) Troubleshooter (link to the tool). While more useful post-enrollment, its diagnostic capabilities can provide clues about the environment.
Unique Perspective: The Common Pitfall Everyone Misses – The User Object
From my experience managing deployments for hundreds of devices, one elusive issue stands out: The Azure AD User Object State.
Autopilot isn’t just about the device; it’s a conversation between the device and the user’s identity. If the user’s Azure AD account has issues, Autopilot will fail silently or cryptically.
Always check:
- Is the user’s account licensed for Intune/Windows 365? (An EMS E3 or Microsoft 365 Business Premium license, for example).
- Is the account enabled and not blocked?
- Is the user a member of the correct groups for profile assignment?
- Has the user hit any service limits (like device enrollment quotas)?
I once spent hours debugging a “can’t connect” error only to find the user had accidentally been added to a dynamic group with a misconfigured rule, excluding them from all device enrollment policies. The fix was a 30-second group membership change.
Prevention: Best Practices for Flawless Autopilot Deployment
- Pre-register Everything: Upload hardware hashes for all devices before they ever reach the user.
- Use Dynamic Azure AD Groups: Assign Autopilot profiles to groups based on device attributes (like
deviceName -contains "IT-")for automatic, error-free assignment. - Maintain a “Golden” Network: Have a dedicated, open SSID (like “Corp-Provisioning”) with unfettered access to Microsoft endpoints for initial setup.
- Test Extensively: Pilot new Autopilot profiles with a small device group before company-wide rollout.
- Document Your Process: Keep a runbook of your registration and hash upload process to avoid simple mistakes.
Final Resort: Microsoft Support and Community
If you’ve exhausted all options:
- File a support request through the Microsoft 365 admin center. Provide your correlation IDs and detailed logs.
- Leverage the community wisdom on the Microsoft Tech Community, especially the Intune and Windows 11 forums. Many obscure issues have been solved there.
Conclusion
Fixing Autopilot not working in Windows 11 is a systematic process of elimination. Start with the device registration and network, move through Intune and Azure AD settings, and finally delve into hardware and logs. By understanding the service flow and using this guide as your roadmap, you can transform deployment headaches into a streamlined, automated process.
Remember, Autopilot is a powerful tool that represents the future of IT management. With careful setup and proactive troubleshooting, you can ensure your users experience the “magic” of self-deploying devices, boosting both productivity and satisfaction.
Disclaimer: This guide is based on experience with Windows 11 and Autopilot as of 2023. Microsoft frequently updates its services, so always refer to the latest official Microsoft Learn documentation for the most current procedures.


