Cura 4.2.1 does not start and makes 4.1 dead as well

[WillemII 0]

Hello,

To start with first my different machines. First a desktop (self made) with Windows10 Ver. 1903 Build 18362.267. Graphics Nvida Geforce GTX 650. Installed Cura 4.2.1, no problems what so ever.

Second a Laptop HP Windows10 Ver. 1903 Build 18362.267 with Intel HD Graphics Driver version 20.19.15.5070. Installed Cura 4.2.1, no problems noted.

My work Laptop Asus Vivo Book Windows10 Ver. 1903 Build 18362.239 and. 267 after update with Intel UHD Graphics 600 driver version 2420.100.6287. Installed Cura 4.2.1 will not start, reinstalled the previous beautiful working 4.1 splash screen came up until "The configuration will be updated" then disappeared and did not start up. The task manager had three cura.exe showing with 0% working but three different sizes, one had 53.2 Mb, one had 4.6 MB and the last one had 53.0 Mb. Stopped all exe and restarted the laptop. Uninstalled both Cura version and restart the laptop again. Installed Version 4.1 but it do not want to start. Uninstalled 4.1, restart installed 4.0 with the same result, no start. 

The compatibility with Windows 8 I tried at first, before I started all the rest, I forgot to mention that.

Uninstalled  4.0 installed 3.6 and it worked.

Then I had a good idea and formatted 😏 my harddrive, reinstalled Windows with version 1903, installed Cura 4.2.1 with the same results as before. Also any version with a 4 will not start anymore. Version 3.6. works beautiful as before but I'm not able to got any Version 4. to work.

That was my weekend. 

If somebody has any idea please answer me. 

I need a little help now.

 

WillemII 

[whitingjon 0]

I had a similar situation yesterday with 4.2.0 installed.

So I uninstalled it, and went to 4.2.1.

It worked all day yesterday.

This morning, went to go back in to Cura, and 4.2.1 gets stuck with the "Updating configuration....".

Now after a reboot, it appears to be ok.

 

Look at the log file it creates during loading.

%AppData%\cura is the location of mine.

Check out stderr.log

[TrollingFlies 0]

There are several threads like this one.  Are you trying to run it as an admin?

Sometimes I run a dxdiag report, save the file and Cura 4.2 will open.  Other times not.  I'm trying to find the time to contact tech support for more help, but can't find the time right now.

 

Chip

[WillemII 0]

Hello,

first thanks to the fast replies. 

To whitingjon: I did't look the the file but I will see if it still exist.

 

To TrollingFlies: Yes, I run the programs also as admin, I forgot  to mentioned that, sorry. I never run dxdiag, I will try that also. 

[WillemII 0]

Hello,

here are my different stderr.logs from my two Laptops. The log file from the Asus Laptop is very short.

 

 

stderr Desktop PC.log stderr HP-LP.log stderr Asus Vivo-LP.log

[TrollingFlies 0]

Hi Everyone,

I just spent a long time in a chat with https://ultimakernasupport.zendesk.com/hc/en-us# and thus far, seem to have a fix.  

1-Close Cura if you have it open

2-uncheck the "Send (Anonymous) print information, in the general setting in Cura settings. (See attached)

3-go to... this PC/Windows (C:)/Users/<usernamer>/Appdata/Local and delete the Cura folder

4-go to... this PC/Windows (C:)/Users/<usernamer>/Appdata/Roaming and delete the Cura folder

**You will have to reconfig your printer

5-Make sure that you are opening the program as an admin.

 

If has worked for me so far, but time will tell.  I hope this helps others out.

 

Chip

[nallath 674]

We switched out the way that this is handled for 4.3, so i expect that this won't be an issue for that release anymore.

[johnse 8]

I have a perhaps unusual situation, but it may provide another clue.

 

I’m running a Surface Book v2 that has a detachable screen that can be used as a tablet. The screen houses the Core i7 CPU with onboard Intel UHD Graphics 620 GPU. The keyboard contains a discrete Nvidia GTX1060 GPU. Sometimes the CPU apparently stops talking to the Nvidia GPU. At these times, device manage shows only the Intel GPU. Either rebooting or detaching and reattaching the screen will re-enable the Nvidia GPU.

 

When the Nvidia GPU is active, Cura runs fine. When it’s in the failed state, Cura won’t launch. So far I have 100% correlation. I have never had to run in compatibility mode or as administrator.

 

EDIT: I have also confirmed that attempting to launch Cura while in tablet mode fails. It seems that many of those with problems are using default Intel graphics...perhaps the is an incompatibility with that family of GPU?

Edited Thursday at 06:16 PM by johnse

[aringer 0]

Johnse might be on the right path. I switched off "full screen optimizations" in Windows 10 compatibility mode. Until now, Cura seems to start without problems.

[aringer 0]

No sorry, not enough,

Albert

[WillemII 0]

Hello,

Now I got time to answer all this. thanks a lot for all this.

To Trollingflies: That what you wrote is an old issue and does't really is my problem. I'm not able to even start 4.X.X anymore so I'm not getting even to the point with the checkbox. I started Cura with a blank, new installed Windows 10.

To nallath from Team Ultimaker: What do you mean? The problem with the send box?

To johnse: It looks for me also that it is a problem with the Intel graphics driver i.e. specially with Intel UHD Graphics 600. 

To aringer: On my Windows version there is not a "full screen optimization box or anything even close to that. I can only install an specific app to get that in.

 

Anyway thanks again for all trying to help.