Cannot install windows 10 drivers cause they're unsigned

[whateveruser]

Online I've found lots of similar issues, but no solution untill now.

windows does not recognize the drivers, and so the virtuaio drivers are needed, but then putting those inside, they're not accepted as they're not signed



There was some old guide about placing the correct drivers within the iso itself, and so its recognized,
but, it talks about a specific driver for windows 10, which I cannot find within the Fedora root containing all virt-something driver versions (which btw, aside from name coding, I see no way to tell what is what)

any help ?

 

[Impact]

I can't read that. Please explain exactly what you did and share qm config VMIDHERE.
I'd generally recommend to stick to this: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

 

[MarkusKo]

Alternatively you can use an sata controller to install the windows vm, shutdown vm, then add another 1GB hard disk with scsi single controller, start vm, install the virtio guest tools in windows, shutdown vm, change windows hdd to scsi single controller and remove the 1GB hdd, start vm.

 

[whateveruser]

I can't read that. Please explain exactly what you did and share qm config VMIDHERE.
I'd generally recommend to stick to this: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

it says that it could not find signed drivers. Check if the selected media has the correct drivers and then press ok
(Broad translation, I'm not sure about how the actual translation is, English is actually better, but for this installation I need it in italian...)
So it's refusing the drivers for the disk, as they are unsigned

The os is a w10
About the config vmi:

 

[leesteken]

The name of the ISO in the VM configuration is slightly different from the name of the ISO on the website. Where did you download it from? Did you or someone else change the contents?

EDIT: My Windows knowledge is happily declining but I did install such drivers without any issue on (an English) trial Windows 10 in the past.

 

[whateveruser]

The name of the ISO in the VM configuration is slightly different from the name of the ISO on the website. Where did you download it from? Did you or someone else change the contents?

I got through the parent directory, and tried out with different isos, in the hope of a fix.
Can't remember exactly the full path
I just tried with those other isos that you did link, but yet I have the same issue

I've found also:
https://learn.microsoft.com/en-us/w...n-unsigned-driver-during-development-and-test
supposedly changing a registry key would force windows to accept unsigned drivers, so i launched:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\CI" /v DebugFlags /t REG_DWORD /d 0x1 /f

But windows still requires signed drivers

 

[janus57]

Hi,

What happened if you manually add the virtio iso driver as a second CD/DVD and try to load from that ?

Best regards,

 

[whateveruser]

Hi,

What happened if you manually add the virtio iso driver as a second CD/DVD and try to load from that ?

Best regards,

that's what already happens, but if I add a third driver, it still refuses

 

[_gabriel]

Do you select subfolder amd64 ?
or vioscsi\w10\amd64 ?

 

[janus57]

Hi,

It's working on my side with fresh Win10 ISO (from Microsoft), and the latest VirtIO drivers (from : https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.271-1/).
I just have to look in the amd64 -> w10 folder inside the VirtIO drivers iso.

Here are some screenshots.

Config :


Locating drivers :

Driver installing by Windows Setup :


Drive available after driver installations :


Best regards,

 

[whateveruser]

Hi,

It's working on my side with fresh Win10 ISO (from Microsoft), and the latest VirtIO drivers (from : https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.271-1/).
I just have to look in the amd64 -> w10 folder inside the VirtIO drivers iso.

Here are some screenshots.

Config :
View attachment 88188

Locating drivers : View attachment 88189

Driver installing by Windows Setup :
View attachment 88190

Drive available after driver installations :
View attachment 88191

Best regards,

I was dumb, I just passed on the whole iso, without selecting the right path, thanks