Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] UniGetUI 3.1.1 doesnt start anymore #2863

Closed
4 tasks done
makedir opened this issue Oct 20, 2024 · 9 comments · Fixed by #2982
Closed
4 tasks done

[BUG] UniGetUI 3.1.1 doesnt start anymore #2863

makedir opened this issue Oct 20, 2024 · 9 comments · Fixed by #2982
Assignees

Comments

@makedir
Copy link

makedir commented Oct 20, 2024

Please confirm these before moving forward

  • I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions.
  • This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version

3.1.1

Windows version, edition, and architecture

Windows 11 24h2

Describe your issue

This is now the 3rd time this happens with different versions. Can you please try to stop breaking this program?

Steps to reproduce the issue

UniGetUI Log

-

Package Managers Logs

-

Relevant information

No response

Screenshots and videos

No response

@makedir makedir added the bug Something isn't working label Oct 20, 2024
@marticliment
Copy link
Owner

marticliment commented Oct 21, 2024

Any crash report on Event Viewer?

Can you please try to stop breaking this program?

As you will understand, I don't intentionally break things...

@Yentis
Copy link

Yentis commented Oct 21, 2024

I have the same issue on 23H2
image

@marticliment
Copy link
Owner

Disabling the internet makes UniGetUI work again?

@Yentis
Copy link

Yentis commented Oct 21, 2024

Yes, it starts if I disconnect my internet

@makedir
Copy link
Author

makedir commented Oct 21, 2024

I had this issue before on some earlier versions too some months ago. The resolution was to manually remove UnigetUI and reinstall the latest version. But that removed all the apps I had installed through chocolatey.

@makedir
Copy link
Author

makedir commented Oct 23, 2024

Beschreibung
Name der fehlerhaften Anwendung: UniGetUI.exe, Version: 3.1.1.0, Zeitstempel: 0x666b0000
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.4957, Zeitstempel: 0xc5225d0f
Ausnahmecode: 0xc000027b
Fehleroffset: 0x0000000000133b32
ID des fehlerhaften Prozesses: 0x83c
Startzeit der fehlerhaften Anwendung: 0x01db24e56483d9d4
Pfad der fehlerhaften Anwendung: C:\Program Files\UniGetUI\UniGetUI.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: 32a21ffb-98ca-4efb-9ee6-44e68650e901
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

@makedir
Copy link
Author

makedir commented Oct 23, 2024

It seems restarting UnigetUI a few times resolves this issue and you can update to 3.12

@pseisam
Copy link

pseisam commented Oct 29, 2024

It seems restarting UnigetUI a few times resolves this issue and you can update to 3.12

This actually worked after a few restarts (<10). And they say doing the same over and over again and expecting other results is the definition of insane... :D

(So probably a race condition)

@makedir
Copy link
Author

makedir commented Nov 1, 2024

It happened now again here on 3.12. Crashing several times opening it. Until after 10 tries opening it or so, it opened. And I saw it announced an update to 3.13. I think this issue might be triggered, if there is an update push notification in the background, when the app launches.

@marticliment marticliment linked a pull request Nov 15, 2024 that will close this issue
1 task
@marticliment marticliment removed this from the Bugs milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants