[BUG] Packages not being updated despite showing new version

### Please confirm these before moving forward

- [x] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
- [x] I have tested that this issue has not been fixed in the latest [(beta or stable) release](https://github.com/Devolutions/UniGetUI/releases/).
- [x] I have checked the [FAQ](https://github.com/Devolutions/UniGetUI#frequently-asked-questions) section for solutions.
- [x] This issue is about a bug (if it is not, please use the [correct template](https://github.com/Devolutions/UniGetUI/issues/new/choose)).

### UniGetUI Version

2026.2.2

### Windows version, edition, and architecture

Windows 11 25H2

### Describe your issue

Some packages will update and show the new version number in UniGetUI but when opening such programs they are still in their previous version.
For example with qBitTorrent, I have currently installed the 5.2.2 version, UniGetUI found an update for the 5.2.3 and supposedly installed it, even showing the new version in version column:

But when starting qBitTorrent again it will say there's an update (for 5.2.3) and the actual version is still 5.2.2:

I have so many programs installed, how can I know they are actually being updated and not UniGetUI pretending they were without even checking? How does it keep track of versions without verifying the package was actually updated? It doesn't make sense, if UniGetUI knows what version the package was before updating, how can't it detect the version again after trying to update a package or detect that the update actually failed? I can't even force the update again because it assumes the package is already updated.

### Steps to reproduce the issue

_No response_

### UniGetUI Log

```text
-
```

### Package Managers Logs

```text
-
```

### Relevant information

_No response_

### Screenshots and videos

_No response_

Start by reproducing the qBittorrent 5.2.2-to-5.2.3 update described in the issue and inspect how UniGetUI records update results and refreshes installed versions. Done means failed or ineffective updates are detected, the displayed version matches the actual installed version, and the package can be offered for update again when necessary.

Written by the indexing model from the issue text.