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 hel...
- 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
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 .
nmartinez1205 removing the application from the ESP does not prevent it from being installed, it will still install in its own good time after the ESP finishes. The ESP only tracks the installs of the applications specified in the ESP, and will not release the ESP until they are installed. I believe it prioritizes these app installs, but it does not force them to be installed first. This has been an issue with Intune apps and continues to be as there is no way to control the install order. Say, for example you have two apps specified in your ESP, and 10 other required apps. It is possible that these 10 apps could install prior to the 2 you specified, and the time this takes could cause the ESP to time out. However, the application will still install in the background, regardless of the ESP failure or not (providing the installation is working fine), which makes troubleshooting difficult. Another scenario is that an application may fail to install because it has a dependency on another application and cannot install successfully until that application is installed. A third scenario is when an application install fails and puts a prompt or information screen up, which is hidden by the ESP. The user never sees it, and so cannot hit continue or ok or whatever the prompt is waiting for and the ESP stalls and eventually times out. generally these are the best issues as they may prevent the other applications from installing until the button is pressed and the process ends, permitting the next application to start.
Yet another scenario is where you have multiple application deployment mechanisms, like ConfigMgr and Intune, if both try to deploy an application at the same time, one will win, the other will fail due to another install taking place. This can happen with MSI apps or when mixing MSI (lob) and Win32 as the Win32 could have an embedded MSI.
In my personal opinion the Autopilot process is not Enterprise-ready and has so many issues. Don't get me started with Co-Management in Autopilot, that is a whole other can of worms.
- I totally agree with you. With the experience we are having with autopilot, we have detected many failures, most of them we have been able to solve, others, do not adapt to our way of working with the workstations, but, maybe I expressed myself wrong, I decided to remove it from the ESP, while validating why it was not installing or failing that application, since I had many workstations, which were not being configured satisfactorily.
As a workaround, by removing it from the ESP, what I achieved, is that the AP process continues its course so that the workstation is finished configuring satisfactorily.
I did some research, and the failure was because the detection method of the application was wrong, so after fixing it, I was able to assign it back to the 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:
- I've been fighting with this myself for 2 days.......I thought it was me.
I tried it today when I encountered the error and it was Dell Command Update, this time I was installing using a winget script whereas before I packaged the universal app installer. Great find so thanks for sharing, to other Dell users, it looks like we need to install after ESP.
In MEM the error is "The application was not detected after installation completed successfully (0x87D1041C)" so I am going to check my detection script.
JaggerSystems_com
Shift-F10 does not work for me at this point.Additionally, when I click "Collect Logs", it opens a dialog to choose a destination for the log files and then... nothing.
This is using the bog standard Windows 10 ISO available from Microsoft.- Good spot, will try that if I encounter the issue again. Thanks for sharing
