I just wanted to make sure others have not encountered any issues. My setup is stable and I would like to keep it that way 
Joining in with the following observations; over a year since last driver refresh, there have been driver updates but no binaries released until now. Upstream changelogs minimal to say the least. This is Not the fault of Proxmox team. We know older versions of windows are dropped from support on later versions.
Installed virtio-win-0.1.302 on x3 test nodes comprising 60-odd 2022, 2025 datacenter and standard, W10, W11 ent and LTSC, not that versioning makes much difference. Includes x6 SQL 2022 servers testing db performance. All nics are NetKVM, all i/o is virtio-scsi, all vms have vio-serial, SOME have balloon. All installed with guest agent version 110.2.3.
Home-grown upgrade script inside SCCM for modern windows (essentially does a pnputil /add-driver /install with detection logic on driver version in %SystemRoot%\System32\DriverStore\FileRepository) works well with held-back reboot.
Short memory use increase on hosts until all windows VMs upgraded to same version, perhaps KSM, perhaps balloon, no idea not fussed..
No issues, network, disk i/o inside vm or other. No issues backing up with PBS. Other peoples mileage may vary.
We know a simple driver update only needs a restart of the OS not complete reset of VM on host but if you haven't already done it, pve-qemu-kvm-11.1 just dropped along with a PBS update if you use, time it right and you can hit all 3.
My thanks to the upstream driver maintainers for maybe a long overdue update with some fixes and to the Proxmox team for continual improvement on all things Proxmox!
M
Installed virtio-win-0.1.302 on x3 test nodes comprising 60-odd 2022, 2025 datacenter and standard, W10, W11 ent and LTSC, not that versioning makes much difference. Includes x6 SQL 2022 servers testing db performance. All nics are NetKVM, all i/o is virtio-scsi, all vms have vio-serial, SOME have balloon. All installed with guest agent version 110.2.3.
Home-grown upgrade script inside SCCM for modern windows (essentially does a pnputil /add-driver /install with detection logic on driver version in %SystemRoot%\System32\DriverStore\FileRepository) works well with held-back reboot.
Short memory use increase on hosts until all windows VMs upgraded to same version, perhaps KSM, perhaps balloon, no idea not fussed..
No issues, network, disk i/o inside vm or other. No issues backing up with PBS. Other peoples mileage may vary.
We know a simple driver update only needs a restart of the OS not complete reset of VM on host but if you haven't already done it, pve-qemu-kvm-11.1 just dropped along with a PBS update if you use, time it right and you can hit all 3.
My thanks to the upstream driver maintainers for maybe a long overdue update with some fixes and to the Proxmox team for continual improvement on all things Proxmox!
M