Installing AI Workbench ends in Preparing installation. This may take a few minutes. Checking bundle for artifacts

[hwulfershb]

Tried to install NVIDA AI Workbench on my Win11 24H2 Notebook several times. The 1st time the installation ends in an application error. After changing the system language from german to english (and uninstalling docker for desktop/wsl subsystem reboot system etc.) installation hangs in “Preparing installation. This may take a few minutes. Checking bundle for artifacts…” - waiting for 2 hours with no result. Repeated the installation several times with the same result.

Best Regards
Holger

My environment:
wsl -l -v

NAME STATE VERSION

• Ubuntu Running 2
  docker-desktop Running 2
  NVIDIA-Workbench Stopped 2

Processor: Intel(R) Core™ Ultra 9 185H 2.50 GHz
Installed RAM: 64,0 GB (63,5 GB usable)

Windows 11 Enterprise
Version 24H2
OS build 26100.2894

GPU: RTX 2000 Ada

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

[twhitehouse]

Hi. Sorry you are having an issue.

Can you get into a terminal for the NVIDIA-Workbench WSL distro and run the following command?

nvwb support create-bundle

If that works, then you will find the zip file in the .nvwb folder in that distro.

Please send it to aiworkbench-support@nvidia.com, and make sure to include a link to this forum post for reference.

[hwulfershb]

Hi,

nvwb support create-bundle ends in -sh: nvwb: not found.

Best Regards

Holger

[twhitehouse]

Got it.

Can you follow the guidance here to get the main.log file?

Don’t post it here.

Instead, send it to aiworkbench-support@nvidia.com.

[hwulfershb]

sent the log to aiworkbench-support@nvidia.com

[twhitehouse]

got it. back at you in a bit.

[twhitehouse]

Ok. Let’s try the following.

• Go into the wsl terminal for NVIDIA-Workbench, which I assume exists because wsl listed it.
• Check if workbench is a user there with: cat /etc/passwd | grep workbench
• Check if the directory ~/.nvwb/bin exists, if it doesn’t then create it with
  • mkdir -p /home/workbench/.nvwb/bin
• Then run the installer again.
• If it fails, send the logs to that email again.

[hwulfershb]

Hi,

there was no user workbench.

Sent the logs again.

Thanks a lot and Best Regards

Holger

[twhitehouse]

Thanks. Will look at them.

What language pack are you using for your Windows OS?

@sophwats for viz.

[hwulfershb]

Hi,

German and US-EN.

[twhitehouse]

are these errors coming with the german or the english language pack, or both?

[hwulfershb]

First tried it with german – no luck. Installer stopped very early. After adding english language pack (and set english as default language – at this time I used both language packs) the installer “hung” a little later. I found that the ext4.vhdx did not have the workbench user configured. The rest are consequential error. Maybe the installer has a problem with the german language.

[twhitehouse]

Yeah. I thought we fixed that.

Let me check with eng to get best path to find the problem.

Back in a bit.

[twhitehouse]

Sorry for taking so long.

Ok. Let’s have you manually create the workbench user and then run the installer again.

• Open a Windows shell and then get into the distro as root with the command wsl -u root -d NVIDIA-Workbench.
  • Make sure to enter as root.
• Then create the workbench user and the /home/workbench/ folder with the command sudo useradd -m -s /bin/bash workbench
• Then make sure the workbench user owns the directory with the command sudo chown -R workbench:workbench /home/workbench
• Then run the installer again.

If it errors, send the logs again.
`

[hwulfershb]

Hi,

it´s working now.

Will there be an official fix available for the installer in the near future?

[twhitehouse]

Ok. Can you clarify if my suggestion fixed it?

We thought we’d fixed it.

Let me talk with engineering to see if we can get it into our testing.

[hwulfershb]

Hi,

your suggestion fixed it.

I think the main problem is the responses to the installation actions, which in my case were not in English and were therefore misinterpreted by the installer (because of the german language package of windows in my case).