Forum Discussion
Company Portal No Longer Installing During Autopilot Enrollment
Up until today, Autopilot enrollment which included Company Portal from the Microsoft Store (NEW) was successful. Starting today, the same enrollment workflow with similar hardware is failing to install Company Portal, reporting an error code of 0x87D1041C ("The application was not detected after installation completed successfully"). The only difference between yesterday and today? Today's enrollment including updating Windows to10.0.26200.8457 (today's Patch Tuesday update).
I did find information that there was a similar issue nearly a year ago, where the latest Windows Update resulted in the same errors, and Company Portal requiring an update to fix. Are we looking at the same issue again?
23 Replies
Not able to reproduce this issue....tried many AP pre-pro + win 11 12/05 + CP on system assigned to AP group. each time it succeed 🤯. even I tried ESP WU enabled. tried after a wipe as well after new iso with media creation tool. There should be another point in common.
Our Model is a Dell Pro 14 Premium PA14250
Do you mean this issue only occurs on a specific hardware? Especially Dell?
Or specific pre-installed image from Dell maybe?
The may update broke something with pre provisioning for sure, if I make a second company portal and scope it to all users in the user (not system) install behavior, it installs during account phase of autopilot.
For now I'll do all users + user install behavior
Just wondering but is this still happening? AKA can you test again after reading this?
Still happens for me. July 1 2026 with company portal in system context scoped to my device. Windows build 26200.8457. Failed to install during autopilot.
Still broken as of May 21 2026. I had to manually download company portal and its dependences with winget and package to intune.
The microsoft store version of intune is still throwing the 0x87D1041C error on devices with the latest update build of 26200.8457 (May 2026)
This is definitely only an issue if the laptop has 26200.8457 as our other laptops with 26100.8457 does not have the issue.
Just wondering but is this still happening? AKA can you test again after reading this?
Same problem here aswell. Anyone found any fix or info from Microsoft?
Did anyone get a fix for this? Instead of just removing it as a blocking app or tricking the registry?
Logged a support case with Microsoft, they have confirmed the issue with the May update and are waiting for a fix. Their only recommendation is to remove from blocking in ESP for now.
We are also seeing similar Autopilot failures within our environment that appear to correlate with Company Portal being configured as a required app during ESP (Enrollment Status Page). In our configuration, we currently have the setting “Allow users to use device if installation error occurs” set to “No,” which is causing the provisioning process to fail when Company Portal does not install successfully.
Based on recent observations, this behavior aligns with what others are reporting, where failures in required app installation during ESP are preventing device provisioning from completing.
Same issue for us, whole pre-provisioning process is failing since we have company postal (system) as required in ESP.
Do you have any news about that issue? I've reported that to MS but no answer for now
So far its only happening on 26200.8457 and a Dell Pro 14 Premium.
Seeing the same thing. After installing the latest windows update from Tuesday it's been failing for us.
error: "The application was not detected after installation completed successfully (0x87D1041C)"
So it does install but isn't meeting some detection rule built into the company portal app from the MS store. Like the previous user we took it out of the blocking apps in ESP since it does install. This way our autopilot doesn't fail.Just wondering but is this still happening? AKA can you test again after reading this?
We're experiencing the same issue during Autopilot pre-provisioning today.
Our work around was the following: -
Opening Registry: -
Go to - Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > Autopilot > EnrollmentStatusTracking > Device > Setup > Apps > Tracking > Sidecar > Win32App_*
Find the app listed in their Updated the InstallationState from 4 to 3 and deleted the ErrorHresult Key.
Then went to -
Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Provisioning > AutopilotSettings
And deleted the key -
DeviceSetupCategory.Status
Then clicked re-try and it then allowed us to progress further.
And any where CP was missing it re-tried most cases the app was their though.
Same Issues during Pre-Prov / Autopilot, The application was not detected after installation completed successfully (0x87D1041C), otherwise the usual deployment looks ok, Company Portal was added as a blocking app in ESP and its breaking the Pre-provisioning now ( Since 13/05)
Just wondering but is this still happening? AKA can you test again after reading this?
