Common Update Issues

Nothing happens when I run LegacyUpdate.exe

There is an issue in Windows XP that appears to be triggered by the digital signature on the latest versions of Legacy Update (1.8 and later). This makes Legacy Update setup not run at all, with no error message.

To work around this, you will need to unblock the file:

  1. Right click LegacyUpdate.exe and select Properties.

    Context menu on LegacyUpdate.exe, with Properties highlighted.

  2. Click Unblock at the bottom of the window, then click OK.

    LegacyUpdate.exe Properties dialog, with the Unblock button highlighted.

This workaround isn’t needed if legacyupdate.net is in your Internet Explorer Trusted Sites list. This is done for you automatically when you install Legacy Update.

If you’re nervous about whether the file is safe or not, you can review the Digital Signatures tab of the file properties on a newer operating system such as Windows 10, which will have no issue confirming that it’s signed by Hashbang Productions.

Microsoft Security Essentials

Attempting to update Microsoft Security Essentials on Windows XP or Vista will display an error message with code 0x80072EFE - “The definition updates couldn't be installed. Please try again later.” Instead, you will need to manually download and install the final definition update that supported these versions:

Updating Security Essentials still won’t be possible, because no more updates exist. However, once manually installed, these definitions can always be used to scan your PC for malware.

Windows Live Essentials 2012

Attempting to install Windows Live Essentials 2012 on Windows XP or Vista, as offered by Windows Update, will fail. This is because it ignores your PC’s Windows Update configuration, and will always try to retrieve updates directly from Microsoft, bypassing Legacy Update. Instead, you will need to manually download and install the full/offline installer of Windows Live Essentials 2012.

Security Update for Windows XP (KB2686509)

This update, a security patch for a vulnerability in how Windows XP parses keyboard layout data, is notorious for failing to install. The cause is that the update is slightly different between standard Windows XP and Windows Embedded 2009, so if you’ve selected to receive Embedded 2009 updates on XP, the incorrect version of this update will be downloaded.

To fix this, manually download and install the Windows XP variant of the update:

Windows 7 “E” editions

Legacy Update requires Internet Explorer, but certain editions of Windows 7, labelled as “E”, don’t include Internet Explorer by default.

To install Internet Explorer, use one of the following downloads:

“NTLDR is missing” after installing updates

The final version of the Windows Update Agent released for Windows XP has a bug that triggers a limitation of XP’s bootloader (NTLDR). This seems to only occur on Windows XP Home Edition and Embedded, and is not an issue on Professional. Specifically, the bug is that the installer enters an infinite loop of creating temporary folders in the root of C:, which causes the NTFS Master File Table (MFT) to become too fragmented for NTLDR’s master boot record (MBR) program to make sense of. This is covered by KB320397, a patch for XP SP1 that was later built into XP SP2, but the issue still seems to occur despite the fix.

Legacy Update 1.6 and later work around this by using an older version of the Windows Update Agent without this bug. If you’ve installed an older version of Legacy Update, or manually installed Windows Update Agent 7.6.7600.256, you can resolve this in one of a few ways: