Application Update Stays Failed

Problem

One or more endpoints show a Failed update for an application, and the update can’t be redeployed. The application is still installed and works on the endpoints.

For example, endpoints with the older Visual C++ Redistributable package showed a Failed update after the package was replaced in the catalog.

Cause

Repository App versions come from winget. See Repository Apps. Sometimes a package in winget is split into separate packages, for example one per architecture. The old package then no longer exists in the catalog.

Endpoints that tracked the old package keep a Failed update entry that points to a package that isn’t available anymore. CapaOne can’t redeploy it, so the entry stays Failed.

Solution

Confirm that the application is installed on the affected endpoints. A Failed update doesn’t mean the application is missing.
Go to Windows → Applications → Overview and open Repository Apps Failed. The list shows the Repository Apps with failed updates.
Click the app. The app opens with a list of the endpoints where the update failed.
Select the failed endpoints and click Remove.

Because the package no longer exists in the catalog, the update doesn’t come back. After the endpoints check in, they no longer show the failed update.

To remove the failed update for a single endpoint instead, open the endpoint and select Applications. Open the menu (☰) at the right of the failed app and select Remove.

To install the application on new endpoints, assign the current package from the catalog.

Failed Company Apps

Company Apps have their own view of failed installations:

Go to Windows → Applications → Company Apps and open the app.
Select the Endpoints tab. It shows the app’s status on each endpoint.
For an endpoint where the installation failed, select Redeploy to try again, or Remove.

The actions available depend on the endpoint’s status: