Windows required app installs slowly and msix missing from App catalogSolved

Hi @zariah. Required Apps and manual app deployments behave quite differently in Hexnode, which explains the timing discrepancy you are seeing.

A manual install, remote action, or automation is a one-time deployment trigger that executes immediately. A Required Apps policy, however, is intended for continuous enforcement. Hexnode checks whether the required app is present during scheduled device syncs and background evaluations. If the app is missing, Hexnode queues the installation during that sync cycle, which is why there is a delay compared to a manual push.

To answer your policy question: yes, multiple Required Apps policies can be associated with the same Windows device. Hexnode evaluates all applicable policies. Also, for your awareness, standard Windows users do not need local admin rights for these deployments because Hexnode installs apps silently using system-level privileges.

Regarding the MSIX app missing from the App Catalog: a successful upload confirmation just means the file was received by the server. The package still needs to finish processing and indexing before it becomes available in policy sections like the App Catalog. You can verify its status by going to the main Apps tab in your portal and checking that the app:

• Appears in the inventory.
• Shows Windows as the platform.
• Has a valid version number populated.
• Has completed processing successfully.

Please let me know if you have any further questions or need additional assistance with your setup.

Best regards,
Eden Pierce
Hexnode UEM

Update on this: both items eventually worked. The required Windows app installed on the test devices on its own, and the uploaded MSIX enterprise app eventually became available to select for the App catalog. 

The confusing part was just the delay, especially since the Msix took a while to show up after the upload confirmation. But the sync timing and indexing explanations make perfect sense. 

Hi @zariah, I am glad to hear both the deployment, and the App Catalog are working for you now.

As you noted, the behavior you experienced points entirely to standard policy evaluation cycles and app inventory processing times rather than any issue with the app packages themselves.

If you ever run into a situation where a Required App seems stuck for an unusually long time, you can always open the device in Manage > Devices and review the Action History to see exactly when the install command was triggered by the system.

Best regards,
Eden Pierce
Hexnode UEM