Error: Activating Python 3.6.5 64-bit ('base': conda) to run Jupyter failed with Error: spawn cmd ENOENT.

[MuSamiNaf]

Bug: Error: Activating Python 3.6.5 64-bit ('base': conda) to run Jupyter failed with Error: spawn cmd ENOENT.

Steps to cause the bug to occur

1. Open or Create a new IPYNB file.
2. Run Cell

Actual behavior

Error: Activating Python 3.6.5 64-bit ('base': conda) to run Jupyter failed with Error: spawn cmd ENOENT.

GIF:

Expected behavior

The cell to run and display a correct output.

Your Jupyter and/or Python environment

Please provide as much info as you readily know

• Jupyter server running: Local
• Extension version: 2020.1.55524-dev
• VS Code version: 1.41.1
• Setting python.jediEnabled: false
• Python and/or Anaconda version: 3.6.5
• OS: Windows 10
• Virtual environment: conda

Developer Tools Console Output

https://pastebin.com/rQf1DzRX

VSCode Settings

{
    "python.pythonPath": "C:\\Users\\AtOmiC.ADMINRG-7UQ6VS4\\Anaconda3\\python.exe",
	"terminal.integrated.env.windows": {
	"PATH": ""},
}

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

[rchiodo]

Does your python path actually exist? It looks like it's saying otherwise, although I'm not positive it's this path:

C:\\Users\\AtOmiC.ADMINRG-7UQ6VS4\\Anaconda3\\python.exe

[MuSamiNaf]

Does your python path actually exist? It looks like it's saying otherwise, although I'm not positive it's this path:

C:\\Users\\AtOmiC.ADMINRG-7UQ6VS4\\Anaconda3\\python.exe

Yes. It exists since I have no problem running .py files.
It is the Anaconda default installation path

[rchiodo]

Maybe it's this path here:

C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate

The first failure is I believe this one:

[Extension Host] Error Python Extension: 2019-12-20 01:07:28: getActivatedEnvironmentVariables [Error: spawn cmd ENOENT  at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)   at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:84:9)] {  errno: 'ENOENT',  code: 'ENOENT',  syscall: 'spawn cmd',  path: 'cmd',  spawnargs: [    '/d',    '/s',    '/c',    '"C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate && ' +      'conda activate base && echo ' +      "'e8b39361-0157-4923-80e1-22d70d46dee6' && python " +      'c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"'  ],  cmd: 'C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate && ' +    'conda activate base && echo ' +    "'e8b39361-0157-4923-80e1-22d70d46dee6' && python " +    'c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py'}

It looks like it's running the cmd.exe shell with these arguments:

/d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate" && 'conda activate base' && echo "e8b39361-0157-4923-80e1-22d70d46dee6" && python "c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"

If you run just this cmd, what happens?

cmd.exe /d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate"

[MuSamiNaf]

Maybe it's this path here:

C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate

Changing the path to this one makes VSCode asks for Python Interpreter.

The first failure is I believe this one:

[Extension Host] Error Python Extension: 2019-12-20 01:07:28: getActivatedEnvironmentVariables [Error: spawn cmd ENOENT  at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)   at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:84:9)] {  errno: 'ENOENT',  code: 'ENOENT',  syscall: 'spawn cmd',  path: 'cmd',  spawnargs: [    '/d',    '/s',    '/c',    '"C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate && ' +      'conda activate base && echo ' +      "'e8b39361-0157-4923-80e1-22d70d46dee6' && python " +      'c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"'  ],  cmd: 'C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate && ' +    'conda activate base && echo ' +    "'e8b39361-0157-4923-80e1-22d70d46dee6' && python " +    'c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py'}

It looks like it's running the cmd.exe shell with these arguments:

/d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate" && 'conda activate base' && echo "e8b39361-0157-4923-80e1-22d70d46dee6" && python "c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"

If you run just this cmd, what happens?

cmd.exe /d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate"

Nothing happens. No outputs. But this is running directly from CMD (Run as Administrator)

However in the VSCode, The directory is the the user directory in the terminal
PS C:\Users\AtOmiC.ADMINRG-7UQ6VS4>

[rchiodo]

I guess the next thing to try is to add more to that command until it fails.

Meaning add the other arguments in too:

cmd.exe /d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate" && 'conda activate base' && 'echo "e8b39361-0157-4923-80e1-22d70d46dee6"' && 'python "c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"'

[MuSamiNaf]

cmd.exe /d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate" && 'conda activate base'

Output:
''conda' is not recognized as an internal or external command, operable program or batch file.

However, if I removed the single quotation marks around 'conda activate base'
the output is

(base) C:\WINDOWS\system32> and a blinking cursor waiting for input

All these tests are directly run from cmd.exe

EDIT:
Trying this directly from the cmd,exe after removing all the single quotation around the commands
cmd.exe /d /s /c "C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate" && conda activate base && echo "e8b39361-0157-4923-80e1-22d70d46dee6" && python "c:/Users/AtOmiC.ADMINRG-7UQ6VS4/.vscode/extensions/ms-python.python-2020.1.55524-dev/pythonFiles/printEnvVariables.py"

Output:
{"ALLUSERSPROFILE": "C:\\ProgramData", "APPDATA": "C:\\Users\\AtOmiC.ADMINRG-7UQ6VS4\\AppData\\Roaming", "CLASSPATH": "D:\\3-WEKA\\Weka-3-6\\libsvm-3.23\\java\\libsvm.jar", "COMMONPROGRAMFILES": "C:\\Program Files\\Common Files", "COMMONPROGRAMFILES(X86)": "C:\\Program Files (x86)\\Common Files", "COMMONPROGRAMW6432":........<the rest of the data is terminated

I terminated the rest of the output just for privacy reasons

[rchiodo]

So you're saying it didn't fail?

[MuSamiNaf]

Yes it didn't fail...No error messages are there. It just displayed lots of directories, folders and paths

[rchiodo]

Can you run a python terminal from within VS code?

[MuSamiNaf]

Can you run a python terminal from within VS code?

Ctrl + Shift + P and Python: Create Terminal

Output

Microsoft Windows [Version 10.0.18362.535]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\AtOmiC.ADMINRG-7UQ6VS4>C:/Users/AtOmiC.ADMINRG-7UQ6VS4/Anaconda3/Scripts/activate

(base) C:\Users\AtOmiC.ADMINRG-7UQ6VS4>conda activate base

(base) C:\Users\AtOmiC.ADMINRG-7UQ6VS4>

[MuSamiNaf]

Alright. I solved the problem, It is related to the Environment Variables Path.
%SystemRoot%\system32 was missing into the PATH variables for the user.
I added %SystemRoot%\system32 to the PATH variable and moved it to the top of the list.
No errors, correct output.

Thanks @rchiodo for your support.