Hello all,

Version 9.0.9137 Release Signed of the Windows PV drivers has been released.

Proudly presenting the first signed build of the XCP-ng Windows PV drivers since 8.2.2.200-RC1 was released over six years ago. This build can be installed as-is without further configuration.

Always download the latest release from https://github.com/xcp-ng/win-pv-drivers/releases !

To download XenClean, click here. The installer downloads also includes a copy of XenClean and XenBootFix. Remember to carefully read XenClean docs before use.

Before installing

Thank you for using our Windows PV drivers. Please carefully read the instructions below.

• Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing.
• Make backups/snapshots before installing!

Known issues

• NIC RSS is not functional; fixes are under way.

Changes since 9.0.9136

• NEW: Digitally-signed drivers and installer.
• Fixes: Fix Xen Guest Agent version reporting.

Changes since 8.2.2-beta

• IMPORTANT: Security fix for XSA-468 (CVE-2025-27462, CVE-2025-27463, CVE-2025-27464). Check the XCP-ng docs or blog announcement for more details.

• This release is based on upstream 9.1-series drivers, which includes the PV Mouse/Keyboard driver and PV Console Driver. You can access the PV console with the following command from a XCP-ng host:

xl console -t pv <vmname>

• New installer with clean uninstallation and multiple install/uninstall safety checks.
• New XenClean utility for cleanly removing XCP-ng and Citrix drivers.
• Numerous driver stability fixes.
• Volume Shadow Service Provider is no longer included. (XCP-ng 8.1 and newer no longer support quiescent snapshots)
• Check out the new Rust-based Xen Guest Agent included in our package! We're looking to bring back even more features to the agent.
• Older Windows versions are no longer supported. The driver requires at a minimum Windows 10 1607 or Windows Server 2016.

Help / Community support

If you encounter installation/uninstallation errors, please try again with one of the following commands:

For installing:
msiexec.exe /i XenDrivers-x64.msi /log install.log

For uninstalling:
msiexec.exe /x XenDrivers-x64.msi /log uninstall.log

Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues.

Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.

• Discussion: https://xcp-ng.org/forum (preferred)
• Issue Tracker: https://github.com/xcp-ng/xcp/issues
• IRC: #xcp-ng and #xcp-ng-dev on irc.freenode.net

Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.0.9136...v9.0.9137

Hello,

We're glad to announce a new Alpha version 9.0.9000.0 of our XCP-ng Windows PV Drivers for Windows 10 1607 or newer, and Windows Server 2016 or newer. Note: this driver release is for testing purposes only. Not for production use!

The release includes new 9.1-series drivers from Xen Project with new features and stability improvements. We also included a XenClean tool for cleanly removing any existing Xen PV drivers, whether they are installed via XCP-ng, Citrix or Windows Update. Feel free to give it a try!

We're looking to finalize the drivers and produce a signed, Windows-ready installation package. Your feedback will help us greatly in reaching this goal.

You'll find the new release on XCP-ng GitHub. Below are the release notes:

Before Installing

• This driver release is for testing purposes only. Not for production use!
• Make backups/snapshots before installing!
• The drivers in this package are testsigned and require enabling testsigning mode. Disable Secure Boot, then run the included script testsign/install.ps1 as Administrator to configure Windows and install the necessary signer certificates. Your VM will reboot automatically.
• If you encounter installation/uninstallation errors, please try again with one of the following commands:

For installing:
msiexec.exe /i XenDrivers-x64.msi /l*vx install.log

For uninstalling:
msiexec.exe /x XenDrivers-x64.msi /l*vx uninstall.log

Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues.

Changes since 8.2.2-beta

• This release is based on upstream 9.1-series drivers, which includes the PV Mouse/Keyboard driver and PV Console Driver. You can access the PV console with the following command from a XCP-ng host:

xl console -t pv <vmname>

• New installer with clean uninstallation and multiple install/uninstall safety checks.
• New XenClean utility for cleanly removing XCP-ng and Citrix drivers.
• Multiple driver stability fixes.
• Volume Shadow Service Provider is no longer included. (XCP-ng 8.1 and newer no longer support quiescent snapshots)
• Management Agent is currently not included. Xen Orchestra may show "Management agent not detected", but shutdown and reboot features will work normally. We're looking to bring back features of the management agent in the next releases.

Help / Community Support

Please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.

Find the latest announcements here: https://xcp-ng.org/forum/topic/10889/xcp-ng-windows-pv-tools-announcements

---

---

edit: Before using XenClean or XenBootFix, please read carefully the instructions on the XCP-ng documentation website!

Hello all,

Version 9.0.9030 of the new Windows PV drivers has been released.

This release brings multiple driver stability fixes, a new Rust-based Xen Guest Agent and the XenBootFix boot repair tool.

This driver release is for testing purposes only and not for production use. It requires putting the system into testsign mode. (only applies to the drivers themselves, not XenBootFix and XenClean; you can use the two tools separately without any configuration)

Download the release here: https://github.com/xcp-ng/win-pv-drivers/releases/tag/v9.0.9030

Release notes are below:

Before Installing

• This driver release is for testing purposes only. Not for production use!
• Make backups/snapshots before installing!
• The drivers in this package are testsigned and require enabling testsigning mode. Disable Secure Boot, then run the included script testsign/install.ps1 as Administrator to configure Windows and install the necessary signer certificates. Your VM will reboot automatically.
• If you're running version 9.0.9000.0, we're interested in hearing about your upgrade experience to 9.0.9030.

Changes since 9.0.9000.0

• NEW: Includes the new Rust-based Xen Guest Agent for resource and IP address reporting.
• NEW: Includes the new XenBootFix boot repair tool for VMs rendered unbootable by any Xen drivers (Xen PV, XCP-ng, Citrix, etc.)
• NOTICE: Xen PV disk drivers are now disabled by default on new installations. The default emulated NVMe driver will be used instead. Existing installations will not be affected.
• Fixes: Many more installation, uninstallation and upgrade safety checks are now built into the installer.
• Fixes: Various improvements to XenClean for more complete removal of driver services.
• Fixes: xenvbd: Xen PV disk drives now report as SSD drives to avoid unnecessary defragmentation (commit)
• Fixes: xenvif: Fix various VM hanging and crashing issues when changing VM network in Xen Orchestra (commit 1, commit 2)
• Debug symbols are now included with the installation package.

Changes since 8.2.2-beta

• This release is based on upstream 9.1-series drivers, which includes the PV Mouse/Keyboard driver and PV Console Driver. You can access the PV console with the following command from a XCP-ng host:

xl console -t pv <vmname>

• New installer with clean uninstallation and multiple install/uninstall safety checks.
• New XenClean utility for cleanly removing XCP-ng and Citrix drivers.
• Multiple driver stability fixes.
• Volume Shadow Service Provider is no longer included. (XCP-ng 8.1 and newer no longer support quiescent snapshots)
• Management Agent is currently not included. Xen Orchestra may show "Management agent not detected", but shutdown and reboot features will work normally. We're looking to bring back features of the management agent in the next releases. Check out the new Rust-based Xen Guest Agent included in our package! We're looking to bring back even more features to the agent.
• Older Windows versions are no longer supported. The driver requires at a minimum Windows 10 1607 or Windows Server 2016.

Help / Community Support

If you encounter installation/uninstallation errors, please try again with one of the following commands:

For installing:
msiexec.exe /i XenDrivers-x64.msi /l*vx install.log

For uninstalling:
msiexec.exe /x XenDrivers-x64.msi /l*vx uninstall.log

Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues.

Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.

• Discussion: https://xcp-ng.org/forum (preferred)
• Issue Tracker: https://github.com/xcp-ng/xcp/issues
• IRC: #xcp-ng and #xcp-ng-dev on irc.freenode.net

Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.0.9000.0...v9.0.9030

kernel-4.18.0-553.71.1.0.1.el8_10 (OL8) and kernel-5.14.0-570.37.1.0.1.el9_6 (OL9) do not contain the fix. kernel-6.12.0-55.29.1.0.1.el10_0 (OL10) does.

@hypernoob I suggest this procedure instead:

• Get the Debian genericcloud QCOW2 image off of here: https://cdimage.debian.org/images/cloud/
• Convert to VHD: qemu-img convert -O vpc debian-12-genericcloud-amd64.qcow2 debian-12-genericcloud-amd64.vhd
• Import the converted VHD into XO
• Attach to empty Debian VM, set to boot from hard drive and convert to template
• Create new VMs from this template, adding your ssh keys and guest agent in cloud config if desired:

#cloud-config
hostname: {name}
ssh_authorized_keys:
  - ssh-rsa ...
apt:
  sources:
    xen-guest-agent:
      filename: xen-guest-agent.list
      source: deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/
      append: false
packages:
  - xen-guest-agent

The same procedure will work with Ubuntu, Alma and other cloud images.

Hi all,

I've uploaded a version of the mitigation script Install-XSA468Workaround-Win7.ps1 with unofficial support for down to Windows 7/2008R2 and 8/8.1/2012/2012R2.

Reminder: this is purely unofficial support and not tested on all listed OSes yet. The mitigation script itself is meant as a last resort only when you absolutely cannot update; it does not mitigate all vulnerabilities and it does not replace updating your drivers.

@Tristis-Oris @TrapoSAMA

XSA-468: multiple Windows PV driver vulnerabilities - update now!

Original announcement: https://xcp-ng.org/blog/2025/05/27/xsa-468-windows-pv-driver-vulnerabilities/.
Check the XCP-ng docs for the latest updates.

Summary

Multiple vulnerabilities have been discovered in all existing Xen PV drivers for Windows from all vendors (XCP-ng, XenServer, etc.) published prior to the disclosure, on May 2025.

These vulnerabilities allow unprivileged users to gain system privileges inside Windows guests.

These issues have the following identifiers:

• CVE-2025-27462
• CVE-2025-27463
• CVE-2025-27464

Am I affected?

Windows guests running vulnerable versions of Xen PV drivers are affected. Other guest OSes are not affected.

To check if you're affected, verify the version of Xen PV drivers in Device Manager.

Driver version numbers are independent from Xen PV tools package versions. Use the methods below to check the precise driver versions.

• XCP-ng PV Bus, XCP-ng Interface and XCP-ng PV Console older than 9.0.9065 are affected.
• XenServer/Citrix PV Bus older than 9.1.11.115; PV Interface older than 9.1.12.94 are affected.
• Other Xen PV drivers for Windows are also likely affected. If you are using these drivers, verify each vendor's security bulletins for more details.

You can check for this vulnerability from within the Windows VMs themselves (most precise, recommended) but also from outside the VMs, using tools we built for this purpose.

If you are reading this article shortly after its publication, it's likely that all of your Windows VMs are vulnerable.
Once patched, follow these instructions to verify that your VMs are no longer vulnerable.

Check a Windows VM for vulnerability

This is the most precise way, but needs to be done per VM.

• Verify the version numbers in Device Manager.
• Use the mitigation script published in the XSA-468 advisory in -Scan mode (will only report the vulnerability, not version numbers). See the script for documentation.

Detect vulnerable VMs at the pool level

This method requires the latest XCP-ng updates to be applied, in XCP-ng 8.2 and 8.3.

We developed two features to help you with the handling of these vulnerabilities.

• A host-side detection script, that you can run in dom0. It will list affected Windows VMs based on their PV driver versions. See the script for documentation.
• A warning ️ sign next to affected VMs and a vulnerable? filter in Xen Orchestra. These features will be made available very soon, through an update to the stable channel. Keep an eye on the XCP-ng documentation for announcements.

This detection depends on XAPI accurately reporting PV driver versions. Prior to the recent XCP-ng 8.2 and 8.3 updates released in May 2025, this was not the case. As a result, the detection tools cannot assess VMs that have not been run since the updates were applied. If no driver information is available, a warning will be displayed.

️ Only virtual machines (VMs) created using a Windows template—or from templates or VMs originally derived from one—can be detected by these tools. They are designed to help users identify vulnerable VMs that may have been overlooked, forgotten during patching, or restored from backups taken before vulnerability fixes were applied. These tools are not intended to serve as comprehensive detection solutions, so do not rely on them exclusively.

How to patch my VMs?

First, create backups and snapshot your VMs before updating.

If you're using XenServer Windows PV drivers or have enabled the "Manage Citrix PV drivers via Windows Update" feature: Upgrade to XenServer VM Tools 9.4.1 or later.

If you're using XCP-ng Windows PV drivers 8.2.x, you should use XenClean to remove the existing drivers, then choose one of the following:

• On a production system, install XenServer VM Tools 9.4.1 or later;
• If you're not running a production system, and want to test the latest XCP-ng Windows PV drivers: install XCP-ng driver version 9.0.9065 or later. (Note that this requires bringing Windows into test signing mode)

If you're already using XCP-ng Windows PV drivers 9.0: Install XCP-ng driver version 9.0.9065 or later.

I can't patch now, what should I do?

You are encouraged to apply the latest updates as soon as possible.

If you absolutely cannot update, apply the mitigation script provided by Vates and the Xen Project, available at https://xenbits.xen.org/xsa/advisory-468.html.

Note that this mitigation script only covers vulnerabilities in the Xen PV Interface driver.

You should run the mitigation script in Scan mode afterwards to make sure the vulnerability is effectively mitigated.

How is Vates helping to address this vulnerability?

This issue was discovered by Vates as part of our investment into upstream Xen development. Vates VMS provides multiple facilities to help users affected this issue:

• We developed fixes for these vulnerabilities, which have been integrated upstream.
• We provided a mitigation script for those who cannot install the update.
• We have added detection logic in Xen Orchestra's latest release channel to actively alert on vulnerable Windows VMs. We also updated XCP-ng 8.2 and 8.3 so that PV driver versions are reported to Xen Orchestra for it to detect vulnerable Windows VMs. See "Am I affected?" above.
• We have developed a script that can be run in dom0 to perform the same detection, in case Xen Orchestra’s detection logic is not yet available to you. See "Am I affected?" above.
• We are publishing an alert about the vulnerability inside all Xen Orchestra appliances.
• We alert about this vulnerability at the beginning of our latest newsletter.

Why can't I use XCP-ng Windows PV drivers in production?

The XCP-ng 9.0 drivers aren't signed by Microsoft yet, and thus currently require putting Windows into test mode. As a result, these drivers are not appropriate for production use.

You may have noticed that the XCP-ng 8.2 Windows drivers can still be used when Secure Boot is disabled. This is due to these drivers being signed before Microsoft changed the driver signing rules and forcing 1st-party driver signatures.

We are actively working with Microsoft to get the drivers signed (which is a slow process). An announcement will be made as soon as a Microsoft-signed build is available.

Related links

• Xen Project announcement: https://xenbits.xen.org/xsa/advisory-468.html
• XenServer Security Bulletin: https://support.citrix.com/article/CTX692748

This is a driver bug that we fixed in XCP-ng Windows tools v9.0.9030 but hasn't been integrated by Citrix yet. You can try it out if you're not running a production system.

@plaidypus Hello, I'll change it to report the correct OS version (Windows 11 Professional 64-bit, Windows Server 2022 Datacenter 64-bit) in the next version. In fact, the change is already integrated in our code here: https://github.com/xcp-ng/xen-guest-agent/commit/004056c1d6f185077768678944558dd5df5fa45d

Hi all, here's a pre-build of the fix for anyone who wants to test (8.3 only):

wget https://koji.xcp-ng.org/repos/user/8/8.3/xcpng-users.repo -O /etc/yum.repos.d/xcpng-users.repo
yum update --enablerepo=xcp-ng-ndinh1

Hello all,

The XCP-ng Standard VGA Display Driver v0.1.34.2310 is released with important compatibility fixes for Windows Server.
Get it here: https://github.com/xcp-ng/win-xstdvga/releases

This driver provides high-resolution consoles and resolution switching in Xen Orchestra for Windows VMs running on the XCP-ng hypervisor.

This is a beta release. This driver will eventually be integrated into the main Windows PV tools package.

Changelog:

• Add support for multiple VGA devices
• Fix compatibility with older versions of Windows Server
• Enable CET Shadow Stack support
• Add device name branding

Hello all,

The XCP-ng Standard VGA Display Driver for Windows v0.1.29.2216 has been released https://github.com/xcp-ng/win-xstdvga

This driver provides high-resolution consoles and resolution switching for Windows VMs running on the XCP-ng hypervisor.

This is a beta release. This driver will eventually be integrated into the main Windows PV tools package.

Driver pulled for bug fixes. Will come back soon

@acebmxer Re time issues: Do you have Xen tools or any other sources of time sync? Suspending a VM and then later resuming it will cause the VM's time to not be updated. It'll have to rely on either NTP or the Xen tools daemon to get the correct time.

@wilsonqanda Make sure to turn off "Network" in boot order. You might also want to increase the VM's root disk size when creating it.

Here's a full cloud config that I used (except the ssh keys):

#cloud-config
hostname: {name}
ssh_authorized_keys:
  - ssh-rsa ...
disable_root: false
apt:
  sources:
    xen-guest-agent:
      filename: xen-guest-agent.list
      source: deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/
      append: false
packages:
  - xen-guest-agent

@busthead Do you see anything when typing dir FS0: at the shell? Also, can you upload the non-working ISO somewhere and send it to me via PM?

The Windows ISOs also require you to press a key to start Setup. If XCP-ng Center is not fast enough to display the screen then you may end up with the UEFI shell. Try starting the installation from Xen Orchestra or spamming a key when the VM is starting.

@Chemikant784 Never mind, I think I've found the right combination of Registry options to disable the driver installations from the onboard script side.

But yes, the idea is to make the process as automatic as possible. I can change the onboard script to shut down after the initial uninstallation instead.

Also, the installation MSI will need some changes in order to avoid being blocked by stale C000 devices.

@Chemikant784 Indeed one of the problems is that on newer versions of Windows, Microsoft decided to completely disregard several Windows Update policies, including the ones related to device installation (?!). So once the Citrix option is enabled, Windows will insist on installing the drivers for it no matter what, which is why the 2nd XenClean is needed after disabling the Windows Update option in order to clean up after Windows.

@Chemikant784 I've been preparing a reworked XenClean and XCP-ng driver onboarding tool here. Every time the onboard.ps1 script is run, it'll try to automatically uninstall old drivers and install the XCP-ng as conditions permit: https://nextcloud.vates.tech/index.php/s/eL4sfxQGxZXe8SX

The Windows Update device is quite stubborn since disabling it causes the problem as you said. Could you try the following procedure:

• Keep the Windows Update option enabled
• Block installation of the PCI\VEN_5853&DEV_C000 device using the "Prevent installation of devices that match any of these device IDs" setting
• Run XenClean
• Turn off the Windows Update option
• Install XCP-ng drivers

Getting rid of the Windows Update device is quite cumbersome... I'll look for a way to automate this

@psafont Freezing/thawing doesn't actually suspend a VM, but it's just a part of the backup process, where I/O operations are quiesced to create a stable view of the on-disk data.

@psafont Looks like these hooks are for suspend-resume rather than snapshot/backups? I couldn't find any mention of hook calls during the snapshot process