-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCSI CD-ROM driver broken in recent Windows builds #1100
Comments
I just tried it with the WHQL drivers, but the issue stays the same, so maybe its not related to signatures or certificates after all? It is possible that they changed the way how you must slipstream drivers into an ISO, but it has worked in this manner from Vista all the way up to Windows 11, so I would be highly surprised if they suddenly changed that. |
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, |
@vrozenfe Hi Vadim, that is great news!! I am not using the installer at all, so if I can preview these drivers from a .zip file I would be very happy! |
@vrozenfe Is there any news already? |
@kroese Best, |
@vrozenfe Thank you Vadim, unfortunately it makes no difference for the issue. The scsi driver fails to be automaticly loaded in both 2025 and 24H2, and when loading it manually I get:
Under previous Windows 11 versions they work fine. |
Does it happen during fresh install or the driver update? Thanks, |
@vrozenfe During fresh install. The commandline is:
|
Upon further testing I discovered something interesting... As said before, the BUT when changing that folders name to something random, for example That did not work with the official But my main goal is to slipstream the drivers into the ISO, like I always did before, and that still fails. |
@vrozenfe I tried to debug the issue with the Windows 11 24H2 Setup a bit further, by inspecting the There are no obvious errors about why it ignores the
So no errors at all or a clue why it is not loading the driver. Except for one message that might be relevant (or not):
Then when manually installing the
but then the problems starts:
From what I can find, this error code means that it cannot install the driver because it already exists (which is true, as it should already have been installed automaticly, but was ignored). So its a still a mystery for me, my best guess as to what is happening: maybe Microsoft made a change in 24H2 to only allow boot-critical drivers to be loaded during WinPE, and the |
@kroese Thanks, |
@vrozenfe Im working on an unattend install. I use the VirtIO drivers in my project: https://github.com/dockur/windows As you can see it has unattended installs for the VirtIO drivers for EVERY Windows version (XP/Vista/Win7/Win8/Win10/11) and every Windows Server version (2003/2008/2012/2016/2019/2022), so I did this many times before. Exactly the same steps work fine for Win11 22H2/23H2 and every version below it. |
@kostyanf14 There are multiple ways to inject the drivers, so I am curious which one you are using? Via the Because those both fail in my case. The only method I haven't tried is via the DISM tools So I am very curious, because I have been struggling with this for weeks now, so I am very surprised you made it work? |
We used |
@kostyanf14 Yes, that is the same way as I am doing it. And if I just switch the ISO between 23H2 and 24H2 (and keep everything else the same) it stops working in my case. What are the contents in |
@kroese I tested with WHQLed drivers instead of the attestation signed, but yes just extracted the content of ISO. |
@kostyanf14 Are you sure you are a SCSI drives (and a SCSI CD-ROM for the Windows ISO)? Because I can make the unattended install work with the |
@kroese checking right now with Windows11_InsiderPreview_Client_x64_en-us_26100.iso and virtio-win11-attestation-0.1-258.zip |
@kroese Works. Install QEMU CLI:
Device: |
@kostyanf14 I think i FINALLY found it.. In your config you are installing Windows from a I have always been installing Windows from a So the next question is: why does Windows suddenly refuses to load the |
yes, and then boot from the same QCOW2 but switch the device to vioscsi
No idea. This is a question to Microsoft. |
To summarize the findings.. In 24H2 and Server 2025: You can do a manual install from a I am not sure if this is a bug in the |
In my tests, I don't see any problem because you need CDROM only during the installation process. |
@kostyanf14 I know, but as the read speeds for paravirtualized But I never benchmarked it to be honest, so big chance that the installation speed will be bottlenecked by something else (the write speeds to the disk for example), and there will be no measurable difference in real-life.
I am really not sure if this issue can be blamed purely on Microsoft. Because there are at least 3 other drivers from So it looks more like a compatibility problem which can only be solved by the |
Please test this with |
@kostyanf14 Also with |
@YanVugenfirer Can you explain a bit why you applied the "Not virtio-win" label? All we know until now is that Windows rejects the |
@kroese Based on experience I don't think the change in driver code or INF file will fix the issue. |
Seems to be fixed in v0.1.262 |
I reported this issue before ( #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 aunattended.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!
The text was updated successfully, but these errors were encountered: