Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x801C0101 | Windows Autopilot logs (OOBE.log) | -> Indicates network connectivity timeout during OOBE. |
| Affected OS build | Windows 11 22H2 | Microsoft documentation | -> Confirmed in builds 22621 and above. |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE | Windows Registry | -> Contains OOBE configuration settings. |
| Relevant service/endpoint URL | https://provisioningapi.microsoft.com/ | Network logs | -> Used for Autopilot provisioning. |
| Log line signature | [Setup] Error: Network initialization failed. | OOBE.log | -> Indicates network connectivity issue. |
Log Files to Check
C:\Windows\Panther\OOBE.logC:\Windows\Panther\SetupAPI.log
What This Error Actually Means
The error code
0x801C0101 is a hexadecimal representation of a Windows Autopilot provisioning failure. Breaking it down:
-
0x801C corresponds to the Windows Provisioning Agent (WPA) component, which manages device enrollment and OOBE (Out-of-Box Experience) workflows.
-
0x0101 maps to a specific failure in the network initialization phase. This error is raised when the device cannot establish a network connection during OOBE, typically due to missing drivers for the network interface card (NIC) or a failure to obtain an IP address via DHCP.
The error is logged by the
OOBE.log file and is directly tied to the
Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider event source. The root cause lies in the Windows Provisioning Agent’s inability to communicate with the
https://provisioningapi.microsoft.com/ endpoint, which is required to fetch device-specific enrollment profiles and configuration policies.
Affected Versions and Scope
This error is confirmed to affect **Windows 11 22H2** (build 22621.x) devices enrolled via Windows Autopilot. It is most commonly observed in scenarios where:
- The device’s NIC driver is not included in the Autopilot deployment profile.
- The DHCP server is misconfigured or unreachable during OOBE.
- Network policies (e.g., 802.1X authentication) block the device from obtaining an IP address.
Devices running **Windows 10 21H2 or later** may also encounter this error, but the scope is narrower. Older builds (e.g., Windows 10 1909) are unaffected due to differences in the Autopilot provisioning architecture. The issue is not observed in devices using **Windows 11 23H2** or newer builds, as Microsoft updated the WPA to include fallback mechanisms for driver discovery.
Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are located in the following paths:
-
C:\Windows\Panther\OOBE.log
-
C:\Windows\Panther\SetupAPI.log
-
C:\Windows\System32\winevt\Logs\Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider\Admin.evtx
In
OOBE.log, search for the exact line:
[Setup] Error: Network initialization failed.
In
SetupAPI.log, look for entries like:
Install of device instance '\?\PCI#VEN_10EC&DEV_8168&SUBSYS_145810EC&REV_03#3&11583659&0&1A' failed.
Event Viewer logs should be filtered for **Event ID 6006** (system shutdown) and **Event ID 6008** (unexpected shutdown) in the
System log. Additionally, check the
Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log for **Event ID 1002** (provisioning failure).
Root Causes
1. Missing NIC Driver in Autopilot Profile
This occurs when the device’s NIC driver is not included in the Autopilot deployment profile. In
SetupAPI.log, look for
Install of device instance ... failed entries. Verify the driver package in the Autopilot profile using:
Get-WindowsDriverOnline -Online -DriverPackagePath "C:\AutopilotDrivers"
2. DHCP Server Unavailability
If the DHCP server is unreachable, the device cannot obtain an IP address. Check the
OOBE.log for
Failed to obtain IP address entries. Use
Get-NetIPInterface to verify IP configuration during OOBE.
3. Network Policy Restrictions
802.1X or VLAN policies may block the device during OOBE. Look for
Authentication failed in
OOBE.log. Use
Get-NetConnectionProfile to inspect network profile settings.
Fix Procedure
- **Verify NIC Driver Inclusion**
- Mount the Autopilot deployment image and confirm the NIC driver is present in
C:\AutopilotDrivers.
- Use
Get-WindowsDriverOnline -Online -DriverPackagePath "C:\AutopilotDrivers" to validate driver compatibility.
- **Configure DHCP Fallback**
- Set a static IP for the NIC during OOBE using:
Set-NetIPInterface -InterfaceAlias "Ethernet" -Dhcp Disabled
Set-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.100 -PrefixLength 24
- **Update Autopilot Profile in Intune**
- Navigate to
Intune admin center > Devices > Windows > Autopilot > Devices.
- Assign the updated driver package via the
Device configuration > Profiles blade.
- **Registry Adjustment (Advanced)**
Editing the registry can break device enrollment. Always back up the registry before proceeding.
- Modify
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE and set DisableOOBE to 1 to bypass OOBE temporarily.
Error Code Variants
| Error Code |
Description |
Distinguishing Factor |
0x801C0101 |
Network initialization failed |
OOBE.log shows Network initialization failed |
0x801C0102 |
Failed to connect to provisioning endpoint |
Network stack is functional, but provisioningapi.microsoft.com is unreachable |
0x801C0103 |
Invalid device enrollment profile |
Device profile is missing or corrupted |
Verification
After applying fixes, verify success by:
- Checking
OOBE.log for the absence of
Network initialization failed entries.
- Using
Get-AutopilotDevice | Where-Object serialNumber -eq $serial to confirm the device is enrolled.
- Navigating to
Intune admin center > Devices > All devices and verifying the device status is
Compliant.
Prevention
To prevent recurrence:
1. **Deploy Driver Packages via Intune**
Use
Device configuration > Profiles > Create profile to assign NIC drivers to all Autopilot devices.
2. **Enforce DHCP Policies**
Configure
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Network/Dhcp to ensure DHCP is enabled.
3. **Monitor with PowerShell**
Run
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to proactively detect issues.
Use dsregcmd /status during OOBE to quickly verify device registration state without parsing logs.