Closed qqii closed 2 years ago
Hi @qqii, are you running the installer on Windows Server 2022?
I've noticed that the virtio-win-drivers-installer/constants.wxi.in
doesn't contain the 2022 version so it runs and succeeds but doesn't install any of the services or files in Program Files (I think it only creates the net folder).
As a UNSAFE workaround for Server 2022 you can change HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName
(see virtio-win-drivers-installer/properties.wxs
) to contain 2019 instead of 2022 and revert it back to the original after installation.
PS. @vrozenfe is it possible to add an installer warning screen notifying the user that the OS is unsupported? Because right now the installation will succeed for Server 2022 but no services will be installed.
Also Win 11 reports itself as Windows 10 in the registry key above, so could the installer have an advanced button where the users could select a suitable version to install (as a drop down menu)?
@milsav92
We are going to add WS2022/Win11 support soon.
Vadim.
Is there a time frame on "soon"? Is that published anywhere?
Not published yet. There is a certain testing and validation process which needs to be completed before releasing the drivers for the new OS version.
You can subscribe yourself to the following bug and watch the progress https://bugzilla.redhat.com/show_bug.cgi?id=1995479
Regards, Vadim.
Yes, I was running Server 2022. As suggested using to 2019 blnsrv.exe
worked, except I copied it to the location manually.
How do I subscribe on bugzilla?
@qqii You should be able to add yourself to CC List on the bug's page. In any case the problem should be fixed in build 215-2. Please visit https://github.com/virtio-win/kvm-guest-drivers-windows/issues/696 for more details.
Vadim.
The installer doesn't seem to copy
blnsrv.exe
or install the Balloon Service.