Compatibility
What XPC supports — stated plainly.
A public matrix rather than a sales sheet. Where we support something we say so; where the behaviour belongs to Windows or your remote client we say that too; and where we make no promise, we say nothing more than that.
Supported
Tested and supported by XPC. Raise it with us if it does not behave as described.
Works, owned elsewhere
Unchanged by XPC because Windows and your remote client remain in place. Support stays with that vendor.
Not claimed
We make no promise here. It may work, but do not plan around it without testing.
Windows versions
XPC installs as a standard MSI on supported Windows desktop editions.
| Item | Status | Notes |
|---|---|---|
| Windows 11 Pro and Enterprise | Supported | Current and recent servicing versions. |
| Windows 10 Pro and Enterprise | Supported | Supported servicing versions. |
| Windows 11 / 10 Home | Supported | Supported. XPC Mode is configured from the XPC Cloud Portal, so no domain join or Group Policy is required. |
| Windows LTSC editions | Supported | Common in kiosk, POS and frontline estates. |
| Windows Server as a desktop endpoint | Not claimed | XPC targets desktop endpoints. |
| Non-Windows endpoints (macOS, Linux, ChromeOS) | Not claimed | XPC is a Windows access shell. |
Remote platforms the endpoint connects to
XPC launches the vendor's native client on the Windows PC, so the session experience is the one your platform already delivers.
| Item | Status | Notes |
|---|---|---|
| Citrix Virtual Apps and Desktops (Workspace app) | Supported | Published desktops and published applications. |
| Microsoft RDP / RDS session hosts | Supported | Standard Remote Desktop client. |
| Azure Virtual Desktop | Supported | Launched through the Microsoft client on the endpoint. |
| Windows 365 Cloud PC | Supported | Launched through the Microsoft client on the endpoint. |
| VMware / Omnissa Horizon | Works, owned elsewhere | Launched via the vendor's Windows client; behaviour owned by that client. |
| Amazon WorkSpaces | Works, owned elsewhere | Launched via the vendor's Windows client. |
| Parallels RAS | Works, owned elsewhere | Launched via the vendor's Windows client. |
| Browser-delivered portals and web applications | Supported | Published as a launcher entry. |
Peripherals
Windows and its drivers stay in place, so attached hardware behaves as it does on a normal Windows PC.
| Item | Status | Notes |
|---|---|---|
| Receipt, label and document printers | Works, owned elsewhere | Existing Windows drivers and vendor utilities. |
| Barcode, RFID and document scanners | Works, owned elsewhere | Unchanged driver stack. |
| Headsets, handsets and webcams | Works, owned elsewhere | Handled by Windows and the native client. |
| Smart card readers and signature pads | Works, owned elsewhere | Unchanged Windows drivers and middleware. |
| Cash drawers, scales and POS peripherals | Works, owned elsewhere | Vendor drivers and utilities continue to load. |
| Multi-monitor layouts | Works, owned elsewhere | Owned by the native remote client's display handling. |
| USB redirection behaviour | Not claimed | Determined by your remote platform and client policy, not by XPC. |
Management, security and identity
XPC changes the user-facing shell. It does not replace or interfere with the systems that manage the endpoint.
| Item | Status | Notes |
|---|---|---|
| RMM and remote support tooling | Works, owned elsewhere | Agents continue to run on Windows and reach the device. |
| EDR and antivirus agents | Works, owned elsewhere | Unchanged; XPC is not a security product. |
| Microsoft Intune / MDM enrolment | Works, owned elsewhere | Device management and compliance reporting unaffected. |
| Group Policy and Active Directory join | Works, owned elsewhere | Existing joins and policies remain valid. |
| Windows Update and patching | Works, owned elsewhere | Your existing patching process continues. |
| XPC Mode enable/disable per PC | Supported | Controlled centrally from the XPC Cloud Portal. |
| Branding of the XPC screen | Supported | Logo, colours and wording, per tenant. |
| Replacing your identity provider or MFA | Not claimed | XPC does not provide authentication. |
Boundaries
What XPC deliberately does not claim.
Being clear about the edges is the only way a compatibility statement is useful.
Limits
Read this before you plan a rollout.
- XPC is not an operating system. If something does not work on the Windows endpoint today, XPC will not change it.
- XPC is not a remote desktop protocol or a VDI broker. Session delivery remains your platform's responsibility.
- XPC is not an endpoint security product, an RMM or an MDM, and does not replace any of them.
- XPC does not add peripheral or redirection capability beyond what Windows and your native client already provide.
- Platforms listed as 'works' are launched through the vendor's own Windows client; behaviour inside those sessions is owned by that vendor.
Test it on five PCs, free.
The fastest way to confirm compatibility in your environment is to run XPC on a handful of machines.