Windows Modern Application Installation: Behaviors, Edge Cases, and Troubleshooting Guidance

This article documents expected behaviors, configuration dependencies, edge cases, and common troubleshooting scenarios related to Windows Modern Application deployments.

SOTI MobiControl

Windows Modern

Administrators may encounter scenarios where applications:

• Installed successfully, but reported as Failed or Not Installed
• Remain stuck in an Installing state
• Consume storage without appearing in the application catalog
• Fail due to detection mismatches or missing prerequisites
• Require manual intervention for certificates, dependencies, or installation commands

These behaviors are commonly observed with EXE-based deployments due to the lack of standardized metadata and vendor-specific installer behavior.

APPX and MSIX deployments are generally more predictable because they rely on the Windows package's deployment engine, but they may still fail if dependencies or prerequisites are missing.

This guidance applies to the following application package formats:

• EXE
• APPX
• MSIX
• APPX Bundle
• MSIX Bundle

It also outlines common causes of installation failures, detection of mismatches, upgrade inconsistencies, and deployment validation issues.
Most installation-related issues are caused by gaps in application configuration rather than platform defects.

Applicable deployment scenarios include:

• Mandatory application deployments
• Optional application deployments
• Custom-signed applications
• Applications requiring PowerShell pre-install or post-install scripts
• Applications deployed through Windows modern application management workflows

1. Application Detection and Validation

Application installation status is determined through detection logic rather than installer exit codes alone.

The platform validates application presence using:

• App ID detection
• Package identity verification
• Winget-based package lookup behavior

Important: Incorrect App IDs may allow the application to install successfully while still reporting:

• Failed
• Not Installed

This behavior is expected when detection metadata is incorrect.

2. EXE Application Configuration

EXE applications require manual configuration of:

• App ID
• Version
• Installation command

There is no automatic metadata discovery for EXE installers.

Common Risks

Incorrect configuration may result in:

• False installation failures
• Stuck installation states
• Upgrade inconsistencies
• Incorrect application reporting

Silent Installation Commands

Many EXE installers require explicit silent installation arguments.

Common methods for identifying supported commands include:

• app.exe /?
• app.exe /help

Not all installers expose supported arguments. Installer behavior is controlled entirely by the application vendor.

Example of a few commands that are available.

3. Retry and Queue Behavior

Mandatory applications:

• Retry automatically up to three times
• Retry during the next device check-in cycle
• May temporarily block the installation queue if installation fails repeatedly

A 60-minute execution timeout helps prevent indefinite queue blocking.

Optional applications:

• Attempt installation once
• Return to Install Available after failure
• Require manual retry by the user

This behavior is expected.

4. Certificate Requirements

Applications signed with non-Microsoft certificates require the signing certificate to exist on the device before installation.

Recommended Action

Deploy the certificate separately using Profiles prior to deploying the application.

5. Script Execution

Only PowerShell scripts are supported.

Scripts are configured per application and execute in the following order:

1. Pre-install
2. Post-install

Common Use Cases

• Environment preparation
• Dependency installation
• Cleanup operations
• Configuration changes

Script failures may affect installation completion behavior. Scripts should always be validated before production deployment.

6. APPX and MSIX Package Behavior

APPX and MSIX packages are managed by the Windows package deployment engine.

Key Behaviors

• Dependencies must be uploaded explicitly
• Missing dependencies prevent installation
• Older platform versions below SOTI MobiControl 2026.0.0 may require additional system configuration changes

Bundle Packages

APPX Bundle and MSIX Bundle packages may contain multiple architecture-specific packages.

The deployment engine automatically installs the appropriate package for the target device architecture.

7. Simplified Installation Workflow

 

The following validation steps are recommended before production deployment:

• Manually test EXE installers outside the platform
• Confirm the correct App ID
• Validate silent installation arguments
• Verify application dependencies
• Validate signing certificates
• Confirm architecture compatibility for bundle packages
• Test PowerShell scripts independently before deployment

Successful validation significantly reduces deployment failures and support escalations.