Upgraded to 4.6.1, now Cura won't open

[emptyinbox 0]

Cura doesn't start.  Goes to the splash screen and hangs, then I have to force quit.  Rebooting doesn't fix the issue.  Uninstalling and Re-Installing does not fix the issue.

 

Cura has always taken forever to start, now after 5+ minutes it's still just doing nothing.

 

Any ideas?  I don't see any logs or anything, and there's no console error since it just hangs.

 

I wish Cura would behave like a 21st century program and just update in place instead of having to use InstallShield or whatever and patch over top of itself leading to errors like this.

[emptyinbox 0]

Finally fixed my issue by deleting the cura/4.6 path in %AppData% and then uninstalling and reinstalling again.  In the process I lost my configuration settings.  😠

 

I find it incredibly annoying to open Cura and see "UPGRADE TO 4.6.1 YOU DEFINITELY WON'T REGRET IT". Every. Single. Time.  I'm this close to blocking Cura's internet access so it never knows when there's an update.

 

/rant

Edited May 12, 2020 by emptyinbox
clarity

[ahoeben 1,948]

8 hours ago, emptyinbox said:

I'm this close to blocking Cura's internet access so it never knows when there's an update.

 

In the General preferences, scroll down to the "Privacy" section and uncheck "Check for updates on start".

[nallath 1,120]

Look, i believe you didn't find anything in the logs. I also think that we might be able to see things in the logs that don't make sense to you.

So as always:

1. Please report bugs / issues on github.

2. Fill in the entire bug template when doing so.

 

That being said; How would updating in place prevent this issue?

[Slegnor 0]

I was having the same issue on a 3 monitor setup, Windows 10 x64.

I had been using Cura 4.6.1 to slice with no issues, I closed the program and then went to re-open about 30 minutes later and it just wouldn't load.  Reboot, reinstall, trying Cura 4.4 which i still had installed, installing 4.7, nothing would make it load on any version.

 

I eventually found the issue and it's not one I've seen mentioned before so thought I would share.

 

I run GPUTweak for my graphics card, it has an option for an On Screen Display (OSD) overlay which i never use. 

Somehow this got enabled (probably via a keyboard shortcut which is the same in another application) and as soon as I disabled this, Cura started.
I re-enabled it and Cura would fail to load again.

 

Just something for people to try should they also be running GPUTweak or other software with overlays (FRAPS, MSI Afterburner etc)

Edited October 19, 2021 by Slegnor