Common problems¶

Solutions to the most common situations when launching and running the panel.

GPU not visible in the virtual machine¶

Symptoms: your card isn't listed under devmgmt.msc → Display adapters (only a basic adapter), or VendorID/DeviceID won't detect in the panel settings.

Fix:

Make sure the correct driver version is installed on your main PC (see Step 4).
Power off the VM and run Crux_GPU.bat again, entering the VM name.
Start the VM and check devmgmt.msc once more.

Passthrough won't work without host drivers

If the driver on the main PC is missing or outdated, there's nothing to pass through. Install the driver on the host first, then pass it through.

VendorID / DeviceID won't auto-detect¶

Symptoms: the panel settings show "could not detect - enter manually".

Fix:

The usual cause is the GPU isn't passed through or drivers aren't installed. Check the item above.
If the card is visible in devmgmt.msc but auto-detect failed, press "AUTO-DETECT" again or enter the values manually.

Nvapi file error when launching CS2¶

Symptoms: CS2 won't start and shows an error related to nvapi files.

Fix:

Open File Explorer and go to drive C:.
In the search box (top-right), type nvapi.
Wait for the search to finish and delete all the files it finds - every single one.
Launch CS2 again.

Tip

If the error keeps happening, make sure the GPU drivers are passed through correctly and the recommended driver version for your card is installed.

Black bands on the window background in the VM¶

This isn't a panel bug - it's a quirk of Hyper-V's output in Enhanced Session mode (VMConnect). It doesn't affect anything. If it bothers you, connect to the VM over regular RDP or disable enhanced session.

Didn't find your problem?

Message support - we'll help.