Installation Error on WSL activation

[tade]

If you are reporting a bug or error, consider submitting a Support Bundle to aiworkbench-ea@nvidia.com. This will help us solve your issue more quickly.

Please describe your issue or request: (tick the boxes after creating this topic):
Unfortunately the installation of the AI Workbench results in an Application Error.
I have WSL2 installed and use it regularly. However, the installation wants to activate WSL2 again and does fail. Is it possible to skip the WSL activation?

main.log (22.1 KB)

Please tick the appropriate box to help us categorize your post
Bug or Error
Feature Request
Documentation Issue
Other

[twhitehouse]

Hi Tade.

WSL2 is a requirement on Windows, so there’s no getting around it.

However, looking at the logfile it seems that you just need to configure your virtualization settings and you should be OK.

The last lines are:
2025-02-12 19:47:20.275] [info] (install-wsl2) stderr [2025-02-12 19:47:20.275] [error] (install-wsl2) Could not update Windows Features. Manually enabling 'Virtual Machine Platform' and 'Windows Subsystem for Linux' via Windows Features and then rebooting your machine may resolve the issue. [2025-02-12 19:47:20.275] [info] (install-wsl2-channel) { error: null, success: false } [2025-02-12 19:47:20.276] [info] (renderer) Navigating to app-error, /progress-wsl2-install

I think your situation should get resolved if you follow the troubleshooting guidance here: Troubleshoot AI Workbench — NVIDIA AI Workbench User Guide

[tade]

Hi,

Thanks, but I’ve read the Troubleshoot and it didn’t help.
Again, I have WSL2 installed, but I think the installer does not recognice it correctly maybe.
Right before the error, it says that everything was activated (in german)… Then it just fails…

[twhitehouse]

Did you upgrade your WSL2 from a previous WSL?

[tade]

I am not sure anymore. It is possible that I accidently installed WSL and then upgraded, when I first installed WSL back then.
If so, would it require me to install WSL2 clean from scratch?

[twhitehouse]

I’m guessing that’s the case because it’s the major situation where we are still seeing weird behavior with WSL.

Can you please do the following?

• Open a windows shell
• Run systeminfo
• Find the section corresponding to Hyper-V Requirements
• Copy the section and paste it into a reply to this message.

[tade]

Ah yes, I already did that but was not aware what it means…
Original German:

Anforderungen für Hyper-V: Es wurde ein Hypervisor erkannt. Features, die für Hyper-V erforderlich sind, werden nicht angezeigt.

English:

Hyper-V Requirements: A hypervisor was detected. Features required by Hyper-V are not displayed.

Additional info:
The Hyper-V Windows Feature is not activated

[twhitehouse]

Ok.

Let’s try the following.

• Go to Windows Features and disable Hyper V
• Verify that Virtual Machine Platform is enabled
• Restart your system and enter BIOS/UEFI to verify/enable virtualization
  • Do this by pressing the correct key, F2 or F10 or something like that right after turning it on
  • Find the virtualization setting and make sure it’s enabled. It may be under “Advanced Settings” in BIOS.
• When you restart, go back and enable Hyper V and reboot.
• Run the installer again.

[tade]

Unfortunately, this did not change anything.

• Bios virtualization is on
• Hyper-V is now also enabled
• VM-Plattform is enabled
• Windows-Subsystem for Linux is enabled

Installer behaves the same. WSL is not detected and the installer wants to activate it and still runs into the same error. Log output is exactely the same.

[tade]

I also now uninstalled WSL deactivated everything and even now I run into the exact same issue…

[twhitehouse]

what language pack is your windows system?

[tade]

german

[tade]

I think this is it. I now changed my language pack to english and the installation already detects WSL correctly and starts downloading the WSL distribution.
It seems for now the installer only works for a english system!

[sophwats]

Woah! Well, I’m pleased it is now working @tade. We will investigage this ‘only installing in engliosh systems’ now - thanks for bringing this to our attention! cc. @twhitehouse

[twhitehouse]

@tade - It’s supposed to work with German. We added non-english language pack support a while back.

This is a bug that we need to fix.

I will raise this to the engineering team and get back to you.

[tade]

yes, that’s what I would have expected. Anyway, for now I have a workaround and can try workbench AI.
Thanks for the hint!