No Network Adapter in fresh Windows Server after Upgrade to Proxmox 7

Dec 2, 2021
1
0
1
41
What works for me while using German versions:

- setting VM hardware to Q35 v6.0
- install of Windows Server as usual (load drivers from the second ISO/DVD virtual io 208)
- install qemu-agent and missing drivers after first boot to desktop
- shut down the VM and change VM hardware to Q35 v6.1
Thx, worked for me...
 

Alb

Member
Jul 18, 2019
1
0
6
49
Hy

we also have the same problem with german win 2k19 u 2k16.

A quick and dirty workaround ist the following. I will try to test more and make the workarount more efficient.
(Maybe its better delete the Nic from Hardware, install the driver, add device and start installation)

* Boot VM with Default (i440fx) 6.0
* Add the Attached 2 Regkeys to registry (Maybe ist better to User Current Control Set)
* install the driver: Pnputil /add-driver d:\netkvm\2k19\amd64\netkmv.inf /install
* reboot the server, maybe use "Stop"
* after Reboot, uninstall the VirtIO Nic if ErrorCode 56 is present
* Install Nic with "Automatisch nach aktualisierter Treibersoftware suchen"

Hope this can help

The Regkeys in the Attaches iso, delete the txt extension


kr
Roland
Above I underlined the parts from @ciRoland 's help that fixed the issue for me - after switching settings back and forth multiple times and hoping for Windows 10 with error code 56 to sort itself out - I just removed all NICs from within Windows Driver Manager / Gerätemanager, let Windows search for them and voila, to my surprise they were fully working after Windows reinstalled the NICs.
I didn't think that it was that easy, so make sure that you try that approach rather than fiddling around with other settings.

After you've successfully got your NIC working, you can replicate the problem by changing the NIC type: The code 56 error reappeared for me and the above will fix the problem again.

When this worked for me, I was on i440fx and 6.0, UEFI bios
 
Last edited:
Mar 30, 2020
94
11
13
42
Hy

Seems my fix only works for Windows Server 2019,
Last week we tried to migrate some Server 2016 from ESXi to PVE 7, the solution from SebastianH81 was ok for us

Think isn't a driver bug because we have the same behavior with E1000 Nic.
If we use the i440fs chipset, no eth nics availibe under ncpa.cpl (Networkkard-Configuration)

Mybe the problem is sitting on chipset-implementation. But this is only a suspicion by myself.
 

lps90

Member
May 21, 2020
168
6
23
works for me, just installed a fresh win2016 from ISO on latest Proxmox VE 7.0
Try it in latest version ;)
The v7.0 and v7.1-7 it works with no problems, but the latest v7.1-8 is with problems withh LXC and VM's ;)
My VM's are always stopping after some hours and the syslog shows:
"Dec 13 20:38:25 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:38:44 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:03 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:22 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:41 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:00 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:19 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:38 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:57 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:16 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:35 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:54 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:13 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:32 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:51 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:43:10 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout"
 

remedien

New Member
Dec 14, 2021
1
0
1
45
I've installed in english and after installing driver I changed region language to german.
Thanks for your comments here, it's very helpful
 

Deleted member 116138

Guest
Try it in latest version ;)
The v7.0 and v7.1-7 it works with no problems, but the latest v7.1-8 is with problems withh LXC and VM's ;)
My VM's are always stopping after some hours and the syslog shows:
"Dec 13 20:38:25 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:38:44 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:03 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:22 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:39:41 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:00 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:19 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:38 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:40:57 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:16 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:35 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:41:54 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:13 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:32 Server pvedaemon[1390]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:42:51 Server pvedaemon[1389]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout
Dec 13 20:43:10 Server pvedaemon[1388]: VM 1000 qmp command failed - VM 1000 qmp command 'guest-ping' failed - got timeout"
Are running PVE on an AMD cpu? If so, try kernel 5.15.
 
Dec 8, 2021
1
0
1
62
What works for me while using German versions:

- setting VM hardware to Q35 v6.0
- install of Windows Server as usual (load drivers from the second ISO/DVD virtual io 208)
- install qemu-agent and missing drivers after first boot to desktop
- shut down the VM and change VM hardware to Q35 v6.1
This worked for me too, tnx!
Config: PVE 7.1-7, Win Server 2019 German, virtio 0.1.208-1
 
Last edited:

Borotes

New Member
Apr 8, 2021
15
0
1
24
What works for me while using German versions:

- setting VM hardware to Q35 v6.0
- install of Windows Server as usual (load drivers from the second ISO/DVD virtual io 208)
- install qemu-agent and missing drivers after first boot to desktop
- shut down the VM and change VM hardware to Q35 v6.1
Which network card did you use? I tried what you did on Windows 10 / 2016 but with the virtio paravirtualised card i can't install the drivers.
 
Jan 5, 2022
1
1
1
33
Hy Guys,

I also had this Problem with Proxmox 7.1 and Windows Server 2019 and no Network Adapter is shown A Solution that work for me is following

Setup the machine with Following Parameters.

Machine Type: pc-440fx-6.1
Bios: SeaBIOS
Networkcard: Virtio
Virtiodriver: virtio.win-0.1.208

On installing Machine Just search for the Harddisk driver in vioscsi/2k19/amd64

Finish the Installation

and then do following steps

Go to the Deice Manager Right click the Network Card and Update Driver and here come the Important thing go to your virtio disk in following path
NetKVM/2k16/amd64 an intall this Driver

The 2k19 driver dont work

Install the Rest of Missing drivers with Just the path of your whole virtio Disk

and your done

Best Regards
 
  • Like
Reactions: majorgear

avenger

Member
Jun 23, 2017
2
3
21
45
Same issue here. Does anyone know what the reason for this problem is and what is a reasonable solution? (not work around!)
 
  • Like
Reactions: IsThisThingOn

Deleted member 116138

Guest
Same issue here. Does anyone know what the reason for this problem is and what is a reasonable solution? (not work around!)
For now it looks like that only German versions are affected. So it must be something within Microsoft‘s mysterious OS galaxy…
 

onerom

New Member
Feb 2, 2022
1
0
1
53
Unfortunately Setting Machine Version to 5.1 didn't fix it for me.
Dear all,
this was a very good hint (...for me) :)

Changing the machine version to 5.1 I could install Windows 10 with a network (card).

THX
 

avenger

Member
Jun 23, 2017
2
3
21
45
Updating the machine to an outdated version is not a professional solution to the problem. I've always been a fan of Proxmox, but here I have to say that I feel left out by the developer. The German version of Windows worked up to version 6.x. I don't think M$ is the only one to blame for the problem.
 

Mr.Doubt

New Member
Mar 6, 2022
2
1
3
52
For Windows 10 and Server 2019 in german version, I've tried to change chipset. Somtimes it works, sometimes not.
I've integrated the virtio-drivers (0.215) in the boot.wim, also to the install.wim.
Windows 10 hangs at "Starting devices" at 90%, Server 2019 at 50%. After a few mitutes setup continues.
After reboot, there ist a yello sign at the Red Hat NIC. Deleting the harware (not the driver) an search for new harware fixed it for me every time. Testet on two different hosts (one Intel, one AMD) more than 4 times.

Packeges:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)

Hope this could help someone.
 

IsThisThingOn

New Member
Nov 26, 2021
9
0
1
Is proxmox gonna solve this problem or is "Install it in English and later on change to German" to official solution to this problem?

I don't have a problem with the second one, I just think it should be better documented if that is the solution for this problem.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!