Every business has one. A piece of software that’s critical to operations, hasn’t been updated in years, and absolutely will not run on anything newer than Windows 7. Maybe it controls a piece of manufacturing equipment. Maybe it’s a custom database built for a client that no longer exists. Maybe it’s an accounting package that predates cloud software by a decade.
The temptation is to keep an old physical machine running just for that application. Virtualisation is a better answer.
The Legacy Software Problem
Software written for Windows XP or Windows 7 can fail on modern operating systems for several reasons:
- It uses APIs or system calls that were removed in later Windows versions
- It requires 16-bit subsystem support, which is absent from 64-bit Windows
- It was written to run as an administrator by default, which conflicts with modern security models
- It relies on specific registry paths, file locations, or hardware abstraction layers that have changed
Running it on a modern physical machine with Windows 10 or 11 often produces errors, crashes, or silent failures. The software simply wasn’t written to handle the environment it’s now being asked to run in.
What Windows XP Mode Was
Microsoft introduced Windows XP Mode with Windows 7 as an official solution to this problem. It was a licensed copy of Windows XP running inside a virtual machine (powered by Virtual PC), integrated into the Windows 7 desktop so that XP applications appeared in the Windows 7 taskbar alongside native apps.
Windows XP Mode is no longer supported and cannot be activated on modern Windows. But the principle it demonstrated is still the right approach: run the legacy operating system inside a virtual machine, isolated from the host, with the application running inside that controlled environment.
The Modern Equivalent: Virtualisation
The current approach to running legacy software on modern hardware is to create a virtual machine running the required legacy OS and install the application inside it. The VM runs on modern hardware using a hypervisor; the legacy OS and application run inside it, unaware that they’re not on physical hardware from 2003.
This gives you several advantages over keeping an old physical machine running:
The hardware is modern and supported. The VM host runs on current hardware with current firmware, supported components, and reliable storage. The ageing physical machine with failing capacitors and an end-of-life hard drive is retired.
The legacy OS is isolated. A Windows XP VM with no internet access and no connection to your main network is significantly less dangerous than a physical Windows XP machine connected to your office network. Isolation limits the damage if the old OS or software is exploited.
Snapshots provide a safety net. Before any change, you take a snapshot of the VM. If something goes wrong, you roll back in minutes.
The VM is portable. A virtual machine is a set of files. It can be copied, backed up, and moved to new hardware without reinstallation.
How to Set It Up
Choose Your Hypervisor
For a single legacy application on a desktop machine, VirtualBox (free) is a practical choice. For a production environment where the VM needs to run continuously, Proxmox or Hyper-V on a server is more appropriate.
Source the Legacy OS Licence
This is the part many people overlook. Running Windows XP or Windows 7 in a VM still requires a valid licence. If your business has existing licence keys from original installations, these are typically transferable to a VM (check Microsoft’s licence terms for your specific edition). Volume licence customers should verify with their licence agreement.
Microsoft no longer sells Windows XP or Windows 7 licences, but legitimate used licences are available through specialist resellers. Do not use unlicensed copies; beyond the legal risk, unlicensed installations may have been tampered with.
Install and Configure
Install the legacy OS in the VM, apply any service packs available at end-of-life, and install the legacy application. Configure networking carefully:
- If the application doesn’t need network access, disable the VM’s network adapter entirely
- If it needs to communicate with other systems on your network, place it on an isolated VLAN with only the specific access it requires
- Do not give it general internet access
Integrate with Modern Workflows
Many hypervisors support shared folders between the VM and the host, allowing files to be passed in and out without network access. VirtualBox’s Guest Additions provide clipboard sharing and display scaling as well.
For applications that produce output (reports, exports, printed documents), configure them to write to a shared folder that the host machine can access. This allows the legacy application to fit into modern workflows without exposing the old OS to the network.
What About Compatibility Modes?
Windows 10 and 11 include compatibility modes that attempt to emulate earlier Windows environments for legacy applications. Right-clicking an executable and choosing Troubleshoot compatibility runs a wizard that adjusts how Windows presents itself to the application.
Compatibility modes work for some older applications, particularly those that fail due to permission issues or minor API differences. They don’t work for applications that require 16-bit support, specific hardware drivers, or deep integration with a legacy OS environment.
Try compatibility mode first. If it doesn’t resolve the problem, a VM is the reliable solution.
When the Real Answer is Replacement
Running legacy software in a VM is a pragmatic workaround, not a long-term strategy. The right long-term answer is replacing the legacy application with a modern equivalent.
That’s not always possible immediately. Replacement may require budget that isn’t available, a vendor that no longer exists, or custom redevelopment of something that was built in-house. In those cases, a properly isolated VM extends the life of the application without the risks of running it on an exposed physical machine.
But if a replacement path exists, the VM approach buys time rather than solving the problem. Use it as a bridge, not a destination.