Forum Discussion
Solved
Autopilot Error (0x81036502) - Endpoint Manager
Dear community members,
I am facing an issue with my Endpoint Manager's autopilot feature. It suddenly stopped working and I am receiving error code 0x81036502. I would greatly appreciate any help or advice on how to resolve this issue.
According to my research, this error is related to either a timeout issue or with the Windows 10 version 22h2. I am running Windows 10 version 22h2 on my endpoint. I have tried several troubleshooting steps but to no avail.
If anyone has any information or suggestions, please share them with me.
Thank you for your time and assistance.
Best regards,
Rashad Bakirov
- https://call4cloud.nl/?s=0x81036502 😛
just use my blog as your own personal google search....
Lets start by looking at which apps you configured as required apps during the esp
If you know the apps... use mn his get-autopilotdiagnostics tool to determine which app has a wrong install status ... or by looking at the registry
https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/understand-troubleshoot-esp
I guess with a little bit of searching you will find the culprit
- Getting the same with Windows 10 22H2 here.
rashadbakirov We are experiencing this issue with a single machine. We are noticing all required and non-required apps fail to install during ESP with error code 0x800711C7, which according to some posts online like this one the error code means "HRESULT_FROM_WIN32(ERROR_SYSTEM_INTEGRITY_POLICY_VIOLATION), "Your organization used Device Guard to block this app. Contact your support person for more info."", which apparently presents itself when running Windows in S-Mode, but this is not the case here, the machine is freshly installed from Microsoft with the latest version of Windows 10 22H2.
We are now going to try with older versions of Windows 10 like 21H2, I'll update this post if it works.
- Did you find the root cause of your failure? Did older version of Windows 10 work? Thanks
Hello world
I may have worked out how to find and resolve this.
When the device throws up the error, press Shift + F10 to open a cmd prompt. Open regedit.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking\Device\Setup\Apps\Tracking\Sidecar
Here you'll see all win32 apps being deployed. We only deploy win32 apps but you may have some other registry locations with apps in. You'll find them in this general area anyway.
Look for a registry value of 4. This app has failed installation is likely what caused the issue. Make a note of the app ID string.
Use the app ID string to go to the app in Intune
I had to actually go in to the app, and visually find the app id, pasting it didn't work. I might have had an incorrect URL.
Anyway, that's how you find the app causing issues. Exclude it and you'll find ESP works fine.
Regards,
Stefan- We encountered this issue today and we followed these instructions. We changed the value from the failed Reg key from 4 to 3 and that seemd to solve the issue for us.
- I identified the failed application and by simply deleting it from the ESP, the computer installation continued without problems.
I have to check why it failed, because when I finished the computer installation, I noticed that the application had been installed without problems, maybe it is something in the recognition method.
Anyway, thank you very much for your input, it has been a great help.I think this is a way too but it seems like I can't login after I deleted the records failed in ESP .
This helped me alot and saved me tons of time, thank you!
As of today 5/24/2023 the internal Intune "Microsoft 365 Apps for Windows 10 and later" install only sporadically, 4 out of 5 deployments fail, and 1 succeeds with 100% identical hardware and configuration. I had to remove the apps from the group in order to permit ESP to complete successfully. If this is not some royal Intune MEM screw up I don't know what is:
rashadbakirov The solution and suggestion described herein is a fallacy, respectfully to the previous posters this issue is much bigger than what it appears and has nothing to do with a "smoking gun" bad app error which was the case in this specific instance and that further diluted the true problem identification.
This error is 22H2 error and was introduced into 22H2, same exact profiles and Auto Pilot setup does NOT trigger the same error, as long as Windows 10 version is less than 22H2 - for example 20H2 works just fine.
So, does anyone know what's going on with 22H2
Thanks
Boyan
- That error the op mentioned it a time out error… that could occur because alot of reasons.. but when the esp is failing it apps, its because of an app failing…
- @Rudy Respectfully if it was time out why does it NOT occur with 20H2 but only with 22H2?
- https://call4cloud.nl/?s=0x81036502 😛
just use my blog as your own personal google search....
Lets start by looking at which apps you configured as required apps during the esp
If you know the apps... use mn his get-autopilotdiagnostics tool to determine which app has a wrong install status ... or by looking at the registry
https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/understand-troubleshoot-esp
I guess with a little bit of searching you will find the culprit- Solved. Hi, thank you very much for your answer.
We have many apps configured as required apps on ESP, and a few days before one of these apps was updated by software teams, and the new version has an installation error, which we missed.Hi - i am having the same issue, please advise me which apps were updated thanksrashadbakirov
