WSL: Bad Install: Missing 'Validate environment prerequisites' Cuda and Conda (and other) Linux Scripts.

[mattezell]

I installed AI Toolkit in VSCode using the official Extensions installation path.

Version: 1.105.1 (user setup)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Upon running the Validate environment prerequisites helper, I was notified that Conda and Cuda weren't installed - so I clicked the 'Setup WSL Environment' button.

The spawned shell instance pops up a sudo password request (after it seemingly sent a RETRUN twice, so I'm on the 3rd password attempt at this point).

After entering the correct password, the following error pops up in an error modal:

The terminal process "sudo 'bash', '/home/matt/.vscode-server/extensions/ms-windows-ai-studio.windows-ai-studio-0.24.1-linux-x64/bin/Scripts/install_conda.sh'" terminated with exit code: 127.

Then a 2nd sudo password prompt, and the following error:

The terminal process "sudo 'bash', '/home/matt/.vscode-server/extensions/ms-windows-ai-studio.windows-ai-studio-0.24.1-linux-x64/bin/Scripts/nvidia_cuda_install.sh'" terminated with exit code: 100.

Upon closer inspection, I see that '/home/matt/.vscode-server/extensions/ms-windows-ai-studio.windows-ai-studio-0.24.1-linux-x64/bin/Scripts/' doesn't exist, though '/home/matt/.vscode-server/extensions/ms-windows-ai-studio.windows-ai-studio-0.24.1-linux-x64/bin/' does.

(.venv) matt@LEGION5090:~/w/github/claude-cookbooks$ ~/.vscode-server/extensions/ms-windows-ai-studio.windows-ai-studio-0.24.1-linux-x64/bin/
Inference.Service.Agent               WorkspaceAutomation.Agent             libonnxruntime-genai.so               libonnxruntime.so                     libonnxruntime_providers_shared.so    libonnxruntime_providers_tensorrt.so

So I decided to install under VSCode in Windows... And surprisingly, the /bin/Scripts/ folder and script assets are there...

So I created the 'Scripts' folder and copied these scripts into it within WSL - at which time I was able to successfully complete the 'Setup WSL Environment' process without error...