Please confirm these before moving forward.
Describe the improvement
Improve error reporting when a package installer fails because running processes are blocking the installation (e.g. Git).
Current behavior
When updating Git through UniGetUI using WinGet, the installation may fail with a generic error.
In my case, UniGetUI reported only that the update had failed.
After inspecting the installer log generated by the package installer, the actual reason was:
The following process(es) use Git for Windows:
Git for Windows (PID ...)
...
Please terminate those processes and retry.
The installer aborts because it is executed in silent mode (/VERYSILENT), so it cannot prompt the user to close the running processes.
Expected behavior
If possible, it would be helpful if UniGetUI could surface the underlying installer error whenever it provides a more specific reason than the generic failure reported by WinGet.
For example, in this case, UniGetUI could display a message such as:
Git is currently being used by one or more running processes. Please close the applications using Git (or terminate the listed processes) and try the update again.
Optionally, UniGetUI could offer a Retry button after the user has closed the blocking processes.
Describe how this improvement could help users
Without checking the installer log, it is not obvious why the update failed. A clearer and more actionable error message would save users from having to manually inspect log files for a very common scenario.
This is not a WinGet or Git installer bug—only a suggestion to improve the user experience in UniGetUI by surfacing the actual installer failure reason whenever possible.
Please confirm these before moving forward.
Describe the improvement
Improve error reporting when a package installer fails because running processes are blocking the installation (e.g. Git).
Current behavior
When updating Git through UniGetUI using WinGet, the installation may fail with a generic error.
In my case, UniGetUI reported only that the update had failed.
After inspecting the installer log generated by the package installer, the actual reason was:
The installer aborts because it is executed in silent mode (
/VERYSILENT), so it cannot prompt the user to close the running processes.Expected behavior
If possible, it would be helpful if UniGetUI could surface the underlying installer error whenever it provides a more specific reason than the generic failure reported by WinGet.
For example, in this case, UniGetUI could display a message such as:
Optionally, UniGetUI could offer a Retry button after the user has closed the blocking processes.
Describe how this improvement could help users
Without checking the installer log, it is not obvious why the update failed. A clearer and more actionable error message would save users from having to manually inspect log files for a very common scenario.
This is not a WinGet or Git installer bug—only a suggestion to improve the user experience in UniGetUI by surfacing the actual installer failure reason whenever possible.