Home › Windows Autopilot › 0x801C01F1

Windows Autopilot · 0x801C01F1 · Windows 11 22H2

Windows Autopilot Error 0x801C01F1 on Windows 11 22H2 OOBE Failure

Autopilot profile download fails due to NTP sync or network issues during OOBE. Verify network connectivity and NTP configuration.

Error Details

FactValueSourceNote
Exact error code0x801C01F1OOBE error dialogDisplayed during Autopilot profile download
Affected OS buildWindows 11 22H2 (22621.x)System Information (msinfo32)Confirmed via OOBE context
Registry key for NTP settingsHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ParametersRegistry EditorVerify NtpServer value
Autopilot service endpointhttps://win.autopilot.microsoft.comNetwork request logsCheck connectivity to this URL
Log line signatureError downloading Autopilot profile: 0x801C01F1AutopilotSetup.logSearch for HTTP/timeout errors

Log Files to Check

What This Error Actually Means

The error code 0x801C01F1 is a hexadecimal representation of a Windows Device Management (WDM) error. Breaking it down: 0x801C identifies the component as the Windows Device Management service, while 01F1 (decimal 529) specifies the error type. This code is raised by the AutopilotSetup process during Out-of-Box Experience (OOBE) when the device fails to download its Autopilot profile from https://win.autopilot.microsoft.com. The root cause typically involves either network connectivity issues to the Autopilot service endpoint or misconfigured Network Time Protocol (NTP) settings preventing time synchronization. The error is logged in C:\$Windows.~BT\Logs\AutopilotSetup.log with the signature Error downloading Autopilot profile: 0x801C01F1, indicating a failure in the initial profile retrieval phase.

Affected Versions and Scope

This error is specific to **Windows 11 22H2 (build 22621.x)** and has been observed in tenants where strict NTP policies or network restrictions are enforced. It does **not** affect Windows 10 or earlier versions of Windows 11. The issue is most prevalent in environments where devices are enrolled in Autopilot with Azure AD hybrid join or where NTP servers are configured to non-Microsoft endpoints. Tenants using Microsoft-managed NTP (time.windows.com) or allowing outbound HTTPS to win.autopilot.microsoft.com are less likely to encounter this error. The error is also exclusive to devices provisioning via Autopilot; manually enrolled devices or those using traditional Windows Deployment Services (WDS) are unaffected.

Where To Look First: Logs and Event IDs

The primary diagnostic artifacts are located in two log files: - C:\$Windows.~BT\Logs\AutopilotSetup.log - C:\$Windows.~BT\Logs\WindowsSetup.log Use Get-Content -Path "C:\$Windows.~BT\Logs\AutopilotSetup.log" | Select-String "0x801C01F1" to identify the exact failure point. Look for lines containing Error downloading Autopilot profile: 0x801C01F1. In the Windows Event Viewer, check the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log for **Event ID 10001** (NTP sync failure) and **Event ID 10002** (Autopilot profile download failure). Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to extract relevant events. Network-related failures may also appear in the System log under **Event ID 6005/6006** (Network connectivity changes).

Root Causes

1. NTP Synchronization Failure

The device cannot synchronize with a valid NTP server, causing the Autopilot service to reject the request due to time drift. Verify the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters registry key for misconfigured Type or NtpServer values. Use Get-WinTime to check current time synchronization status.

2. Network Connectivity to Autopilot Endpoint

The device cannot reach win.autopilot.microsoft.com over HTTPS. Confirm with Test-NetConnection win.autopilot.microsoft.com -Port 443. Firewalls, proxies, or DNS misconfigurations often block this endpoint.

3. Misconfigured Proxy or TLS Settings

If the device uses a proxy, it may lack proper authentication for the Autopilot endpoint. Check Get-ItemProperty -Path "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" for proxy exceptions. TLS 1.2 must be enabled; use Test-TlsConnection win.autopilot.microsoft.com to validate.

Fix Procedure

  1. **Verify NTP Configuration** Run Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Parameters" -Name "NtpServer" -Value "time.windows.com,0x9" to reset to Microsoft's NTP server. Restart the Windows Time service with Restart-Service w32time.
  2. **Force NTP Sync** Execute w32tm /resync /now and check Get-WinTime for successful synchronization.
  3. **Test Autopilot Endpoint Connectivity** Use Test-NetConnection win.autopilot.microsoft.com -Port 443 to confirm reachability. If blocked, adjust firewall rules or proxy exceptions.
  4. **Deploy NTP Policy via Intune** In the **Intune admin center > Devices > Configuration profiles > Create profile**, select **Windows 10 and later > Administrative templates**. Configure the OMA-URI ./Device/Vendor/MSFT/Policy/Config/Time/ForceNtpUsage with a value of 1.
  5. **Check TLS Settings** Run Get-TlsCipherSuite and ensure TLS 1.2 is enabled. Use Set-TlsEccCurveOrder -CurveNames "P-256,P-384" if necessary.
Modifying NTP settings on enrolled devices may disrupt time-sensitive operations. Always test in a non-production environment first.

Error Code Variants

Error CodeDescriptionDistinguishing Factor
0x801C01F1Autopilot profile download failure due to NTP/network issuesLogged during OOBE with NTP sync failure in logs
0x801C01F2Autopilot profile download failure due to expired certificateAppears when TLS handshake fails with certificate errors
0x801C01F0Autopilot profile download failure due to invalid device IDOccurs when device enrollment ID is malformed or missing

Verification

After applying fixes, re-run Test-NetConnection win.autopilot.microsoft.com -Port 443 to confirm connectivity. Check C:\$Windows.~BT\Logs\AutopilotSetup.log for the line Autopilot profile successfully downloaded. In the **Intune admin center > Devices > All devices**, verify the device shows a status of Enrolled under **Windows enrollment**. Use Get-AutopilotDevice | Where-Object serialNumber -eq $serial to confirm the device is recognized.
Use dsregcmd /status during OOBE to quickly check enrollment progress and identify NTP or network issues in real time.

Prevention

Implement a **Windows 11 Baseline policy** in Intune to enforce NTP settings and TLS requirements. Navigate to **Intune admin center > Devices > Configuration profiles > Windows 10 and later > Baselines** and enable the **Time synchronization** and **TLS settings** policies. Additionally, deploy a PowerShell script via device configuration to audit NTP settings with Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Parameters" and automatically correct deviations. Regularly review **Autopilot device logs** in C:\$Windows.~BT\Logs using Get-Content -Path "C:\$Windows.~BT\Logs\AutopilotSetup.log" | Select-String "0x801C" to proactively identify patterns.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.