vscode condaはCommandNotFoundErrorを活性化させます

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If your shell is Bash or a Bourne variant, enable conda for the current user with

$ echo ". C:\Users\user\Anaconda3/etc/profile.d/conda.sh" >> ~/.bashrc
or, for all users, enable conda with

$ sudo ln -s C:\Users\user\Anaconda3/etc/profile.d/conda.sh /etc/profile.d/conda.sh
The options above will permanently enable the 'conda' command, but they do NOT
put conda's base (root) environment on PATH. To do so, run

$ conda activate
in your terminal, or to put the base environment on PATH permanently, run

$ echo "conda activate" >> ~/.bashrc
Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
your ~/.bashrc file. You should manually remove the line that looks like

export PATH="C:\Users\user\Anaconda3/bin:$PATH"
^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^

ターミナルPowerShellのセットを統合した場合、自動的に統合された環境conda端子で活性化することができないため、エラー上記vscodeは、およびWindows 10で、デフォルトでは、端末PowerShellを統合しました

オプション1

個人設定は内部の追加"terminal.integrated.shell.windows": "C:\\Windows\\System32\\cmd.exe"、デフォルトの統合ターミナルを変更します

オプション2

個人設定は内部に追加し"python.terminal.activateEnvironment": false、自動起動環境をキャンセル