Vadim Rozenfeld

Build 195 (Dec 19, 2019) was the last published build that contains WinXP/WS2003 and Winn7 binaries. Since that point those targets were exuded from our regular builds. However, if your...

msi installers and package bundle are designed to work for Win8/WS2012(R2) and Win10/WS2016/2019 only. On previous versions you need to install the drivers manually.

@crobinso https://github.com/virtio-win/virtio-win-pkg-scripts/commit/7a97bab227aa98a6898142833ae1debca5eea22a Speaking about possible changes in RHEL/Fedora spec files, I have to say that after Feb 22nd the entire cross-signing procedure that we use for signing upstream virtio-win drivers...

@Doud-FR Let me reproduce and check this issue. Thanks, Vadim.

> Thanks! If you need another logs i can give you... Yes, please. It would be helpful. Thanks, Vadim.

@Doud-FR It will be nice if you can post the setupapi log file https://docs.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-device-installation-log-entries Best, Vadim.

@Doud-FR Thanks a lot. Give me some time to sort it out. Best, Vadim.

@Doud-FR Unfortunately, I was not able to reproduce this issue on my setups. Was it the first try to install 221 drivers on your system? There one thing that looks...

@dmachaj You are right. Unfortunately, the RH signature is expired and we can not use it anymore for the driver signing purpose. The good thing is that this problem should...

Try pointing to the exact location. For example /amd64/2k8R2/ ,or viostor/2k8/amd64/ (use the correct driver name that you need, instead of viostor)