Application Update Stays Failed
Problem
Section titled “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.
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
Section titled “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.
Adobe Acrobat Reader shows Not compliant on endpoints with Acrobat Pro or Standard
Section titled “Adobe Acrobat Reader shows Not compliant on endpoints with Acrobat Pro or Standard”Problem
Section titled “Problem”You install the Adobe Acrobat Reader Repository App on an endpoint, and the endpoint shows Not compliant. The package log contains lines like these:
Install: Shell_Execute: Completed with status: '1603'Installation returned 1603. Adobe Acrobat-family product is already installed: Adobe Acrobat (64-bit) 26.002.22031This may be a higher edition than Adobe Acrobat Reader, such as Adobe Acrobat Pro or Standard.The package will not remove or replace the existing Adobe Acrobat installation.SCRIPT ENDED WITH EXITCODE: 504To get the log, see Collect the agent logs.
The endpoint already has Adobe Acrobat Pro or Adobe Acrobat Standard, not the free Adobe Acrobat Reader. Adobe installs Reader and the paid editions as the same Acrobat product family, so the Reader package can’t install on top of a paid edition. The package doesn’t remove or replace the existing Acrobat installation.
CapaOne detects which Acrobat edition an endpoint has:
| Installed on the endpoint | Update offered |
|---|---|
| Adobe Acrobat Reader (64-bit) | Adobe Acrobat Reader (64-bit) |
| Adobe Acrobat Reader (32-bit) | Adobe Acrobat Reader (32-bit) |
| Adobe Acrobat Pro or Standard | None |
The endpoint shows Not compliant only when someone installs Reader on it manually from Repository Apps. If the Reader installation fails for any other reason, the endpoint shows Failed.
Solution
Section titled “Solution”- Don’t install Adobe Acrobat Reader on endpoints that have Acrobat Pro or Standard. Acrobat Pro and Standard open PDF files without Reader.
- Exclude these endpoints from the groups or the Automation rules that deploy Reader.
CapaOne offers Adobe Acrobat Reader (32-bit and 64-bit) as Repository Apps. Adobe Acrobat Pro and Standard aren’t available as Repository Apps.
Failed Company Apps
Section titled “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:
| Status | Actions |
|---|---|
| Failed | Redeploy, Remove |
| Up to date | Redeploy, Uninstall |
| Not installed | Install |