trelane

@dinhngtu Thanks for fixing the note.

The IP loss did happen on 9.6.0. On the first boot after I set has-vendor-device=false, the guest still reported tools 9.6.0 build 19 (xenbus 9.1.13.23, xenvif 9.1.15.8, xennet 9.1.8.6), and both static IPs were already gone: the main NIC was on DHCP and the second NIC had a 169.254 address. XenClean and the 9.2.385 install came after that.

@cg Agreed. The next person can grab the .msp here:
https://github.com/xcp-ng/win-pv-drivers/releases/download/v9.2.385/XenTools-fix-9.2.351.msp

@dinhngtu Could the release note say "attached to this release" instead of "included"? It reads as if the .msp ships inside the zip. And thanks, your answer settled it. Both of my Windows VMs are on 9.2.385 now, and I took fresh full backups after the switch.

When I turned off "Manage Citrix PV drivers via Windows Update" (has-vendor-device=false) to switch from XenServer VM Tools, Windows treated the NICs as new adapters. The static IPs were gone and one NIC came back on the Public firewall profile. Have console access ready, or a startup script that puts the IPs back by MAC address.

The 9.2.385 release notes list "Fix data corruption issue during in-memory snapshots and backups," with no detail on scope. Two questions before I decide what to do with my Windows VMs:

1. Which XCP-ng tools versions had the bug? Was it only 9.2.350, or does 9.1.x have it too? I just upgraded a VM from 9.1.200 and want to know whether I should re-check older backups of it.
2. Does it affect XenServer VM Tools? I have a Server 2025 VM on XenServer VM Tools 9.6.0 and would rather not swap tool families on it unless the bug applies.

Thanks.