Introduction
The error 0x87D1041C related to Company Portal application installation during the Autopilot enrollment process has recently caused issues, particularly after the May Windows update. This article examines the causes, identifies changes in system context operation, and explores how a suspended flight modification enabled installation recovery.
Good to know
Autopilot enrollment is designed to pre-configure devices before deployment to users, which includes installation of necessary applications.
Origin of Error 0x87D1041C
The error 0x87D1041C indicates that Intune was unable to detect the application after its installation, even though the installation appeared to complete successfully. This issue manifested after the May Windows update, while the Company Portal installation configuration had not changed.
Impact of Changes in Windows Apps
Technical Context of Store Installation
Installing an application from the Microsoft Store involves several steps:
- Retrieving the package from the Store.
- Staging content on the device in C:\Program Files\WindowsApps.
- Registering the package in the system or user context.
This process is orchestrated by several essential Windows components:
- InstallService.dll: Responsible for the installation workflow from the Store.
- AppXDeploymentClient.dll: Enables operations on AppX and MSIX packages.
- AppXDeploymentServer.dll: Manages deployment and package state.
Why Does the Error Persist?
Although the package is correctly stored in WindowsApps, the final registration process was not being completed. This led Intune to report the application as missing, resulting in error 0x87D1041C.
![ FixInstallUnderSystemContext. This modification introduces installation logic that redirects system-dependent operations toward the user context.
[IMAGE:5:https://patchmypc.com/app/uploads/2026/06/image-4.jpg](https://patchmypc.com/app/uploads/2026/06/image.jpg]
Caution
User context installation works as expected after sign-in, but prevents detection during Autopilot pre-provisioning.
Analysis of May Update and FixInstallUnderSystemContext
Discovery of Modified Behavior
When examining the changes in InstallService.dll after the May update, a new function was identified.
Detailed Operation
When the FixInstallUnderSystemContext function is active, Windows searches for users logged into the device and attempts to finalize installation for them via UWAInstallWork::_DoInstallForAllLoggedOnUsers.
This causes problems during Autopilot pre-provisioning, where no user is yet logged in. As a result, the installation is reported as complete, but Intune cannot detect the application.
![ "1"**.
[IMAGE:12:https://patchmypc.com/app/uploads/2026/06/image-4.png:fix install under system context flight active](https://patchmypc.com/app/uploads/2026/06/image-2.png]
Feature Flight Activation
An examination of the sccinstallservice.json configuration file revealed that this new feature was enabled by default with "FIXINSTALLUNDERSYSTEMCONTEXT".
Tip
To verify the state of this configuration, use tools like PowerShell with JSON file analysis on the system.
Recovery Through Feature Deactivation
Communication with Microsoft
After analyzing the situation, details of the findings were shared with Microsoft. A suspended flight of the FixInstallUnderSystemContext feature was subsequently applied via modification of the configuration JSON file.
Results Obtained
After disabling the function in InstallService.dll, Company Portal installation in system context successfully resumed during Autopilot pre-provisioning, as expected.
Conclusion
The FixInstallUnderSystemContext feature aimed to improve installation flows for users, but its behavior is incompatible with Autopilot pre-provisioning. This situation highlights the importance of thorough testing before deploying modifications to critical components.
Important
Administrators should monitor Windows updates and their impacts on Intune and Autopilot flows, and perform laboratory testing before any deployment.
