Original publish date: March 27, 2025
KB ID: 5057606
Support for Windows 10 will end in October 2025
After October 14, 2025, Microsoft will no longer provide free software updates from Windows Update, technical assistance, or security fixes for Windows 10. Your PC will still work, but we recommend moving to Windows 11.
Summary
After you install a Windows update released on or after November 15, 2022, you might receive error messages when you provision and install an app to a device enrolled with a third-party MDM service. Intune managed devices are not impacted.
For example, when you provision an enterprise app by using the EnterpriseModernAppManagement configuration service provider (CSP), enrolled devices may not successfully install the app.
Additionally, errors might be reported in the following locations:
MDM Console
Error 0x80190193: Opening the package from location <GUID>?appKind=ModernEnterprise failed.
MDMDiagHtmlReport.html log file
Modern App(<app-name>) Failed -2147009296
Error: -2147009296 = ERROR_INSTALL_OPEN_PACKAGE_FAILED - Package could not be opened.
Windows Event log file: microsoft-windows-appxdeploymentserver-operational.evtx
Information 603 Microsoft-Windows-AppXDeployment-Server Started deployment Add operation on a package with main parameter <GUID>?appKind=ModernEnterprise and Options BackgroundTaskOption and SkipDeploymentOperationRpcCallerIsAdminCheck. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
Error 465 Microsoft-Windows-AppXDeployment-Server error 0x80190193: Opening the package from location <GUID>?appKind=ModernEnterprise failed.
Error 497 Microsoft-Windows-AppXDeployment-Server Error 0x80070002: Opening the Msixvc package from location <GUID>?appKind=ModernEnterprise failed. Please check whether the Msixvc support services are installed.
Error 403 Microsoft-Windows-AppXDeployment-Server error 0x80190193: Failure to get staging session for: [https://%3cMDM-server%3e/WindowsApplicationProvider.svc/Application/%3cGUID%3e?appKind=ModernEnterprise][https://%3cMDM-server%3e/WindowsApplicationProvider.svc/Application/%3cGUID%3e?appKind=ModernEnterprise]https://<MDM-server>/WindowsApplicationProvider.svc/Application/<GUID>?appKind=ModernEnterprise.
Error 404 Microsoft-Windows-AppXDeployment-Server AppX Deployment operation failed for package with error 0x80073CF0. The specific error text for this failure is: error 0x80190193: Opening the package from location <GUID>?appKind=ModernEnterprise failed.
What changed?
Starting with the Windows update released on November 15, 2022 (KB5020030), changes were introduced that altered the mobile device management (MDM) client response payload.
When you use the EnterpriseModernAppManagement configuration service provider (CSP), the MDM service must deploy the following registry change to enrolled devices before deploying any applications.
This registry change adds the MDM service fully qualified domain name to the Data for the MdmHosts value in the Appx subkey:
Registry location: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Appx
Value name: MdmHosts
Value data: ^(?:[^\/]*)((\.MANAGE[^\.]*\.(MICROSOFT\.(COM|US)|MICROSOFTONLINE\.CN)$)|(MDMSERVICE\.CORP\.CONTOSO\.COM)$)
Notes
-
You must add the fully qualified domain name of the MDM service to the end of the “Value data” for MdmHosts. In this example, we added (MDMSERVICE\.CORP\.CONTOSO\.COM)$).
-
The MDM service fully qualified domain name may be different in your environment.
-
The “Value data” must be in ALL CAPS.
References
EnterpriseModernAppManagement configuration service provider (CSP)
