Slow startup on Windows: splash screen appears in more than 20 seconds

Symptoms

  • IDE startup takes more than 20 seconds to show the splash screen for the first time, subsequent start is usually much faster.

  • Antivirus software with the real-time monitor such as Windows Defender is working on the computer.

Cause

Windows Defender slows down IDE startup by scanning its files. The scanning has become much slower recently for the yet unknown reason.

Resolution

Add IDE process to the exclusion list of the installed antivirus. Here are the steps for the Windows Defender:

  1. Go to Start > Settings -> Update & Security -> Virus & threat protection -> Virus & threat protection
  2. Under Virus & threat protection settings select Manage settings
  3. Under Exclusions, select Add or remove exclusions
  4. Select Add exclusion and specify the "idea64.exe" process for IntelliJ IDEA.
Process names to exclude from the antivirus for the other IntelliJ platform based IDEs:
  • webstorm64.exe
  • datagrip64.exe
  • clion64.exe
  • rider64.exe
  • datagrip64.exe
  • goland64.exe
  • phpstorm64.exe
  • pycharm64.exe
  • rubymine64.exe
  • webstorm64.exe
  • studio64.exe
5 comments
Comment actions Permalink

I also needed to add an exclusion for "fsnotifier64.exe" so that the startup-windows (which displays the startup progress bar) showed up. I'm not sure if this further accelarted the start-up performance in total.

Edited by elnecsario
3
Comment actions Permalink

The same exclusion had to be done also in Malwarebytes on Windows. Now it is back to usable again.

Thanks for this tip.

 

0
Comment actions Permalink

Excluding rider64.exe and fsnotifier64.exe didn't help: Windows Defender was still scanning something and it took long for the Rider's splash screen to show up.

The following gist helped and now Rider starts quickly: https://gist.github.com/nerzhulart/89c6a376b521a6e7eb69a04277a9489a

0
Comment actions Permalink

Surely whitelisting these processes leaves you open to anyone just using these process names?

2
Comment actions Permalink

This is hardly a solution and whitelisting processes should be an emergency workaround only.

You should fix whatever is causing this behaviour in the first place, because other, much larger software packages do not run into similar problems.

 

0

Please sign in to leave a comment.

Have more questions?

Submit a request