Why does MATLAB get stuck in the "Initializing" or "Busy" state or take a long time to start?

Not so much a question as as add to another post (that I dont have enough reputation points to post to). If someone can add this to that post, I feel like it would be helpful.

This post was helpfull to me, untill last time it didn't fix the issue. https://www.mathworks.com/matlabcentral/answers/92566-why-does-matlab-get-stuck-in-the-initializing-or-busy-state-or-take-a-long-time-to-start

After reaching out to Matlab Support I was able to get Matalb working again. This is the fix they provided me:

Thank you for contacting MathWorks Support.

This could be an uncommon issue with MATLAB connecting with the default printer driver, which can cause MATLAB to be stuck in Initializing for an extended period of time.

Slow initialization between "init desktop" and "psParser" phases has been known to be caused by a slow connection between MATLAB and the default printer. If this is the root cause, then the following workarounds are available:

A) Set your default printer to "Print to PDF", then see if the issue is resolved.

The link below is a guide from Microsoft to change the default printer.

https://support.microsoft.com/en-us/windows/set-a-default-printer-in-windows-e10cf8b8-e596-b102-bf84-c41022b5036f#ID0EBF=Windows_10

B) If you have printers on your network that you are connected to, check to see if temporarily removing or disabling these devices helps.

Hope this helps someone.

[Yangyuan]

work for me. Thanks

[Image Analyst]

Thanks for following up - it may help others. I added a link to your post here as an answer to that Mathworks tech support posting that you mentioned.

[Dongyue]

Worked for me. Many thanks.

[Thomas Rutten]

Thank you, this was exactly how my problem is solved after having Matlab initializing all the time withour stating up anymore. The problem was a network printer?

Thank you

[Ethan Wright]

@Thomas Rutten, glad to hear! In our case it was a network printer cuasing the issue. I assume due to the system not being able to communicate to it a timely fasion, or maybe just not readding the driver properly. (unsure really why) but it works!! So that's good enough for me.

Cheers,