[SOLVED] Windows VirtIO Drivers 0.1.173-5 MSI Setup failed / Windows 10 Pro Version 1909

[Semmo]

I installed a VM with Windows 10 Pro 1909 like mentioned in the best practices here: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

I downloaded the ISO for the windows virtio drivers version 0.1.173-5 (latest) but i can not complete the msi installer. It does a rollback and in the MSI log it's the error 1603. I Already activated Test Mode in Windows with BCDEDIT but can still not complete the setup (i also did a fresh install, activated test mode first and then tried the MSI installer)

Has anyone successfully installed the virtio drivers with the MSI in Windows 10 or has some hints for me? I don't know what I could try next.

I will update this post with a logfile soon.

 

[Semmo]

I tried the version "0.1.173-2" and it worked. So maybe version 0.1.173-5 is just buggy.

 

[MarcoP]

0.1.173-4 is also fine

 

[tom]

latest 0.1.173-6 seems to work again.

https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.173-6/

 

[Semmo]

@MarcoP & @tom Thank you!

 

[davleema]

Latest 0.1.173-7 iso is still not working on Win10 1909 x64. Failed to start services when running x64 msi installer...

 

[tom]

Latest 0.1.173-7 iso is still not working on Win10 1909 x64. Failed to start services when running x64 msi installer...

I just did a fresh ISO install from Win10 1909. The MSI installer from 173-7 ISO just worked for me.

Please post your VM config:

qm config VMID

 

[davleema]

balloon: 1056
bootdisk: virtio0
cores: 3
description: Win10 x64 Ent 1909
ide0: none,media=cdrom
keyboard: fr-be
memory: 3875
name: Win10-Test-VM3
net0: e1000=3A9:9B:7E:F3C,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=a2019498-3ee2-45b7-817a-bec11e58d640
sockets: 1
virtio0: local:106/vm-106-disk-1.qcow2,size=105G

 

[davleema]

This Win10 VM is version 1909 x64 Enterprise, it is domain joined. The installer starts but fails when starting services, and then complains about insufficient admin privileges. Even though it asked for and got admin rights at the start of the installation.

 

[tom]

So a permission issue? Try to login as local admin and run the installer again.

 

[davleema]

logged in as local administrator, doesn't help either. The installer still fails at "starting vdservice". Windows event log doesn't clarify why the msi fails.

 

[tom]

balloon: 1056
bootdisk: virtio0
cores: 3
description: Win10 x64 Ent 1909
ide0: none,media=cdrom
keyboard: fr-be
memory: 3875
name: Win10-Test-VM3
net0: e1000=3A9:9B:7E:F3C,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=a2019498-3ee2-45b7-817a-bec11e58d640
sockets: 1
virtio0: local:106/vm-106-disk-1.qcow2,size=105G

Seems you missed to enable the Qemu Agent in your VM config.

https://pve.proxmox.com/wiki/Qemu-guest-agent

 

[davleema]

Yep, that did it. However, I can't recall having to enable this option with other VM's. I guessed it was set to enabled once the qemu guest tools were installed.