[GH-ISSUE #70] [BUG] ST Launcher warns "MiniConda3 Path not found" even fixing the Path #30

New issue

Open

opened 2026-10-15 18:06:20 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 18:06:20 +00:00

Owner

Originally created by @byslexic on GitHub (Aug 21, 2024).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/70

Environment

🪟 Windows

System

WIndows 10 V 22H2 OC build 19045.4651

Describe the problem

When starting ST Launcher, a brief window pops up prior to the menu:
[WARN] miniconda3 NOT FOUND in PATH: C:\Users\Gamers\miniconda3 etc

I have since fixed this so both the System and User variables PATH now point to the correct folder, C:\Users\main\miniconda3 .
I rebooted Windows.
ST Launcher is still giving the same error with the old Path:
[WARN] miniconda3 NOT FOUND in PATH: C:\Users\Gamers\miniconda3 etc
It appears to not be taking or looking for the current Path.
How do I correct ST Launcher?

Additional info

No response

Please tick the boxes

I have explained the issue clearly, and I included all relevant info
I have checked that this issue hasn't already been raised
I have checked the docs

Originally created by @byslexic on GitHub (Aug 21, 2024). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/70 ### Environment 🪟 Windows ### System WIndows 10 V 22H2 OC build 19045.4651 ### Describe the problem When starting ST Launcher, a brief window pops up prior to the menu: `[WARN] miniconda3 NOT FOUND in PATH: C:\Users\Gamers\miniconda3` etc I have since fixed this so both the System and User variables PATH now point to the correct folder, C:\Users\main\miniconda3 . I rebooted Windows. ST Launcher is still giving the same error with the *old* Path: `[WARN] miniconda3 NOT FOUND in PATH: C:\Users\Gamers\miniconda3` etc It appears to not be taking or looking for the current Path. How do I correct ST Launcher? ### Additional info _No response_ ### Please tick the boxes - [X] I have explained the issue clearly, and I included all relevant info - [X] I have checked that this [issue hasn't already been raised](https://github.com/SillyTavern/SillyTavern/issues?q=is%3Aissue) - [X] I have checked the [docs](https://docs.sillytavern.app/) ![important](https://img.shields.io/badge/Important!-F6094E)

bsakaguchi added the

🐛Bug

🚏 Awaiting User Response

🪟 Windows

labels

2026-10-15 18:06:20 +00:00

bsakaguchi commented

2026-10-15 18:06:21 +00:00

Author

Owner

@deffcolony commented on GitHub (Aug 21, 2024):

Hi @byslexic,

Do not modify the System variables directly, as it can affect the entire system and other users. Instead, it's safer to modify only the User variables, which will apply to your specific user account.

Make sure the following paths exists in the user variables called PATH and please change USERNAME to ur own username

C:\Users\USERNAME\miniconda3
C:\Users\USERNAME\miniconda3\Library\mingw-w64\bin
C:\Users\USERNAME\miniconda3\Library\usr\bin
C:\Users\USERNAME\miniconda3\Library\bin
C:\Users\USERNAME\miniconda3\Scripts

To ensure that the changes take effect, please open a new Command Prompt window (since changes to environment variables are not reflected in existing command prompts) and run the following command to test if miniconda3 is correctly recognized:

conda

If miniconda3 is correctly installed and configured in your User PATH, you should see output from the conda command.

If the issue persists, double-check that you've added the correct path to the User variables and that there are no conflicting paths or old references left in the System variables.

@deffcolony commented on GitHub (Aug 21, 2024): Hi @byslexic, Do **not** modify the System variables directly, as it can affect the entire system and other users. Instead, it's safer to modify only the User variables, which will apply to your specific user account. Make sure the following paths exists in the user variables called PATH and please change USERNAME to ur own username ```shell C:\Users\USERNAME\miniconda3 C:\Users\USERNAME\miniconda3\Library\mingw-w64\bin C:\Users\USERNAME\miniconda3\Library\usr\bin C:\Users\USERNAME\miniconda3\Library\bin C:\Users\USERNAME\miniconda3\Scripts ``` To ensure that the changes take effect, please open a new Command Prompt window (since changes to environment variables are not reflected in existing command prompts) and run the following command to test if miniconda3 is correctly recognized: ```bash conda ``` If miniconda3 is correctly installed and configured in your User PATH, you should see output from the conda command. If the issue persists, double-check that you've added the correct path to the User variables and that there are no conflicting paths or old references left in the System variables.

bsakaguchi commented

2026-10-15 18:06:21 +00:00

Author

Owner

@byslexic commented on GitHub (Aug 26, 2024):

@deffcolony Thank you for the response.
Miniconda3 is installed under another user profile ("Main") than the one that is currently in use ("Gamers").
If I were to change the user variables PATH as you recommend, they would be wrong because the folders do not exist under the user "Gamers" - they only exist in user directory: C:\Users\main\miniconda3 , and the user variable path as it is set is currently correct. This is the situation I described in the first message.

How do you recommend rectifying?

@byslexic commented on GitHub (Aug 26, 2024): @deffcolony Thank you for the response. Miniconda3 is installed under another user profile ("Main") than the one that is currently in use ("Gamers"). If I were to change the user variables PATH as you recommend, they would be wrong because the folders do not exist under the user "Gamers" - they only exist in user directory: `C:\Users\main\miniconda3 `, and the user variable path as it is set is currently correct. This is the situation I described in the first message. How do you recommend rectifying?