[IMPROVEMENT] Automatically (prompt to) reinvoke (un)installers interactively when files they require are in use.

[RokeJulianLockhart]

Please confirm these before moving forward.

• I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
• This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
• This improvement is not a bug. If you want to report a bug, please use this template.

Describe the improvement

Reinvoking winget upgrade 'OBSProject.OBSStudio' with the -i flag ¹ allows the user to actionably close the applications that are utilizing the files, ² which OBS necessitates access to, in order to upgrade itself.

Describe how this improvement could help users

Currently, a user must read the failure log, ascertain which error message is relevant, understand it, and locate how to reinvoke the upgrader interactively. This is infeasible to expect of the userbase of UniGetUI.

Footnotes

1. github.com/microsoft/winget-pkgs/issues/105965#issuecomment-2460765408 ↩

2. obsproject.com/forum/threads/please-close-this-these-application-before-installing-obs-fix.125012/#post-667767 ↩

[marticliment]

Reinvoking winget upgrade 'OBSProject.OBSStudio' with the -i flag 1 allows the user to actionably close the applications that are utilizing the files, 2 which OBS necessitates access to, in order to upgrade itself.

This is not exactly true.
Using the -i flag triggers the installer to show in a graphical mode (not automated), and it happens to be the case that the installer/uninstaller for OBS does only handle the case where it is already running when run interactively. It would not make sense to trigger the interactive install mode when an operation fails due to a running application, since each installer will handle this in a different way (and OBS installer should already take care of the running app when running interactively)

[RokeJulianLockhart]

It would not make sense to trigger the interactive install mode when an operation fails due to a running application, since each installer will handle this in a different way

Martí Climent (@marticliment), I suppose it would be infeasible to maintain a whitelist.

OBS installer should already take care of the running app when running interactively

In my case, the running application was part of my driver software, so it can't.

[marticliment]

The thing here is that OBS is the only installer who exposes this behaviour.

What you can do is set OBS installation options to update interactively