Windows version detection issue When migrating Media Center to Server 2003 x86 When running Windows Update with Legacy Update
Hi Adam Do you know the XP2ESD project in the MDL forum? (Create modern Windows XP installer) project information https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-6-2.82935/ George King Plans to Move Media Center 2005 and Tablet PC Edition to Server 2003, where I'm also responsible for both the Addon and UpdatePacks. But I wonder if the program has problematic detection.
After using the Media Center addon
1.legacy update error says Windows XP Pro x64 (it is x86)
2.And I tested the 2nd round without UpdatePacks, more crashes with legacy update, Windows Explorer crashing.
3. The update still installed correctly.
Video of the test https://drive.google.com/file/d/1UqP7AoSoYFEWgmmltLC3c-8xNVHHe0l6/view?usp=share_link
I'm happy to provide you with a test file if you want.

I think it is the media center reg key that interfered the detection of WU
I think it is the media center reg key that interfered the detection of WU
As a Windows XP x86 version 3790.3959 is weird for WU Server so it cannot determine what is that.
You may delete the key registry and check,the restore it.
The OS detection in Legacy Update 1.8 now uses exactly what Windows itself reports - specifically it pulls the string from WMI, which you can also see by running wmic os get caption. I don’t fully understand how this Media Center/Tablet PC on Server 2003 setup works, but given I can see Manage Your Server in the taskbar I’m assuming the OS caption might still be “Windows Server 2003, Standard Edition”.
Note - this doesn’t change which updates you’ll see. The OS label on the website is more of a cosmetic thing, unrelated to what updates Windows Update will deliver you.
Since this is a configuration that was never supposed to be possible originally, it makes sense that WU is confused about it and is probably returning the wrong set of updates. It’s hard to say if this is even a config that can be updated. Someone might need to try triaging which updates do and don’t work.