What were you trying to do that didn't work?

After upgrading the virtio-win drivers from 1.9.40 to 1.9.53 in a Windows server 2022 VM, the custom network interface name is lost and renamed to "Ethernet Instance 0"

What is the impact of this issue to you?

It affects applications that depend on the network interface name.

Please provide the package NVR for which the bug is seen:

virtio-win-1.9.53-0.el9_6.noarch.rpm

VirtIO Ethernet Adapter 100.102.104.29400

How reproducible is this bug?:

Always

Steps to reproduce

1. In a Windows server 20022 VM with virtio-win-1.9.40, rename the network interface.
2. Upgrade to virtio-win-1.9.53 and reboot

Expected results

Network interface name preserved

Actual results

Network interface name is set to a generic "Ethernet Instance 0"