Description of problem: Installing the VirtIO drivers for Windows 2k12 afterwards fails. The drivers are rejected due to an invalid catalog file. Force-installing the drivers leads to a BSOD. Version-Release number of selected component (if applicable): https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.104-1/virtio-win-0.1.104.iso but also "virtio-win-0.1.103.iso" and "virtio-win-0.1-81.iso How reproducible: Every time Steps to Reproduce: 1. Install Windows 2k12 without VirtIO 2. Add VirtIO HD afterwards 3. Mount ISO and try to install viostor.sys Actual results: Processing inf : vioscsi.inf Adding the driver package failed : The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. Processing inf : viostor.inf Adding the driver package failed : The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. Expected results: Working VirtIO-HD. Additional info: Using the same ISO during the initial install and installing the VirtIO drivers from the beginning works without problems. The Windows installer seems to ignore the signature mismatch that early. Running the following command on 0.1.104 prints (among others) the following sha1hash: > "C:\Program Files (x86)\Windows Kits\8.1\bin\x86\signtool.exe" /verify /v /kp E:\NetKVM\2k12\amd64\netkvm.sys ... > Hash of file (sha1): 135E3AA23217610AEE8046F68550B0BA86F4EAE6 > "C:\Program Files (x86)\Windows Kits\8.1\bin\x86\signtool.exe" /verify /v /kp E:\viostor\2k12\amd64\viostor.sys ... > Hash of file (sha1): EF11F5E539EEE0A9DB6DF3710A0DAA35066C5607 Looking into the corresponding .cat "Security Catalog File" - netkvm.cat contains the above given hash for netkvm.sys, - viostor.cat contains 55FC4DA2EE96ECC3FD4865680436DCDA6B8C6BDD instead! Running "sha1sum" on Linux print some completely different hashes, so I don't know what the Microsoft tool actually hash: > # sha1sum /cdrom/NetKVM/2k12/amd64/netkvm.sys /cdrom/viostor/2k12/amd64/viostor.sys > 1aa91c8e1d7680457d92c1875810a79f68af536d /cdrom/NetKVM/2k12/amd64/netkvm.sys > f39bc2b561091addfcac30e370227c91700d2698 /cdrom/viostor/2k12/amd64/viostor.sys See Bug #1117055 for a similar bug.
Created attachment 1033330 [details] setupapi.setup.log
Created attachment 1033331 [details] setupapi.dev.log
I can install the driver successfully but I think the root cause for reporter is the driver is not digital signed by Redhat ( I can reproduce this) Cloning this bug on RHEL as well
Should be fixed in build 105
Published build 105 now. Phillip please check the latest rpm/iso and reopen if you still have issues