Cura не запускается на windows 10

Maybe do you have a log file of Cura starting unsuccessfully (without the compatibility mode set)?

Copy link

Contributor

Author

Very weird! Then maybe running this via the command line would give a bit more output to debug what’s going on. Here’s some instructions, though you seem to know your salt but just in case:

1. Press Win+R.
2. Type cmd and press enter.
3. In the command window, type C:\Program Files\Ultimaker Cura 4.0\Cura.exe (or wherever you installed it).

I’d expect it to produce something in STDCOUT then… 🤔

Copy link

Contributor

Author

Run eventvwr.msc and check Windows Logs\Application for any Cura-related entries.

fwiw I’m running Cura 3.6 and 4.0 under Windows 10 64-bit edition (17763) without any such issues.

Copy link

Contributor

Author

We’re also getting this bug report via the support channel of Ultimaker (who gets it via resellers who gets it from customers).

If it helps, my issue was actually caused by the fact my laptop has multiple graphics chipsets. My laptop has both Intel Graphics on board but also a dedicated Nvidia 1060 as well. If I configured the app to always start using the Intel Chipset it opens fine, it only has an issue with the Nvidia chipset.

It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine.

Thanks
Jamie.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

yes. me too on my microsoft surface 2017 model (windows 10)

If it helps, my issue was actually caused by the fact my laptop has multiple graphics chipsets. My laptop has both Intel Graphics on board but also a dedicated Nvidia 1060 as well. If I configured the app to always start using the Intel Chipset it opens fine, it only has an issue with the Nvidia chipset. It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine. Thanks Jamie.

I think I have this problem, too. How do you make it use Intel rather than Nvidia?

I disabled Intel UHD 620 in the control panel and Cura 4.0 now runs. #5699

Copy link

Contributor

Author

Same here. (MS Surface Pro 4; Intel HD Graphic with dual screen setup)
Only extra Plugin is OctoPrint.

same here (i3-6100 with integrated Intel GPU), Windows 10 x64.
Tested with Cura 3.6 and 4.1

Any luck with this? interestingly i also have intel UHD620 as graphic card (notebook), so this issue might be related to it

No luck for me. I still have to disable UHD 620 when I want to use Cura.

@Donner-Party you have another graphic card right? i dont think thats a option for me, i made it work with win7 compatibility, but its kinda slow

Yes. My laptop has dual graphics processors.

This thread on the Ultimaker forums seems to be confirming an issue with Intel GPUs. https://community.ultimaker.com/topic/29138-cura-421-does-not-start-and-makes-41-dead-as-well/?tab=comments#comment-245633

I have a SurfaceBook v2. This has an Nvidia GTX 1060 in the detachable keyboard and an Intel UHD 620 in the screen. When the screen is detached (Intel GPU only) Cura will not start. When connected to the keyboard it starts fine.

I did have an issue where the Nvidia adapter would stop responding. When this happened, again with only Intel GPU available, Cura would not start.

When Cura fails to start like this, there is no log information written.

In my case, I have 100% repro for having it start or fail under these conditions.

Yup, same here on a Surface Pro 2017
Cura starts up and runs a process in the background but never creates a window

TaskManager Process view

Same issue on Windows 10/64 laptop with just the Intel HD Graphics 520 GPU. I’ve only been able to get Cura to open a couple times, but some article I’d seen had mentioned trying over and over — so I’ve been attempting to open it about a dozen times both as administrator and not, before wiping them out in Task Manager and starting over. It has worked a couple times but the method may have nothing to do with it.

Today, I succeeded by running in Win8 compatibility mode and hitting Test the program 3-times (without killing the failed processes). Finally got the Cura splash screen to load on the third try and the program to open. I’ll try to come back and edit this comment if I reboot and succeed with same method a few times.

This issue still exists in 4.3!
Is this ever going to be addressed?

I have to revert to 4.1 (again!!!) in order to have Cura running on my MS Surface Pro 2017

We’re trying to fix this. Since 4.3 it also started reproducing on our test printers. We still have no idea what’s causing it though and it hasn’t happened yet on any computer with the debugging tools to fix it. And it’s a bit of a phantom bug, too, as is evident by you reporting that it works in 4.1 but not in 4.3 while the original issue was reported for 3.6 and 4.0.

This is happening with me on my fully updated Surface Book 2 (Core i5 with integrated Intel graphics only) with Windows 10 and Cura 4.1. If I start Cura, the Cura process appears in task manager, but never opens a window. If I start another Cura instance, it does the same thing. Restarting Windows or power-cycling the machine don’t fix the issue. I’ll see if reinstalling Cura does.

Update: Uninstalling Cura (full uninstall, including configuration files), restarting Windows, and reinstalling Cura doesn’t fix the issue for me. However, reinstalling, then setting Windows 8 compatibility mode did: https://community.ultimaker.com/topic/27056-cura-36-and-40-dont-start/?do=findComment&comment=236568

Hi @Adminius , thanks for the report. Please report again if you have any further problems related to this.

Hi @reibuehl , thanks for the report, sorry it didn’t help you.

Could you also try to run cura but then via commandline? Some things are logged before the logging plugins are loaded (so they don’t get written to the semi permanent logs).

Copy link

Contributor

Author

Hi, I had a similar problem with another slicer.
You have to go to the system registry, delete the records and leave that window open.
Open Cura, go to the registration window and update data, if there is an error it will appear there.

Similar issue here. Cura 4.4.1 installed fine on Win 8.1 64bit. Upon execution, it hangs during interface load, then shuts down. Log file attached. Thanks in advance for any advise.
cura.log

Try running curaengine.exe and then cura.exe … it happened to me in the latest version and I only did it once, then I charge well.

Cesar,

Thank you very much for the quick reply and advise. Unfortunately, it did not fix my problem:

Do you know anything else I might try?

Best Regards,

Bob

have you tried this? it was the best result for me

Hi Cesar,

I was using those settings but they did not get the program to start.

I found my solution. I had to turn on the high performance settings on my NVIDEA graphics processor. Once I did that, it started up properly.

Maybe this info will be helpful to others. Thanks for your help.

Bob

Copy link

Contributor

Author

For me clicking like 20 times on the program eventually opens it, tho honestly i gave up on cura (at least on my personal laptop).

Probably a compatibility issue with the INTEL HD driver. That failed on my LT as well. I also have an INVIDEA GeForce card installed. Enabling 3D acceleration on the GeForce fixed my issue.

Glad you can run with 15.4

As far as we know, this issue is fixed in the 4.5 version. We’ll release a beta today, so feel free to give that a try. It’s a complicated issue since a lot of people are reporting different things under the same denominator.

Copy link

Contributor

Author

Hi Reiner,

I’m not affiliated with Cura; just another user like you. I also happened to have the same issue on my HP Envy LT (for any version up to 4.4.1; haven’t loaded 4.5 beta as yet). What worked for me was to go into the NVidea control panel; Manage 3D Settings and select High-performance NVIDIA processor as the preferred graphics processor on the Global Setting tab. Auto-select will default to integrated graphics and GUI load will fail. Apparently the imbedded graphics processor is not up to the task.

Hope this helps!

Good luck,

Bob

Copy link

Contributor

Author

@riebuehl there are two things I’d like to ask you to try:

• Update your Intel graphics drivers. I think we’ve probably asked you this before, but a few weeks ago Intel came with an update to their graphics drivers that specifically fixed one of our issues that had this symptom.

• If Cura still doesn’t start after that, kill the process from the task manager and please find the file C:\Users\<riebuehl>\AppData\Roaming\cura\4.5\cura.cfg and open that with a text editor. Under the header [view], add the following line:

  opengl_version_detect = force_modern
  

  Save that file and try starting Cura again. Does it start then?

Copy link

Contributor

Author

@Ghostkeeper Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

Copy link

Contributor

Author

Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

We’ve fixed multiple things in 4.5 that are related to Cura not starting. One of them is the workaround I posted above with force_modern. Related commits are here: Ultimaker/Uranium#565

Hi all,

Cura 4.6.2 on Windows 7 on an HP G72 laptop w/ szitchable GPUs :

• Intel GMA HD (PCI\VEN_8086&DEV_0046&SUBSYS_143A103C&REV_02)
• AMD-ATI Radeon HD 5470 (PCI\VEN_1002&DEV_68E0&SUBSYS_143A103C&REV_00).

Cura wouldn’t even start w/ AMD : process visible a few seconds, then disappears with no log anywhere,

With Intel, it starts but at first click, it hangs w/ standard Windows popup «recherche une solution» («looking for a solution») then «fermer l’application» («close application»).

So for me this software is just useless…

Did you try Windows 8 Compatibility? Or the workaround I mentioned above?

Thanks Ghostkeeper for your answer !

I’ve left the issue for now, got another machine on which Cura works OK and no time to test. This machine is usually on Linux and rarely booted on Windows ^-^ But this week-end I’ll probably have enough time to test both workarounds. I don’t know if there is a W8 compat setting on W7, but I’ll look… but the force_modern workaround seems best bet…