Windows is still setting up the class configuration for this device. (Code 56)

[Honeypie]

Hi,
for 2 days I am trying to install WIN 10 as a virtual machine on Proxmox VE without success. I always get an error in the windows device manager for the network adapter: „Windows is still setting up the class configuration for this device. (Code 56)“ - and the network connection is not working. I checked Google, your forum, YouTube videos and so on. Especially on YouTube I saw a lot of videos, showing how easy this installation should work. I tried exactly the same steps - but didn‘t work.
I am using the newest software versions available:
Proxmox VE 7.1-5
virtio-win-0.1.208.iso
Win10_21H2_German_x64.iso
Network device: VirtIO (paravirtualized)
I tried all available network devices - always the same problem
As the Youtube videos are 6 month or older, I also tried an older Win ISO image, getting the same error.

Everything else works fine - all other driver are OK.
I did not check with an older Proxmox VE version. So I am afraid that the newer Promox VE version produce this problem. Is this possible?
Or is this a known problem with a solution ?
What else could I try ?

 

[ldzielak]

I just updated to VE 7.1.5 and my windows VMs fail to boot and freeze, I'm trying to figure out how to roll back to 7.0.xx once my clone jobs compete I will go back. I tried to spin up a new VM and installer can even locate a valid drive to install. Have a look at the V7.1 release forum, sounds like there is a bug..

 

[Honeypie]

Does it mean, with the newest Proxmox VE 7.1-5 it is not possible to create a Win10 virtual machine with a working network adapter ? Win10 without network and internet does not make much sense to me!?
There must be anybody out there who created a virtual Win10 with the latest Proxmox VE - if so - how to do ?

 

[tom]

As you post in the English forum: just use the English Version of the Win10 ISO, this one is known to work.

(For the German ISO, there are several workarounds. e.g. try to boot with Machine Version to: 5.1. And or search the forum for several other tips)

 

[tom]

I just updated to VE 7.1.5 and my windows VMs fail to boot and freeze, I'm trying to figure out how to roll back to 7.0.xx once my clone jobs compete I will go back. I tried to spin up a new VM and installer can even locate a valid drive to install. Have a look at the V7.1 release forum, sounds like there is a bug..

This another issue, please post your VM settings in a new thread.

 

[Honeypie]

As you post in the English forum: just use the English Version of the Win10 ISO, this one is known to work.

(For the German ISO, there are several workarounds. e.g. try to boot with Machine Version to: 5.1. And or search the forum for several other tips)

I didn‘t know that there is a German Proxmox forum. But your tip was very useful. Thank you. I loaded an English ISO version and installed the virtual machine in about 30 minutes without any problems. Finally I changed the keyboard to German and installed the German Language Pack. All works now !
Finally that means, Proxmox Version 7 does not work well with German WIN ISOs

 

[grand]

Maybe someone else also runs into it....
The error also occurs in the Hungarian version of Windows 10. Ethernet card 56 code - error.
Tested Proxmox 7.1-10 - Win10 21H2 prof. / virtio driver (0.1.171 and 0.1.215 tested) q35 version ( 5.2, 6.0, 6.1) - error occurs

Solution: Machine q35 / version 5.1 (works - no errors).

 

[gk_emmo]

Maybe someone else also runs into it....
The error also occurs in the Hungarian version of Windows 10. Ethernet card 56 code - error.
Tested Proxmox 7.1-10 - Win10 21H2 prof. / virtio driver (0.1.171 and 0.1.215 tested) q35 version ( 5.2, 6.0, 6.1) - error occurs

Solution: Machine q35 / version 5.1 (works - no errors).

Thx m8 After 4 hours of fighting we finally found this thread

 

[Roll-Your-Own]

Maybe someone else also runs into it....
The error also occurs in the Hungarian version of Windows 10. Ethernet card 56 code - error.
Tested Proxmox 7.1-10 - Win10 21H2 prof. / virtio driver (0.1.171 and 0.1.215 tested) q35 version ( 5.2, 6.0, 6.1) - error occurs

Solution: Machine q35 / version 5.1 (works - no errors).

Works for me too - Thank you!!!

 

[RolandK]

please report the problem to microsoft, it would be interesting what they have to tell about that. you may use "feedback hub" and report the link to the feedback-hub issue here.

https://gitlab.com/qemu-project/qemu/-/issues/774

https://github.com/virtio-win/kvm-guest-drivers-windows/issues/745

 

[RolandK]

apparently me ( and others) were wrong, the problem seems to originate in qemu, at least the mentioned git commit is causing issues, see

https://gitlab.com/qemu-project/qemu/-/issues/774#note_1178918198