[GH-ISSUE #5343] [BUG]: ALLM takes 2-3 minutes to start if systray program is no longer running #5031

Closed
opened 2026-06-05 14:51:37 -04:00 by yindo · 3 comments
Owner

Originally created by @bulrush15 on GitHub (Apr 3, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5343

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I have AnythingLLM v1.11.2 on Windows 11.

ALLM takes 2-4 minutes to start, or won't start at all, if I quit the program and then close the systray app.

Are there known steps to reproduce?

  1. Reboot PC for a fresh start.
  2. Start ALLM. I double click on the ALLM icon I have. There are no parameters on the command line of the icon. You don't have to do anything.
  3. Quit the ALLM Desktop app by hitting the "X" in the upper right corner of the ALLM window. Now go to the systray, right-click ALLM, and quit that program.
  4. Double click on the ALLM icon to start it.

ALLM might take 5 minutes to start or more, or may not restart at all.

Suggestion: If the systray program is not running then ALLM should fail gracefully. Possibly have the option (in settings) to reduce the timeout to 1 minute or less. Make the timeout in seconds.

Originally created by @bulrush15 on GitHub (Apr 3, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5343 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I have AnythingLLM v1.11.2 on Windows 11. ALLM takes 2-4 minutes to start, or won't start at all, if I quit the program and then close the systray app. ### Are there known steps to reproduce? 1. Reboot PC for a fresh start. 2. Start ALLM. I double click on the ALLM icon I have. There are no parameters on the command line of the icon. You don't have to do anything. 3. Quit the ALLM Desktop app by hitting the "X" in the upper right corner of the ALLM window. Now go to the systray, right-click ALLM, and quit that program. 4. Double click on the ALLM icon to start it. ALLM might take 5 minutes to start or more, or may not restart at all. Suggestion: If the systray program is not running then ALLM should fail gracefully. Possibly have the option (in settings) to reduce the timeout to 1 minute or less. Make the timeout in seconds.
yindo added the possible bugneeds info / can't replicateDesktop labels 2026-06-05 14:51:37 -04:00
yindo closed this issue 2026-06-05 14:51:37 -04:00
Author
Owner

@timothycarambat commented on GitHub (Apr 3, 2026):

I am not replicating this issue - is this on Linux or something?

<!-- gh-comment-id:4184505001 --> @timothycarambat commented on GitHub (Apr 3, 2026): I am not replicating this issue - is this on Linux or something?
Author
Owner

@bulrush15 commented on GitHub (Apr 5, 2026):

I am not replicating this issue - is this on Linux or something?

It's on Windows 11 25H2.

<!-- gh-comment-id:4189263400 --> @bulrush15 commented on GitHub (Apr 5, 2026): > I am not replicating this issue - is this on Linux or something? It's on Windows 11 25H2.
Author
Owner

@bulrush15 commented on GitHub (Apr 6, 2026):

The problem was caused by Nvidia Game drivers from March 2 2026. This was fixed with Nvidia game drivers of March 24, 2026 which are version 595.97 which were installed today. This has been confirmed to be an Nvidia driver issue. This bug is no longer there.

No CUDA settings were found or adjusted. I'm guessing CUDA is on by default.

<!-- gh-comment-id:4194137132 --> @bulrush15 commented on GitHub (Apr 6, 2026): The problem was caused by Nvidia Game drivers from March 2 2026. This was fixed with Nvidia game drivers of March 24, 2026 which are version 595.97 which were installed today. This has been confirmed to be an Nvidia driver issue. This bug is no longer there. No CUDA settings were found or adjusted. I'm guessing CUDA is on by default.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5031