Why? Why Windows XP? Why not!
I’ve been always wondering why all of the sudden we stopped getting good and realiable support for Windows XP in VMware. Plus, I have considered that security measures have been implemented for a reason, and disabling a bunch of stuff arbitrarily doesn’t make things work safely in this day and age. With all of this being said, I’ve been reading a bunch of posts across the internet to figure it out over time and I’ve come to the following conclusions:
- Revisions of “Hardware” versions within VMware stopped caring about XP
- VMware drivers for XP stopped being shipped, which is a pain in it of itself
- Microsoft changed how the timers worked across the system, from a system-wide timer, to a per-process timer - (Previously it was a global resource if I read correctly…)
SO! I’ve cobbled up a couple of things to tinker with with the latest version of VMware, some things work, some things don’t - but I am still trying to see how to make this all work! Remember, the idea is to go forwards with the updates here, not backwards!
Getting the drivers!
You can just browse to the master VMware Tools repo while you can, it’s still open. Latest VMware Tools that support XP is 10.0.12.
Fixing the timer! Audio comes back!
One of the issues with trying to run Windows XP with the latest VMware Pro is that the audio is super garbled. This is a direct impact from the Global Timer vs Per-Process timer. Sometimes you get choppy audio, sometimes no audio at all! From here, you have two choices to use:
- GitHub - Raymai97/VMAudioBackHost: Another attempt to fix what VMAudioBack couldn't. - Program to run once your XP VM has started to fix the timing
- GitHub - everything411/VMAudioBackHook: DLL hijack version of VMAudioBack / VMAudioBackHost, fix distort sound/audio issue for Windows XP/2003 VM in VMware running on Win10 2004 or later - Same concept but it loads itself directly on VMs, no need to run a separate program other than VMware.
Enabling 3d!
If you find that VMware doesn’t support DirectX 3D through dxdiag.exe, then you can add the following line to your .vmx file (The config file for your XP VM):
mks.enable3d = "TRUE"
mks.gl.allowUnsupportedDrivers = "TRUE"
Now this is a bit experimental so take it with a grain of salt: Some posts highlight that Windows 2000 3D support is dropped if a VMware Hardware version older than 9 is used. You can update the following line within your .vmx file:
virtualHW.version = "9"
Note: You may have to remove the sata devices from this configuration as it is not supported within the Hardware version 9. Windows XP should be running on IDE virtualization IIRC.
What’s missing?
After doing all of that, you will see that you will have audio working perfectly, and that 3D acceleration (D3D) is working great! However, 2D (DD - DirectDraw) runs SO poorly it’s not funny to even make fun of. I am still unsure on how to fix this, but will come back to this to update once I figure it out!
Edit: Forgot to add the references ![]()
References
- Windows Timer Resolution: Windows Timer Resolution: The Great Rule Change | Random ASCII – tech blog of Bruce Dawson
- Timer resolution bug identified: Doesn't work in latest VMWare Workstation Player 16 · Issue #3 · Raymai97/VMAudioBack · GitHub
- 3D Settings for VMware: https://www.vogons.org/viewtopic.php?t=88678
- Last VMware Tools version to support Windows XP: VMware Tools support for Windows 2000, Windows XP, and Windows Server 2003