Cura 2.3.0 splash screen then nothing else

[LePaul 283]

Well this is annoying, the beta ran alright. While loading some large parts this evening, Cura sat on "preparing to slice" for a long time, never doing anything.

I downloaded the Windows 64-bit version and installed that. Allowed it to uninstall the beta and then install.

At the end of the installation and option to run Cura, nothing happened.

I tried the install again. No splash screen. Even checked the task manager...no where to be found

Cleared temp files (CCleaner), reboot....install again.

Now when I launch Cura I get the splash screen but nothing else.

Windows 10 (latest build) 64 bit. Help

[neotko 1,361]

From beta to final it was problematic to have temp files of previous versions. Maybe it needs a full Cura cleaning but I don't use windows (thank god )

Maybe there's config file making your cura banana.

[nilrog 94]

Not sure what CCleaner deleted. But I had to delete the whole cura-user-folder before the final 2.3 build started working.

[LePaul 283]

CCLeaner cleans up temp file and so on (seriously good program, Google it)

Well I expected better than "Thank God I run a Mac" from support. My goodness.

[nallath 568]

CCLeaner cleans up temp file and so on (seriously good program, Google it)

Well I expected better than "Thank God I run a Mac" from support.   My goodness.

 

I think you are better off removing all the files yourself.

[neotko 1,361]

CCLeaner cleans up temp file and so on (seriously good program, Google it)

Well I expected better than "Thank God I run a Mac" from support. My goodness.

 

Oh I was just pulling your leg since we know each others, don't worry I will answer on a professional and serious manner.

[LePaul 283]

Text comes across dry...my response was [intended] to be humorous too.

So remove the folder under Program files and try again? Will do.

[neotko 1,361]

Holy we need more emojis

I think that if cura works like on mac it might do temp files on other folders.

[LePaul 283]

Well, as detailed elsewhere, I have the exact same problem on my work computer.

That's running Windows 7 64-bit

Un-installed 2.3.0

Deleted the Program Files \ Cura 2.3.0

Re-installed.

At end of install, selected "Run after install" Nothing happened.

Launched Cura 2.3.0 from Start - All Programs - Cura 2.3.0

Splash screen loads, starts load up steps...then vanishes

What should I try next?

[neotko 1,361]

Maybe a full search for cura word on the hard disk. Maybe the beta left some files that are causing conflict?

[LePaul 283]

Well I don't want to loose 15.4.2 as I have those settings set for my UMO

Awaiting some troubleshooting tips from the developers

[ahoeben 462]

Have you tried renaming c:\users\[your name]\appdata\local\cura to cura.bak?

Edited October 26, 2016 by Guest

[LePaul 283]

I'll check from home

Unable to find that on the work PC (could be permissions on the work computer)

[ahoeben 462]

Sorry, it is "AppData" instead of "Application Data". You may have to type in the path, because the "AppData" folder is hidden by default.

[LePaul 283]

That worked....renamed the folder and installed it again

[nilrog 94]

Good...that was the folder I meant above when I just wrote "cura user folder"

Glad to hear you are back on track again

[ahoeben 462]

renamed the folder and installed it again

 

Installing again was not necessary. Could you zip up the renamed folder and post it somewhere so that we can figure out what is happening?

[LePaul 283]

Correct, on my work PC I just renamed the folder and now it is working.

@ahoeben , message me your email and I will send the zipped folder to you

Edited October 27, 2016 by Guest

[LePaul 283]

Oh wait, I have @nallath 's email, I will send it to him

[LePaul 283]

@ahoeben,

@Nallath emailed back with some good information

I also placed your suggestion as the Best Answer, in case others run into a similar issue

[ahoeben 462]

Thanks. Any info worth sharing in the email from Nallath?

[LePaul 283]

I'll let him answer that

[nallath 568]

Uh, LePaul also tested 1.99, which also left some profiles behind. Those profiles never got a proper upgrade plugin, but the 2.1 to 2.3 upgrader did try and upgrade them, which led to horrible results (profiles with type machine_instance_profile).