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?
28 Replies
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?
Same happening here, any device on this windows version has the same problem, other 25h2 versions through autopilot are fine, using the store app, don't suppose you have found a fix for it?
We're experiencing the same issue during Autopilot pre-provisioning starting on May 12th.
Company Portal - Microsoft Store app (new) - Install type System - Assignment Required (Device Group), Autopilot Device setup - Apps error code 0x87D1041C.
The temporary workaround that we've implemented is changing the ESP setting for "Allow users to use device if installation error occurs" to "Yes", and having our security software as the only app for "Block device use until required apps are installed if they are assigned to the user/device".
