HarryTri

Command prompt doesn't recognizes systeminfo as a valid command but here is the "ntldr" modification date: Wednesday, 17th October 2012. I installed from an OEM XP Home SP2 CD and I installed SP3 afterwards. Then I updated my OS with Windows Update and I kept on updating it when new updates were available.

I checked and I have the log (Windows XP SP3 fully updated). Maybe there is something wrong with Remote Desktop itself in your system? By the way I have never used it, maybe the problem has to do with it (changed settings or whatever)? You were faster than me.

Why not MusicMatch Jukebox version 10 (not the Yahoo one of course)?

Good news! I found the solution for the NTVDM problem here: KB2724197 causing ntvdm.exe to crash. Cannot run 16bit applications Here it is presented as a .reg file: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NTVDM] "BiosRomMappingOption"=dword:ffffffff It works with the latest NTOS files update KB2813170. Caution: It needs a reboot in order to work.

Good news! I found the solution for the NTVDM problem here: KB2724197 causing ntvdm.exe to crash. Cannot run 16bit applications Here it is presented as a .reg file: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NTVDM] "BiosRomMappingOption"=dword:ffffffff It works with the latest NTOS files update KB2813170. Caution: It needs a reboot in order to work.

I eventually installed .NET Framework 3.5 and run the Fix it. It says that the location that Windows Update saves files changed (not at all in fact), it supposedly fixes the problem and verifies the fix but if I run it again it reports exactly the same problem. I guess we must wait for a new version of Windows Update as I have already said.

The FixIt requires NET .Framework 2 which I haven't installed at the moment and I don't think it worths the fuss to install it. The KB is for Windows XP SP2, the update package refuses to run on Windows XP SP3 because the SP3 is newer. I searched the Microsoft's site for something else relevant to the problem and I found nothing. I suppose we must wait for a new version of Windows Update. @snuz2 Did you tried x's solution? Did it help?

Which FAQ? I have the same problem and I ended turning off the automatic updates. I would like to try with this Fixit in case it helps.