Microsoft Store app Intune error code Unknown (0x00000000)

I got this issue while deploying the Company Portal application on Intune-managed Windows 10 and Windows 11 devices. The application deployment was only partially successful, and on some target devices, the Company Portal application failed to install.

Users also received a toast notification in the System tray and reported that they were getting an error as shown in the below screenshot. The error message says Company Portal Installation failed.

Company portal Installation failed
Company portal Installation failed

The Company Portal application was deployed to the target devices using the Microsoft Store app (new) deployment method. This approach allows for the deployment of both UWP and Win32 apps directly through the Intune admin center.

The same error message can occur when deploying other applications using the Microsoft Store app (new) method. You can reference this blog post, which will assist you in identifying and resolving the issue for a successful deployment.

Locating Unknown (0x00000000) Error in Intune Admin Center

To locate this error code on Intune admin center, follow below steps:

  • Login on Microsoft Intune admin center
  • Click on Apps and then click on All Apps
  • Click on the app deployment for example: Company Portal
  • Click on Device install status or User install status under Monitor
Click on the application which is having issues. For example: Company Portal
Click on the application which is having issues. For example: Company Portal
  • On the right-hand side, you can view the app’s status. In the screenshot below, you can see that the Status is marked as “Failed” with Status Details displaying the error code “Unknown (0x00000000)
Unknown (0x00000000) error code on intune admin center
Unknown (0x00000000) error code

Fix Unknown (0x00000000) Error code

No additional information is provided in the Intune admin center, other than the error code “Unknown (0x00000000)” Consequently, remote troubleshooting becomes quite challenging. To address this, we must establish a connection with one of the target devices on which this deployment failed.

1. Copy Intune Application Identifier (App Id)

  • Login on Microsoft Intune admin center
  • Click on Apps and then click on All Apps
  • Click on the app deployment for example: Company Portal
  • Using the web browser address bar, find and Copy the app ID in the URL (As shown in below screenshot)
Copy Intune Application Identifier (App Id)
Copy Intune Application Identifier (App Id)

2. Analyze Logs in IntuneManagementExtension.log file

To troubleshoot this error, Analyze logs related to the app deployment. Intune App deployment logs are saved in a file called IntuneManagementExtension.log file, located at C:\ProgramData\Microsoft\IntuneManagementExtension\Logs.

  • Search for the App Id which we have copied in the previous step in the IntuneManagementExtension.log File to Find Deployment Logs and Errors.
  • After a few searches within the log file for the app ID, I eventually located the error message. The screenshot below illustrates that the error message is related to the Microsoft Store Install service“.
  • The installer exception message indicates that a service is either disabled or unable to start. Although it doesn’t specify the service’s name, given that we are deploying a Microsoft Store app, it’s clear that the issue is related to the Microsoft Store Install service.
  • I checked the target device and discovered that the service was indeed in a disabled state. I altered the service status from ‘disabled‘ to ‘manual‘ and waited for the Intune device to check-in, triggering a redeployment of the application on the device.

The solution to this error message is also detailed in another one of my blog posts, where I discuss the Microsoft Store error code 0x00000000 in great detail. You can find the fix there: How to Fix Microsoft Store Error Code 0x00000000.

Note

[Win32App][WinGetApp][WinGetAppExecutionExecutor] Completed execution for app with id: e0f0ef08-5e9e-4a9f-bd05-da79da1e61eb.
WinGet operation result:
Operation result = InstallError
Installed version =
Reboot required = False
Installer Error code = 0
Installer extended error code = -2147023838
Installer exception message = The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
Execution result:
Action status: Failed
Enforcement state: Error
Reboot status: Clean
Error code: 0

Analyze Logs in IntuneManagementExtension.log file
Analyze Logs in IntuneManagementExtension.log file

3. Enable Microsoft Store Install service on the target device

Next, log in to the target device using administrator credentials and follow the steps below to enable the Microsoft Store Install service.

  • Press Win + R keys to open the Run dialog box
  • Type services.msc to press Enter.
  • Find Microsoft store Install service and check its Status
  • If the Status is disabled, change it to Manual
Microsoft store Install service disabled
Microsoft Store Install service in disabled state
  • Double-click on Microsoft Store Install Service and change its Startup type to Manual. Click on OK to save changes.
Update Microsoft Store Install Service to Manual
Update Microsoft Store Install Service to Manual

4. Wait for the next Device check-in

In the next device check-in, the application deployment will be re-tried by the Intune management extension. Please note that it may take some time for this process to begin. To expedite the download and installation, you can manually trigger an Intune refresh cycle on the device. This can also be achieved using PowerShell.

You can also initiate the device check-in process by simply restarting the device. Performing a manual sync on the user’s devices is not mandatory since the device check-in process occurs automatically.

Conclusion

In this blog post, we explored how to resolve the Unknown (0x00000000) error code when deploying Microsoft Store apps via the Intune admin center. This error is quite vague and doesn’t offer detailed information about the underlying problem.

To address this, we looked into the IntuneManagementExtension.log file, where you might encounter different error messages than the one discussed here. Nevertheless, the troubleshooting method outlined in this blog post should help you identify the issue’s root cause and implement a solution.

Leave a Comment