[Bug]: No driver found

[ulledamm]

Which OS?

Other..

Which release?

Other..

Describe the bug

After running the new installer, companion app shows "No driver found".

Steps to reproduce

Windows Server 2016 Standard (1607)

Running the new installer (Run as Administrator)

Device Manager:
VirtualDisplayDriver is listed as "unknown device".

"Device status:
The drivers for this device are not installed. (Code 28)

The parameter is incorrect."

Trying to update manually by pointing to C:\VirtualDisplayDriver results in the same error: "The parameter is incorrect."

Expected behavior

Expected a "green" companion app and the option to select VirtualDisplayAdpater in Display Settings.

Log File

No response

Contact Details

[email protected]

[torarnv]

Same issue here. Windows 11 in Parallels VM, arm64.

[w061a09]

same here

[ulledamm]

Same problem on another Server 2016 Standard.

Installs with no issues and runs perfectly fine on Server 2019 Standard.

[kayti]

Windows 2016 is too old. It is based on (1607), Virtual driver needed at least 1809, I think. Server 2019 is based on 1809. From this version windows changed the structure or something of GPU drivers so they are not compatible with older systems.

[torarnv]

But Windows 11 should be modern enough shouldn't it? I'm seeing the same symptoms on a Windows 11 arm64 VM

[zjoasan]

I'm not sure which version of iddcx library is in all of your OperatingSystems. I know we might have had set the bar to high with iddcx version. When it comes to Virtualization, it confuses the driver even in a recent MS(x64) OS.

So in short, it's right now problematic depending of iddcx version in the OS(or the requirement of the driver, which we might have to be altered with an upcoming release).

When it comes to HyperV / Parallels / VM / Virtualbox environments, I just know there are problems, but I'm short on hardware where I can test/diagnose the problem either in code or if it's OS based (iddcx or deps of it)

[Septoleaf]

Same issue on Windows 11 Pro 24H2.
VDD can't find driver when I change installation directory from the installer (example C:\Program Files\VirtualDisplayDriver).
This results in "Unknown device" added to Device Manager and VDD not working (yellow tray icon).

VDD does however find the driver when I don't change installation directory (default is C:\VirtualDisplayDriver).
This results in VDD working, but previous "Unknown device" from failed installations become functional and need to be manually uninstalled from Device Manager otherwise VDD treats them like additional displays.