Troubleshoot: JumpCloud App Catalog Errors

After installing an application from the App Catalog, reference the command status. Use the information reported in Status Details to troubleshoot issues:

Status Details: failed to ensure winget installation

Symptoms

Installing software on a Windows machine from the JumpCloud App Catalog may result in a Status of “Install Failed” with a WinGet error in Status Details:

  • failed to ensure winget installation: failed to execute winget list. exit status 0xc0000135
  • failed to ensure winget installation: %!w(<nil>)

These types of errors indicate that the Windows Package Manager (WinGet) is either not installed, is corrupted, or its dependencies (like the required runtime libraries) are missing.

Resolution

Work through the following troubleshooting steps to resolve the issue:

  1. Verify WinGet installation:
    • Open a command prompt or PowerShell as admin and run winget --version.
      • If a version number is reported, WinGet is installed.
      • If not, proceed to install WinGet.
  2. Install or update WinGet:
    • Ensure you have the App Installer package installed:
      • Open the Microsoft Store.
      • Search for App Installer.
      • If it’s not installed, install it. If it’s already installed, update it (if an update is available).
  3. Test the installation again by running winget --version.
  4. Install any missing dependencies:
  5. Check environment variables:
    • Ensure that the path to WinGet is included in your system’s PATH environment variable:
      1. Open System Properties > Advanced > Environment Variables.
      2. Under System variables, look for Path.
      3. Add this path if it’s missing: C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
  6. Reinstall WinGet:
    • If WinGet is corrupted:
      1. Open Settings > Apps > Installed apps.
      2. Search for App Installer and uninstall it.
      3. Reinstall App Installer from the Microsoft Store.
    • After performing these steps, unbind and rebind the device to the application again. Installation may take up to 30 minutes. 

If there are still issues, check the Windows event viewer logs and reach out to JumpCloud support. Include the Agent and event viewer logs in your support ticket. See Use JumpCloud Log Collection Scripts for instructions on extracting Agent logs.

Status Details: The installer file’s hash does not match the manifest.

Symptoms

An installed application shows a Status of Install Pending with the following Status Details:

The installer file's hash does not match the manifest. The app install is pending until the installer hash is updated in the winget manifest by the publisher. The app install will fail if the hash is not updated by Month Day, hh:mm (UTC).

This error occurs because the hash of the installer file for the application you are trying to install does not match the hash listed in the WinGet manifest. The hash ensures the integrity and security of the installer file, confirming that it has not been altered or tampered with. There are several reason why this might happen:

  • The publisher might have released a new version of the installer file, but did not update the corresponding hash in the manifest file.
  • The installer file may have been corrupted during the download process, leading to a mismatch in the hash.
  • If the installer file was modified by an unauthorized source, the hash will not match, triggering the error.
  • The hash in the manifest file might have been entered incorrectly by the publisher.

Resolution

The publisher of the app must update the hash in the manifest to match the new installer file. As a workaround until the hash is updated by the publisher, you can leverage other Software Management features from JumpCloud like the Jumpcloud Private Repository or Chocolatey.

Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case