If you’re new to Intune or an experienced user, encountering errors is part of the journey. In this guide, we’ll decode common Intune error codes, explain their meanings, and provide solutions to get you back on track.
Addressing MEM Sync-Related Errors
Error: The sync could not be initiated (0x80190190)
| Symptoms | Syncing policies from Intune’s settings results in a message indicating the failure. The event log displays the entry: “MDM Session: OMA-DM message failed to be sent. Result: (Bad request (400)).” |
| Resolution | The trust to the Intune backend has been compromised and can’t be rectified automatically. The solution lies in re-enrolling your device. Alternatively, you can run a script for cleanup and re-enrollment, although this isn’t officially supported. Another potential issue could stem from having two certificates on your device. Removing the incorrect one could alleviate the problem |
Error: Failed to get AAD Token for sync session User Token: (Unknown Win32 Error code: 0xcaa2000c)
| Symptoms | When syncing policies with Intune, a message stating “Sync wasn’t fully successful because we weren’t able to verify your credentials” appears |
| Resolution | This error occurs when a user logging in to the device has Multi-Factor Authentication (MFA) enabled. Azure AD’s security control demands authentication and proof of identity, leading to only the device portion being synced with Intune. |
Error: OMA-DM message failed to be sent. Result: (Unknown Win32 Error code: 0x801901ad)
Network connection issues are at the core of this error. Causes might include a lack of internet, proxy software restrictions, or driver problems. Remedies include authenticating your proxy software or updating the network driver.
Error: Preparing your device for mobile management (0x800705b4)
This error signifies a time-out during the process. Something halted the device from progressing to the next phase. Investigate the event log for error details and take corrective actions. This could be related to co-management configurations, requiring reevaluation.
Error: This device is already enrolled. You can contact your system administrator with the error code 8018000a.
This error implies that the device is already enrolled in Intune. This might result from provisioning errors during the process. To rectify this, delete the device’s serial number from endpoint.microsoft.com and remove the corresponding AAD object in portal.azure.com. After re-registering the device with the autopilot service, users can start anew, and autopilot should proceed as expected.
Error: This feature is not supported. Contact your system administrator with the error code 80180014.
This error points to device non-enrollment due to an unsupported platform or version. To troubleshoot, navigate through Intune’s Monitor > Autopilot deployments (preview) or scrutinize the event log on the failing device.
Error: LogonUser failed with error code: 1008
IntuneManagementExtention.log shows this code: AAD User check using device check in app has failed, with an accompanying System.ComponentModel.Win32Exception (0x80004005) error. This error occurs on properly enrolled devices, and there’s no need for action as no immediate fix is available.
Error: Expedite client missing
Expedited patches assigned via Microsoft Intune show no progress on assigned devices. The “Windows 10 and later Expedited updates” report indicates:
This error arises when a device hasn’t been online for an extended period. To address this, turn on the device to initiate sync with Windows Update. After sync, the patch will be applied per your configuration.