System's %PATH% is overwrite, micromamba for windows,
Troubleshooting docs
- [X] My problem is not solved in the Troubleshooting docs
Anaconda default channels
- [X] I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Micromamba
Search tried in issue tracker
path
Latest version of Mamba
- [X] My problem is not solved with the latest version
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
System's %PATH% is overwrite, micromamba for windows,
In file _mamba_activate.bat, when @CALL "%_TEMP_SCRIPT_PATH%" is executed, System %PATH% is overwrite. so system's command can't be found.
I made temporary modifications to facilitate correct usage :
@SET OLD_PATH=%PATH%
@CALL "%_TEMP_SCRIPT_PATH%"
@SET PATH=%PATH%;%OLD_PATH%
mamba info / micromamba info
libmamba version : 2.0.0
micromamba version : 2.0.0
curl version : libcurl/8.2.1-DEV Schannel zlib/1.2.13
libarchive version : libarchive 3.6.2 zlib/1.2.13 liblzma/5.4.3 bz2lib/1.0.8 liblz4/1.9.4 libzstd/1.5.5
envs directories : D:\micromamba\envs
package cache : D:\micromamba\pkgs
C:\Users\ctl\.mamba\pkgs
C:\Users\ctl\AppData\Roaming\.mamba\pkgs
environment : None (not found)
env location : -
user config files : C:\Users\ctl\.mambarc
populated config files : C:\Users\ctl\.condarc
virtual packages : __win=10.0.19045=0
__archspec=1=x86_64
__cuda=12.6=0
channels : https://mirrors.ustc.edu.cn/anaconda/pkgs/main/noarch
https://mirrors.ustc.edu.cn/anaconda/pkgs/main/win-64
https://mirrors.ustc.edu.cn/anaconda/pkgs/free/noarch
https://mirrors.ustc.edu.cn/anaconda/pkgs/free/win-64
https://mirrors.ustc.edu.cn/anaconda/cloud/conda-forge/noarch
https://mirrors.ustc.edu.cn/anaconda/cloud/conda-forge/win-64
base environment : D:\micromamba
platform : win-64
Logs
..
environment.yml
...
~/.condarc
....
same for me: when I activate an environment, it it now overwriting my path instead of appending to it. This worked fine for me before updating mamba 2.0.0
PS C:\Users\my_username> $env:Path C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\ASCI\ActiveBatchV12\bin;C:\Program Files\ASCI\ActiveBatchV12\bin\Client\Cli;C:\Program Files\Amazon\AWSCLIV2;C:\WINDOWS\System32\OpenSSH;C:\Program Files\dotnet;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Citrix\HDX\bin;C:\Program Files\Citrix\HDX\bin;C:\Program Files\TortoiseGit\bin;C:\Users\my_username\scoop\apps\miktex\current\texmfs\install\miktex\bin\x64;C:\blp\DAPI;C:\blp\DAPI\DDE;C:\Users\my_username\scoop\shims;C:\Users\my_username\AppData\Local\Microsoft\WindowsApps;C:\Users\my_username\AppData\Local\JetBrains\Toolbox\scripts;C:\Users\my_username\AppData\Local\GitHubDesktop\bin;C:\Users\my_username\AppData\Local\Microsoft\WindowsApps;C:\Users\my_username\AppData\Local\Programs\Git\cmd
PS C:\Users\my_username> mamba activate
(base) (base) PS C:\Users\my_username> $env:Path C:\ProgramData\Miniconda3;C:\ProgramData\Miniconda3\Library\mingw-w64\bin;C:\ProgramData\Miniconda3\Library\usr\bin;C:\ProgramData\Miniconda3\Library\bin;C:\ProgramData\Miniconda3\Scripts;C:\ProgramData\Miniconda3\bin;C:\ProgramData\Miniconda3\condabin
2.0.0, 2.0.1 have the same issue, simple change micromamba.exe back to version 1.5.6, work fine
The problem has been addressed in mamba 2.0.2, can you confirm it fixes your issue?
The problem has been addressed in mamba 2.0.2, can you confirm it fixes your issue?
Looks fixed for me with mamba 2.0.2. Thank you