SOLVED CURA 4.4.0 freezes on startup at Loading plugins...FIX

[RoboDLC 1]

Tried twice to install 4.4.0 on my Windows 10 home 64 bit laptop.  On startup is freezes at "Loading plugins".  The only way to kill it at this point is through task manager and looking at background processes.  The install never makes it to showing up on the task bar as a running application.  I have installed 4.4 on two other Windows computers (10 Enterprise and 10 Pro) with no issues.

Opened a "cmd" window and started it there on command line.  It came up after noting that Windows Firewall had blocked some of it.  I gave permission for it to run and it started.

 

Now it starts from the icon.

 

FYI,

DLC

[OUPS65 3]

Tks, @RoboDLC

What I made, based on your suggestion:

norton -> pare feu -> controle programme -> ajouter ( add a new programme autorisation) -> selected CURA 4.4.0 and gave full autorisation.

Now, the problem is solved.

[territerriterri 10]

Hey @RoboDLC  thank you for reporting this. I'm not sure if the firewall rules should matter - some times during testing, we choose cancel on that Windows Firewall prompt... and it still works without the getting blocked on the splash page. 

 

and @OUPS65, interesting to know this for us. I'll keep a note of it so we can include in our test it next time. 

 

[RoboDLC 1]

You're welcome!  We can't always just complain you know.  😀

 

DLC

[foggy 0]

I just ran into same issue.  I got a new windows 10 PC and installed to use.  It got stuck on loading plugins. Found this post and manually added Cura to the firewall exception list and all was well.

[ximon 0]

I had the same issue on two machines, i had to add curaengine.exe as well as cura.exe to the firewall exceptions before it would load.

[RoboDLC 1]

So, is CURA doing something new or is Windows firewall becoming more effective in blocking snoopware?

 

DLC

[ljexperiments 0]

I also had Cura stop working today.  It did work for 5 days, however today stopped on Windows 10 system-it too hung up on loading plugins.  I tried with and without firewall on.  Perhaps I will look into adding the exceptions.  Any other ideas welcome.

 

 

[ximon 0]

Strangely enough, it didn't work when I turned the firewall off, only when I allowed both .exes through. It may work with only curaengine.exe in the exceptions, as that's the one that's trying to open the port.

[ljexperiments 0]

I allowed both and I get as far as "loading preferences".  What bums me out is it worked for days and then stopped.   I have uninstalled and reinstalled a few times with fingers crossed but, no good...

[V1pr 0]

Had the same problem. After some investigation (like event log) I figured out that I had to add Cura.exe and CuraEngine.exe to the Windows Defender exceptions... after doing so cura 4.4.1 started up ok.

[ljexperiments 0]

Thank you for the feedback, I had to run the compatibility troubleshooter and it has recommended Windows 8 compatibility.

 

I ran compatibility troubleshooter on it and it fixed it.  Hopefully there are no drawback to running in Windows 8 compatibility...

 

I am not sure why it stopped, but it may have been a result of a Windows update...  

[damenzijlstra 1]

Same issue here. I use Cura 4.4.1. on two w10 laptops. An old one and it works fine, but on a new freshly installed Lenovo Yoga it also freezes on startup schreen. Adding cura.exe and curaengine.exe to the firewall settings diddn't solve the issue. Running cura.exe in W8 compatibility mode solved the issue

Edited January 4, 2020 by damenzijlstra

[damenzijlstra 1]

Later i discovered that you have to also allow Cura and Curaengine to public networks in the firewall settings and then it also solves the issue

[toml 0]

Alllowing public networks works for me (after restart of the computer)  Thanks!!!

Edited January 19, 2020 by toml

[ChristoCura 0]

Windows 8 compatibility nor firewall settings fixed my issue with 4.6.  I accepted to update to 4.8 when I started it today (after several months).  That started the problem. Now I have tried 4.6, 4.7 and 4.8.  None worked now.  I should have left it alone....

[Infowire 0]

does this happen in the current version?