Windows 10 pro VM clone - NIC not updating

cot

Active Member
Aug 24, 2015
33
0
26
Using latest Proxmox 4.1-13 and facing problems cloning Win10 pro VM. It seems the NIC/Mac address is still using original/template VM and not automatically updated to the new clone VM's Mac address. Using latest VirtIO drivers (virtio-win-0.1.112).

Workaround is to manually remove/re-add the NIC on pve gui and then inside VM Windows device manager to resolve this issue.

Anyone facing this issue? Is this a bug ?
 
Last edited:
Update:

There seems to be a bug for VirtIO NIC drivers for Win10.
No issues if you select default e1000 NIC for Win10.
 
Just had the same issue on Proxmox 8.1.4 with Windows 11.

This guide said to remove/add the Network interface device from the Hardware list - this did not solve the problem.

However, I also tried renaming the machine (right click "My Computer" -> Properties -> Rename Machine) as it had the same name source of the clone which is not good.

After the rename + reboot the Mac address was updated.

I tried this another time and the only thing I had to do was to rename the machine, it automatically got a new MAC after the clone.
 
Last edited:

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 yours easily in our online shop.

Buy now!