Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | ERROR_SERVICE_DISABLED (0x80070422) | C:\Windows\Logs\MoSetup\BlueBox.log, C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log | -> wuauserv service |
| Affected build range | Windows 11 23H2 | | |
| Registry key involved | HKLM:\SYSTEM\CurrentControlSet\Services\wuauserv | Registry Editor | -> Start value |
| Relevant service/endpoint URL | https://manage.microsoft.com/ | | -> Intune admin center |
| Log line signature | 0x80070422 or 'ERROR_SERVICE_DISABLED' | C:\Windows\Logs\MoSetup\BlueBox.log, C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log | |
Log Files to Check
C:\Windows\Logs\MoSetup\BlueBox.logC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
What This Error Actually Means
The error code 0x80070422, also known as ERROR_SERVICE_DISABLED, is raised during the Windows Autopilot enrollment process when a critical service required for this operation is disabled on the device. Specifically, this error occurs if either the
wuauserv (Windows Update) or
msiserver (Windows Installer) services are not running due to being set to Disabled in the Windows Services management console or via Group Policy settings. This blocks the necessary communication between the device and Microsoft's provisioning servers, leading to a failure in Intune enrollment and policy application.
Affected Versions and Scope
This error is specific to devices running
Windows 11 23H2. It impacts Autopilot enrollment for both pre-provisioned and self-deploying devices. Devices enrolled via other methods, such as traditional manual or Intune-assisted enrollment, are not affected by this issue unless they also have the same service configuration problem.
Where To Look First: Logs and Event IDs
To diagnose an error 0x80070422, you should first review the following logs for relevant entries:
C:\Windows\Logs\MoSetup\BlueBox.log
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
Search these files for occurrences of
0x80070422 or the literal string
"ERROR_SERVICE_DISABLED". Additionally, check the Event Viewer logs under
Applications and Services Logs > Microsoft > Windows > Provisioning-Diagnostics-Provider, looking specifically for events with IDs 69 (Autopilot policy failed) and 107 (Autopilot diagnostics: service state error).
Root Causes
Group Policy Object Setting the Service to Disabled
This can happen if a stale Active Directory computer account has a Group Policy Object (GPO) that sets
wuauserv or related services to disabled. To identify this cause, check the registry key
HKLM:\SYSTEM\CurrentControlSet\Services\wuauserv for its Start value. A value of 4 indicates the service is Disabled.
CIS Benchmark Rule Incompatibility with Autopilot
Organizations implementing hardening baselines based on the CIS Benchmark might inadvertently apply rules that disable
wuauserv. Review your organization's baseline policies to ensure they do not set Windows Update Service to disabled for devices undergoing Autopilot provisioning.
Custom Base Image Optimization
Some organizations create custom base images with services disabled for performance optimization. This can lead to the same error during Autopilot enrollment if these services are critical for the process.
Fix Procedure
- Check Windows Update Service Start Type: Use PowerShell to verify the current state of
wuauserv. Run Get-Service -Name wuauserv | Select-Object Name,Status,StartType.
- Inspect Registry Settings: Confirm that the registry key
HKLM:\SYSTEM\CurrentControlSet\Services\wuauserv is not set to disable the service. Use PowerShell: Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\wuauserv | Select-Object Start.
- Review Windows Update Policy: Check for any registry policies that might block connectivity required by Autopilot. Run
Get-ItemProperty HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate | Select-Object DoNotConnectToWindowsUpdateInternetLocations,DisableWindowsUpdateAccess.
- Analyze Autopilot Event Log: Use PowerShell to get recent events from the provisioning diagnostics log:
Get-WinEvent -LogName 'Microsoft-Windows-Provisioning-Diagnostics-Provider/AutoPilot' -MaxEvents 30 | Select-Object TimeCreated,Id,Message.
- Check Intune MDM Enrollment Status: Ensure the device is AzureAdJoined and MdmEnrolled. Run
dsregcmd /status. If both are NO, the Autopilot registration failed before service checks.
Enable Windows Update Service:
Before re-running Autopilot, enable the necessary services on the device: Set-Service -Name wuauserv -StartupType Automatic; Start-Service wuauserv. Also ensure related services are enabled: bits, cryptsvc, and msiserver.
- Direct Registry Fix: If GPO keeps reverting, directly set the registry value to enable the service:
Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\wuauserv -Name Start -Value 2.
Re-trigger Autopilot:
In Intune admin center, reset the device for re-enrollment. Navigate to Devices > All devices > [device] > Wipe (with Retain enrollment state and user account = No). This will restart the OOBE process.
Error Code Variants
| Error Code | Description |
| 0x80070436 | ERROR_SERVICE_NOT_ACTIVE (Service is not active) |
| 0x80072F05 | ERROR_NO_SUCH_SITE (No such site exists) |
| 0x8007139F | ERROR_SERVICE_DOES_NOT_EXIST (Service does not exist as an installed service) |
Verification
To verify the fix, check that
wuauserv is running during the OOBE phase by using PowerShell:
Get-Service wuauserv. Additionally, confirm successful re-enrollment via Intune by checking the device status with
dsregcmd /status, ensuring both AzureAdJoined and MdmEnrolled are set to YES.
Prevention
To prevent recurrence of this issue, ensure that no Device Configuration profiles in your organization's Intune setup apply settings that disable Windows Update on Autopilot devices before enrollment completes. Navigate to
Intune admin center > Endpoint security > Windows Update > Update rings, and verify the Automatic update behavior is not set to 'Turn off auto updates'. Additionally, review any custom baseline hardening rules for compatibility with Autopilot requirements.
Incorporating these preventive measures into your organization's standard operating procedures will help maintain a smooth enrollment process for all devices undergoing Windows Autopilot provisioning.