Devolutions / Devolutions/UniGetUI

[BUG] Upgrade fom 3.3.0 to 3.3.1 was a desaster

Open
#3,950 25 comments 0 reactions 1 assignee Claimed by @marticliment View on GitHub
bug important needs-author-answer
Dominant language
C#
Stars
26.1k
Forks
924
Avg merge
15h 52m
Merged PRs (30d)
52

Description

### 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/marticliment/WingetUI/releases/).
- [x] I have checked the [FAQ](https://github.com/marticliment/WingetUI#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/marticliment/WingetUI/issues/new/choose)).

### UniGetUI Version

3.3.1

### Windows version, edition, and architecture

Windows 10 x64

### Describe your issue

in an office with several Windows 10 PCs I had to reinstall unigetUI manually with the exe-installer. Automatic upgrade was not possible while in fact 3.2.0 and 3.3.0 were incredibly good programmed.

Automatic upgrade was not possible. I think Martí got the crash reports.

### Steps to reproduce the issue

_No response_

### UniGetUI Log

```text
plz no
```

### Package Managers Logs

```text
no plz no
```

### Relevant information

_No response_

### Screenshots and videos

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.