kvm-guest-drivers-windows: SCSI driver broken in recent Windows builds

I reported this issue before ( https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1037 ) but I think its better to start from scratch, because I understand the problem better now.

In recent Windows version, like Windows 11 24H2 (IoT) and Windows Server 2025, there is a new Setup and this one rejects the Virtio SCSI driver (wether it is WHQL signed or not).

It does not reject the driver when you manually browse to it and select it by hand. But in automatic (unattended) installations, where the drivers are loaded from a $WinPEDriver$ folder or from a unattended.xml, it refuses to load the driver.

I spend the whole day trying to debug why this is happening, but I cannot figure it out.

So can please someone of the team look into this? If there is anything I can do to help in diagnosing the issue, please let me know!

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 45 (8 by maintainers)

Most upvoted comments

Problem still present in v0.1.262

@krendahl-godaddy we probably have a similar use case. Why not install from a sata cdrom to a virtio block (or virtio-scsi)? This combination worked for me. I had to limit the drivers I load on Microsoft-Windows-PnpCustomizationsWinPE to an absolute minimum (NetKVM and viostor/virtio-scsi) though. Just install the rest later during the specialization phase with pnputil. Otherwise, the setup fails very early with an error code indicating that the driver trying to load is already loaded. For reference, this worked on Windows 11 24H2 Pro, Education, and Pro Education.

edit: for error code indicating that the driver is already loaded i mean 0x80070103, probably the same one on quickemu issue

Thank you @nyawox your tip was the key for me to get this working. I tried using the virtio-win ISO during virt-install as well as inserting the virtio drivers into both the boot.wim/install.wim in the install src ISO… but neither worked for me. Once i created a custom virtio-win ISO with only the 2k25 netkvm/viostor/vioscsi drivers the unattended install completed successfully (using a sata cdrom for install ISO as well).

It would be nice to not have to jump through hoops and just drop in the latest virtio-win ISO so i’ll be keeping an eye out on this bug for future resolution.

Issue still present in v0.1.266

@kroese Based on experience I don’t think the change in driver code or INF file will fix the issue. Labels can be always changed.

@kroese sorry for delay. it took me a bit longer than I expected. please give a try to https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/upstream-virtio/virtio-win11-attestation-0.1-258.zip it contains Win 11 attestation signed drivers for arm64 and amd64 platforms from the latest internal build (b258).

Best, Vadim.

We have attestation signed drivers targeted to be installed on Win11 24h2 and WS2025 (partially). They are not included in the latest virtio-win package available from fedorapeople site. The reason for that is mainly because our current virtio-win installer in based on dixf framework which is not compatible withe the latest Windows OSes (higher than Win 8.1) . We are working on this issue, but at the moment we cannot build the installer with the latest attestation signed drivers. But I hope we can try sharing those drivers as is, without the installer., for the preview reason only. Let me check this option.

Cheers, Vadim.