Troubleshooting the Microsoft Store and Microsoft Intune integration
Published Feb 23 2023 08:00 AM 33.7K Views

We recently released a new Microsoft Store app experience in Microsoft Intune, allowing admins to search, browse, and deploy apps from a single location. This feature allows access to most Store apps within Intune, simplifying deployment to device groups and allowing admins the ability to keep apps automatically up-to-date and remove unwanted, built-in apps from devices. However, there are known issues when creating and accessing apps through the Store app in Intune and we wanted to provide some general recommendations and troubleshooting guidance when using this feature.


Understanding app creation issues

The following sections explain scenarios where creating and searching for apps through the Microsoft Store app in Intune may not work as expected.


The desired app is available in the Microsoft Store but is not appearing in the search results

Specific Microsoft Store apps may not be displayed or available in Intune. Common reasons this may occur includes when the app is:

  • Not available in your region.
  • Only available for ages 12 and above.
  • A paid app, which is not supported.
  • An Android app. Accessing Android applications requires additional steps and apps. To learn more, see Windows Subsystem for Android.
  • A Microsoft Store for Business app that is not available publicly in the consumer store.
  • Not available for download and management through Intune.
  • Applications marked as non-searchable in the store. Searching by application name in the store or Intune will not show, but searching by ID will.
  • Multi-word search is quoted whole word search logic, use either a single word or exact match to the name in the Store (no skipping words or partial words).


Win32 app shows not supported

After selecting a Win32 app from the search results, you may see a banner that states “This app is not supported in preview,” and you’re unable to proceed. There are some Win32 apps that either we don’t have enough information on or that have unreliable detection, installation, or upgradability and are, therefore, filtered out as they may not successfully be managed.


A screenshot of the Add App screen showing that the desired app is not supported in the Microsoft Store app.A screenshot of the Add App screen showing that the desired app is not supported in the Microsoft Store app.


Common scenarios include installers that add multiple entries into add/remove programs during their installations or apps with ARM64 installers. Check the application’s page in the Microsoft Store and confirm what installers are used. ARM64, for example, is listed under the system requirements architecture details.


A created application is stuck in processing

If you create an application and then experience a banner that indicates that the app is still processing (and it remains in this state), you will be unable to assign the app. This is typically caused by an issue when Intune attempted to validate the app and can be resolved by re-creating the app. However, if you’re creating the apps by using the Microsoft Graph API and run into this, it’s likely due to a misconfiguration such as a mismatch in the resource type.


Search error messaging

When performing a search with the Microsoft Store app in Intune, or selecting the desired application from the search results, an error dialog may appear with “An error occurred when searching for apps” or “Error getting app manifest” message.


This means that the query was unable to retrieve information from the Store endpoint ( Confirm that you’re using the Store endpoint, that it’s not blocked by firewall rules (as access to this endpoint is required) and try again. If you need additional troubleshooting assistance for this scenario, please open a support case and provide a network trace of the failure.


Troubleshooting app downloading issues

If you’re experiencing issues when downloading the Microsoft Store apps, it’s helpful to understand the installer type of the application package as they work differently and may have their own limitations. There are two installer types:

  • UWP (Universal Windows Platform) apps, which includes .appx/.appxbundle/.msix installers
  • Win32 apps, which includes .exe/.msi installers


You can determine the type by viewing the app Properties > Installer type in the Endpoint Manager admin center. Note that Intune Win32 type apps in Intune (shown as Windows app (Win32)) are not the same as Win32 type Store apps (shown as Microsoft Store app (new)).


Store apps of UWP installer type

Store UWP installers are downloaded and installed using the Microsoft Store. The content should come from a Microsoft content delivery network (CDN). These are partial downloads (byte range requests) based on what is needed for a specific device.


If you want to use Delivery Optimization, it must already be configured on the device. Delivery Optimization is used to perform the download, with Delivery Optimization peering enabled for this type only.


Store apps of Win32 installer type

Store Win32 installers are downloaded by the Windows Package Manager (WPM) from third party download locations determined by the app publisher. See the WPM logs for detailed download progress and the URL used for download.


Common issues:

  • Inaccessibility to the download location (Note, you can use WPM logs to see the exact URL location or by running “Winget show [packageid]” and looking at the Installer > Installer URL property).
  • Hash-mismatch: The file at the endpoint doesn’t match as expected. Downloads are temporarily redirected to a Microsoft CDN with a cache of the installer file until the new installer version can be processed. Access to the Microsoft CDN is needed.
  • Download location reliability: the endpoint may not handle large scale downloads well, especially in a short period of time, or may have other outage issues.
  • Delivery Optimization peering isn’t currently available for Win32 Store apps.


Troubleshooting client logs

Reviewing logs is the best way to understand failures. The following table provides information about the log types, what they report, and where to find them. Note that %TEMP% will be evaluated in the context of the installation, so would be for system user or logged on user based on the install behavior (system or user) set for the app.


Improvements to app processing





  • This is the main Intune client log
  • Look for "[Win32App]" and "[WinGetApp]“
  • High level orchestration of steps for all apps and specific actions for system content apps



  • Includes the Intune orchestration of the WPM library for user context actions (detection, applicability check, install, uninstall, upgrade)



  • WPM (WinGet) logs


Varies by installer

  • Store app Win32 installer logs

If the installer definition supports a custom log location, it defaults to: %TEMP%\winget\defaultStateIn future will be %ProgramData%\Microsoft\IntuneManangementExtension\Logs


Note, custom install location is not supported in manifest on many apps.

Operational Event logs

  • This includes UWP installer logs (both msstore and non-store appx)
  • Search by Package Family Name (PFN) to find your application

Event Viewer - Application and service


Logs\Microsoft\windows\appxdeploymentEvent viewer - Application and Service Logs\Microsoft\windows\appxdeployment-server


Application and Service Logs\Microsoft\windows\Store\operational


The following table is a general overview of the key lines in the Intune Management Extension logs that are helpful to understand where the app installation failure occurs.



Start of check in

“[Win32App] Requesting required apps” or
“[Win32App] Requesting available apps only”

Shows the policies received from Intune Management Extension service

Get policies = [{policies}]

Start processing subgraph with apps

[Win32App][V3Processor] Processing subgraph with app ids: {appId}

Initial detection results (used to determine if action is needed)

[Win32App][WinGetApp][WinGetAppDetectionExecutor] Completed detection for app with id: {appId}

Applicability results (used to determine if action is needed)

[Win32App][WinGetApp][WinGetAppApplicabilityExecutor] Completed applicability check for app with id: {appId}.

Install, Upgrade or Uninstall start

[Win32App][WinGetApp][WinGetAppExecutionExecutor] Starting execution of app with id: {appId}
Post-install detection results [Win32App][WinGetApp][WinGetAppDetectionExecutor] Completed detection for app with id: {appId}


Note: Use the AgentExecutor logs for user context installs and WPM logs for a deeper look into all actions (except for applicability/detection steps).


The app is reported as “Not Applicable” in the IME logs

There are a few reasons that the application may not be applicable:

  • The device is not a Windows device that supports the Intune Management Extension or it only has one core processor.
  • The Intune Management Extension version doesn’t support the new installer type (less than 1.59).
  • In the IME logs, the app appears as:
    • “NotSupported”
    • [Win32App][WinGetApp][AppPackageManager] This client machine only has 1, the application will not be installed.
    • “AppPackageNotFound”
  • The app is not available on the device.
  • None of the installers associated with the app are applicable on the device.
  • Applicability is evaluated by the WinGet library and reasons for the status may include architecture, language, and minimum operating system requirements.


Keep in mind

Some group policies may affect app deployment from the Microsoft Store. Refer to the table in the Store group policies section of Add Microsoft Store apps to Microsoft Intune.



If you have any questions or comments for the Intune team, reply to this post below or reach out to @IntuneSuppTeam on Twitter. For more troubleshooting content related to Win32 apps, check out Troubleshoot Win32 app issues and Troubleshooting Win32 app installations with Intune!

Version history
Last update:
‎May 08 2023 04:19 PM
Updated by: