Windows App version not selectable in Blueprint: configure Verification Criteria on the EXE application

Windows

Title: Windows EXE version missing in Blueprint — configure Verification Criteria

When adding a Windows EXE application to a Blueprint, the version picker appears empty and no version can be selected.

Why this happens

Esper requires Verification Criteria to be configured for each Windows EXE application before it can be assigned to a Blueprint. An EXE can be uploaded and visible in the Windows Apps list without this information, but the Blueprint editor will not expose any version until those fields are completed.

Steps

1. Navigate to Apps & Configuration → Windows Apps in the Esper Console.
2. Locate the EXE application that shows no version in the Blueprint editor and click its name to open the detail view.
3. Click Edit on the EXE package configuration. This opens the fields that control how Esper detects whether the application is correctly installed on a device.
4. Complete all required fields in the Verification Criteria section. These fields tell the Esper Agent how to confirm successful installation — without them, no version can be published for Blueprint use.
5. Click Save.
6. Return to Apps & Configuration → Blueprints, open the relevant blueprint, and add the application again. The version picker should now list the configured version.

Verify: The version picker in the Blueprint editor displays the application version immediately after reopening the add-application dialog. Select the version, save the blueprint, and confirm the application appears in the blueprint's app list with the correct version number shown.

If this doesn't resolve it

If the version picker remains empty after saving Verification Criteria, try the following before contacting support:

• Confirm the save succeeded: Reopen the EXE application in Apps & Configuration → Windows Apps and verify the Verification Criteria fields still contain the values you entered.
• Reload the Blueprint editor: Close the browser tab, reopen the Esper Console, and navigate back to the blueprint.
• Clear the browser cache: A stale cache can prevent the Console from reflecting recent changes. Clear the cache, reload, and try again.

If the version still does not appear, contact Esper Support. Include your tenant name, the application package name, and a screenshot of the Verification Criteria fields as saved in the Console.

Still need help?

If you're still unable to select your Windows App version in Blueprint after configuring verification criteria, please submit a support ticket and include your EXE application name, the verification criteria you've configured, and screenshots of your Blueprint configuration.