Intune error codes and solutions

Intune error codes and solutions

Are you managing Intune? Maybe you just started, or maybe you have been working with the product for a long time. Nevertheless, we all see stuff where we need to be able to find out what to do with it. In this blog post I will help you out with your error codes, what they mean and how to resolve them.

During the post there will be links to many external contributors, so please give them a huge kudos, for their extensive work.

Welcome!

—————————————————————————————————————————————————————–

MEM Sync related errors

The sync could not be initiated (0x80190190)

Operating system
Windows 10 and later

Symptoms:
When attempting to sync policies with Intune from settings it says:

Eventlog says: MDM Session: OMA-DM message failed to be sent. Result: (Bad request (400).).

What happened and how to solve it?
Trust to the Intune backend has been lost and cannot be remediated automatically. Re-enroll your device to solve this issue.

You can run this script to clean up and re-enroll (Be aware that this is not supported and will be on your own risk)

It could also be that your device has 2 certificates where you need to clean out the wrong one. See more here

—————————————————————————————————————————————————————–

Windows Autopilot related errors

Preparing your device for mobile management (0x800705b4)

Operating system
Windows 10 and later

Symptoms:
During autopilot the 1st of 3 phases, Device preparation, fails to finish:

What happened and how to solve it?
This error means “Time-out” and it was not able to get further in the process. Something stopped the device from proceeding to the next phase.

Press SHIFT+F10 to look up the error.
Navigate to the eventlog and this case it says (Unknown Win32 Error code: 0x82aa0002) which indicated that it is related to co-management. Someone setup a configuration for the device to install the Configuration Manager agent during autopilot.

We also see an error (Unknown Win32 Error code: 0x86000022) which is related to configuration manager “The specified node doesn’t exist.”

Check your CMG works and try again or remove the co-management profile assignment and try again, you will see it go through its stages like it should.

There could be many other problems when you see this issue.
See more here
And also here

—————————————————————————————————————————————————————–

This device is already enrolled. You can contact your system administrator with the error code 8018000a.

Operating system
Windows 10 and later

Symptoms:
During autopilot the device fail right after providing credentials:

What happened and how to solve it?
This error means the device already enrolled to Intune. This could be due to error while provisioning the device, but it actually went through some of the process.

In such scenario a device would typically be stuck.

1. Go to endpoint.microsoft.com and delete the serial number of the device
2. Go to portal.azure.com and remove the AAD object corresponding to the Autopilot registration.
3. re-register the device to the autopilot service.

Your user can start over and enter their credentials into the device and Autopilot will proceed as expected.

—————————————————————————————————————————————————————–

This feature is not supported. Contact your system administrator with the error code 80180014.

Operating system
Windows 10 and later

Symptoms:
You are at the OOBE page and want to logon to your device. You think it should go through autopilot, but it fails.

What happened and how to solve it?
This error means the device cannot enroll as the platform or version is not supported.
Here are two ways how to find out what happens:

1. To find out what happens in Intune go to Endpoint -> Devices -> Monitor -> Autopilot deployments (preview)
2. Go to the event log on the failing device. Shift + F10 -> eventvwr.msc -> Applications and Services Logs -> Microsoft -> Windows -> DeviceManagement-Enterprise-Diagnostics-Provider -> Admin

To solve it, register your device to Autopilot as in this case, the device is considered as a “Personal” device, and device restrictions in this environment does not allow “Personal” devices to be enrolled.

—————————————————————————————————————————————————————–

Configuration Profiles related errors

(./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version), Result: (The system cannot find the file specified.).

Operating system
Windows 10 and later

Symptoms:
When looking at the eventlog DeviceManagement-Enterprise-Diagnostics-Provider it says:

What happened and how to solve it?
Nothing to do. It is normal behavior of any Intune managed devices.

The “FakePolicy” is created to detect if a certain patch is present on Windows, and will be removed automatically once machines are ready to consume the new ADMX versioning feature.
Reddit has an article on it here

—————————————————————————————————————————————————————–

Application related errors

LogonUser failed with error code : 1008

Operating system
Windows 10 and later

Symptoms:
You look into the IntuneManagementExtention.log and a code: AAD User check using device check in app is failed, now fallback to the Graph audience. ex = System.ComponentModel.Win32Exception (0x80004005): An attempt was made to reference a token that does not exist.

What happened and how to solve it?
This error occur on perfectly fine enrolled devices, and you should not put any effort in to fix this as there are no fix disposal. If I find a reason or get more information from Microsoft, I will propose a solution here.

Table of Contents

Share this post
Search blog posts
Authors
Modern Workplace consultant and a Microsoft MVP in Enterprise Mobility.
Modern Workplace consultant and a Microsoft MVP in Windows and Devices for IT.

Infrastructure architect with focus on Modern Workplace and Microsoft 365 security.

Passionate IT professional with 20+ experience in IT architecture, consulting, and design. 

Cloud & security specialist with focus on Microsoft backend products and cloud technologies.

Infrastructure architect with focus on design, implementation, migration and consolidation.

Infrastructure consultant with focus on cloud solutions in Office365 and Azure.

follow us in feedly
Categories

Follow on SoMe