[bug]: Launcher takes 5-10 minutes to load (SSD, turned off antivirus software)

[alexwyattdev]

Is there an existing issue for this problem?

• I have searched the existing issues

Operating system

Windows

GPU vendor

Nvidia (CUDA)

GPU model

RTX 4060

GPU VRAM

8GB

Version number

5.10.0

Browser

MS Edge 135.0.3179.73

Python dependencies

No response

What happened

Every time I want to start invokeai with the launcher "Invokeai Community Edition.exe", it takes forever to show up. What is it doing in the background that cannot be done after it popped up?

What you expected to happen

I expected it to take no more than 10s to become visible and usable.

How to reproduce the problem

Shut down all invokeai related processes, and start the exe again.

Additional context

Windows 10 with all updates installed that is available as of 4/17/2025
Intel i4-4700k
32gb memory (~20gb free)
rtx 4060 - 8gb
samsung 880 ssd with about 417gb free

not running anything else, I understand if the extreme slow speed is due to the cpu being the bottleneck, but I would still put all processes after the launcher became visible, so i don't end up clicking on it 2+ times thinking that it did not start

Discord username

No response

[psychedelicious]

Hi, I've transferred this issue to the launcher repo.

The launcher is a very minimal electron app. It should start up in a second or two. I think this is the first report we've had for slow startup times for the launcher.

Things to try:

• Restart the computer.
• Download a fresh launcher exe and run it from the Downloads folder.
• Check the Windows Event Viewer for errors related to the launcher.
• Create a new account on the machine, sign into it and see if the launcher works there.

[alexwyattdev]

Hi,

I have installed it on a completely different PC, Windows 11 - fresh install, i5-14600k - it seems to open up faster than on my other pc, but still takes about 2 minutes. I did not see any event viewer logs that would be warning/error related to invokeai.

[psychedelicious]

Maybe it's a network issue. Can you try with networking disabled and also connected to an entirely different network (e.g. mobile hotspot)?