jprochazka 0 Posted January 31 in Was there ever a fix for the 3.0 to 3.1 upgrade issue? After running into the Cura 3.1 wont start issue after upgrading I switched back to 3.0.4 just to make things work again. After not giving it much thought tonight I noticed 3.2 is on the horizon and figured I might as well give the upgrade a shot again. As was reported in the past by others after upgrading to 3.1 Cura flat out refuses to start. Even gave 3.2 BETA a try same thing. So I am thinking OK this is open source surly someone has found and fixed the issue. Sadly digging through the forums all I see are the same rehashed no working suggestion. I have deleted everything related to Cura of my computer I can find yet 3.1 nor 3.2 BETA will launch. Windows 10 is up to date. All the answers which worked for no one of course don't work for me either such as running the application as administrator, deleting the user config file (whatever that is hell I went as far as deleting everything Cura from AppData and Program Files after uninstalling everything) ,and running windows update. Here is the stderr.log and stdout.log for 3.1.0 before I deleted everything I could find related to Cura. Be nice to actually get Cura working once more... Any clues before I am stuck switching to Slic3r or Simplify3D? stderr.log stdout.log Share this post Link to post Share on other sites
nallath 530 Posted January 31 in Was there ever a fix for the 3.0 to 3.1 upgrade issue? You added outdated containers; 2018-01-30 21:38:40,982 - WARNING - cura.Settings.CuraContainerRegistry.addContainer [57]: Instance container Monoprice Select Mini_variant is outdated. Its setting version is 0 but it should be 4. It seems you didn't actually delete your local configuration. Share this post Link to post Share on other sites
