[Package Issue]: "Bitwarden.Bitwarden" fails to update unless you manually close the app.

[richardhttps]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Update fails with a Bittwarden installer prompt showing the following error:

Failed to uninstall old application files. Please try running the installer again.:2

winget update is initiated with these arguments:
update --id "Bitwarden.Bitwarden" --exact --source winget --accept-source-agreements --disable-interactivity --silent --include-unknown --accept-package-agreements --force

Steps to reproduce

Use winget to update Bitwarden while Bitwarden is open in the background, using the following arguments:
update --id "Bitwarden.Bitwarden" --exact --source winget --accept-source-agreements --disable-interactivity --silent --include-unknown --accept-package-agreements --force

Actual behavior

Update fails with a Bitwarden installer prompt that shows the following error:

Failed to uninstall old application files. Please try running the installer again.:2

Expected behavior

Update in the background without user interaction.

Environment

Windows Package Manager v1.9.25200
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.3037
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.24.25200.0

Screenshots and Logs

No response

[Dragon1573]

I think "automatically close the application before upgrading" should be done by the install wizard itself.

I'm currently using package AList.AList as a local web server and I register it as a Windows Service using package NSSM.NSSM. When I upgrade AList via WinGet, I HAVE TO manually stop the service in advanced, otherwise the upgrade will fail.

[Trenly]

It is an intentional design choice of WinGet to not close running applications before upgrade so that WinGet does not cause the loss of data from terminating an application in an un-saved state. If the installer provides a specific return code that the files are in use, we can add that to the manifest, but @Dragon1573 is correct, any automatic closing of the application must be done by the installer of the application.

[Policy] Area External; [Policy] Installer Issue

[Dragon1573]

If the installer provides a specific return code that the files are in use, we can add that to the manifest.

What behavior is it at the moment? Will winget.exe just notify users for saving data and quit the application themselves? Or it will prompt for a request, save and terminate automatically after users' approval?

[Trenly]

If the installer provides a specific return code that the files are in use, we can add that to the manifest.

What behavior is it at the moment? Will winget.exe just notify users for saving data and quit the application themselves? Or it will prompt for a request, save and terminate automatically after users' approval?

Neither. It just provides a better message as to why the install failed