Anaconda Initialization Script Module for PowerShell (Windows)

Conda.psm1

function Initialize-Conda
{
  $CONDA_ROOT_DIR = "C:/path/to/Anaconda" # Change this
  [System.Environment]::SetEnvironmentVariable("CONDA_EXE", "$CONDA_ROOT_DIR/Scripts/conda.exe", [System.EnvironmentVariableTarget]::Process)
  [System.Environment]::SetEnvironmentVariable("_CE_M", "", [System.EnvironmentVariableTarget]::Process)
  [System.Environment]::SetEnvironmentVariable("_CE_CONDA", "", [System.EnvironmentVariableTarget]::Process)
  [System.Environment]::SetEnvironmentVariable("_CONDA_ROOT", "$CONDA_ROOT_DIR", [System.EnvironmentVariableTarget]::Process)
  [System.Environment]::SetEnvironmentVariable("_CONDA_EXE", "$CONDA_ROOT_DIR/Scripts/conda.exe", [System.EnvironmentVariableTarget]::Process)
	
  Import-Module -Scope Global "$Env:_CONDA_ROOT/shell/condabin/Conda.psm1"
  conda activate base
}

ヒーローだよ! 本当に助かた. ありがとうね...

The only thing I had to fix was having the prompt act normally again (with oh-my-posh / posh-git / psreadline). I discovered that it was $Env:_CONDA_ROOT\shell\condabin\Conda.psm1 that was screwing it up, so I commented out lines 268-275, like so...

<#if (Test-Path Function:\prompt) {
    Rename-Item Function:\prompt CondaPromptBackup
} else {
    function CondaPromptBackup() {
        # Restore a basic prompt if the definition is missing.
        "PS $($executionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) ";
    }
}#>

And it finally gave me my prompt back, instead of the otherwise unhelpful PS > prompt.

(Found this from your blog post FYI: https://hideki.hclippr.com/2019/06/09/using-anaconda-from-powershell/)