sn4k3 / UVtools

MSLA/DLP, file analysis, calibration, repair, conversion and manipulation
GNU Affero General Public License v3.0
1.15k stars 103 forks source link

[Bug] UVTools No longer working on Windows 11 After 4.2.1 to 4.2.2 Upgrade #837

Closed sdmorrey closed 5 months ago

sdmorrey commented 5 months ago

System

Windows 11 64bit, Intel Processor, 32GB of RAM

Printer and Slicer

Not relevant

Description of the bug

Everything was working great. Then I upgraded to 4.2.2 which appeared to go well and literally nothing happened. I don't even see an error message. It just fails to launch.

Thinking it was something weird with my setup I uninstalled 4.2.2 and reinstalled 4.2.1 which of course worked. Then I tried to install 4.2.2 from the distribution .msi and the same thing happened.

I'm unsure if it's a problem with upgrading or with 4.2.2 itself, but I've tried every way I can think of to upgrade this.

It does not launch at all, there is no crash screen and I'm not sure where it would log to. I've even tried launching from the command prompt but I get nada.

How to reproduce

Install 4.2.1 using winget as per the front page Upgrade to 4.2.2 Try to launch Tear hair in frustration

Files

No response

github-actions[bot] commented 5 months ago

This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌

sn4k3 commented 5 months ago

For Windows users v4.2.1->v4.2.2: For who is upgrading from v4.2.1 to v4.2.2 need to uninstall UVtools first and then install the new version. Or upgrade, and run installer again and select repair action. Due to the downgrade of the UI framework it wont be upgraded via MSI installer, that causes the program to not launch.

sdmorrey commented 5 months ago

That's great information to know. Thank you so much! Perhaps the readme could be updated?