Skip to main content

Release History

The best version of Legacy Update to use is always the latest version. However, if you have a specific need for an older version of Legacy Update, you can find them here.

Learn more about Legacy Update and download the latest version, Legacy Update 1.13, on the homepage.

Important

If nothing happens when you open Legacy Update setup on Windows XP, follow these steps to work around a Windows bug.

This release improves handling of numerous edge cases you might run into while using Legacy Update.

  • Adds integrity verification of files downloaded by Legacy Update setup. This ensures downloaded files are not corrupt, blocked by a firewall, or tampered with.
  • Adds detection for a currently running Windows update, to ensure Legacy Update setup doesn’t try to start a conflicting update installation.
  • Legacy Update now detects when Windows has been upgraded (such as from Windows XP to Windows Vista), so it can display a message that it needs to be reinstalled to function correctly.
  • Installation of root certificates is now skipped if it has already been done in the past 30 days. Updates to the root certificate store are infrequent, typically only occurring a few times per year.
  • Adds logging that can help to diagnose issues in Legacy Update.
  • Windows 2000:
    • Fixes “Access is denied” errors when installing Legacy Update on Windows 2000.
  • Windows XP:
    • When upgrading Windows XP Media Center Edition or Tablet PC Edition from RTM or SP1, Legacy Update now installs Service Pack 2 in between, rather than Service Pack 1a. This upgrades Media Center Edition to 2004, and Tablet PC Edition to 2005.
    • When enabling Windows Embedded 2009 updates on Windows XP, Legacy Update now hides the notoriously broken KB2686509 update.
    • When Windows Embedded 2009 updates have already been enabled on hardware that will run into compatibility issues, Legacy Update setup will show a warning.
  • Windows Vista and Server 2008:
    • Installing the Windows Server 2008 servicing stack is now split out into a separate “Prepare for Extended Security Updates” checkbox.
      We’re reverting to using the latest general public servicing stack for Windows Vista, released in 2012. While there are some security and performance benefits to using the Windows Server 2008 servicing stack from 2019, it also brings some compatibility issues, so we now let you decide if you want this. This only applies to new installations of Legacy Update, and won’t change existing ones.
    • Adds a prerequisite update to Hyper-V, KB950050, required for Windows Server 2008 SP1 with Hyper-V to be correctly upgraded to SP2. (Contributed by @Goldfish64 - thanks!)
    • Fixes installation of Windows Vista Service Pack 1 getting stuck at “Configuring updates…”.
    • Works around bugs in the Windows Vista Service Pack 1 and 2 installers causing it to not check if the system has sufficient disk space available, and to fail for languages other than English, French, Spanish, German, and Japanese.
    • Fixes a Windows bug causing the wallpaper from setup mode to persist into the user’s desktop on some editions of Windows Server 2008.
    • Fixes a crash when clicking “Install Updates” on the website.
  • Windows 7 and Server 2008 R2:
    • Adds an option to install the Windows 7 Convenience Update Rollup on new installations of Windows 7. This is a bundle of 66 updates released prior to April 2016.
      While this rollup helps you to get up-to-date faster, it contains updates that introduce telemetry features that some users find undesirable. As such, this option is not selected by default.
    • Adds support for installing Windows Server 2008 R2 Service Pack 1 on Itanium systems.
  • Windows 10 and 11:
    • Fixes some updates not being staged for installation when restarting the system via the Legacy Update website.
  • General fixes:
    • Fixes crashing on 486 processors. (Contributed by @renodr - thanks!)
    • Fixes /norestart flag not working.
    • When running on Windows Server Core, Legacy Update setup now skips features that are not applicable - particularly, Windows Server Core lacks Internet Explorer, so the ActiveX control is skipped. (Contributed by @Goldfish64 - thanks!)
    • Adds support for running Legacy Update setup in Windows audit mode, which is used to prepare an installation of Windows in advance of it being given to an end user.
    • Adds detection for Terminal Services Execute mode on Windows Server. Legacy Update setup must be run in Install mode. We now provide an option to switch to Install mode automatically.

A huge thank you to everyone who contributed towards our fundraiser for a renewed code signing certificate, which we’re now using for this release, and another thanks to those who helped make our new Microsoft Download Center Archive a big success!

Files
LegacyUpdate-1.13.exe
  • SHA1: e39ce17ac8d3cba0c090db274110149609d0ae86
  • SHA256: aa6d892cb6fb856485a9c26b6239df174d616e65dc88c174b752a92a45b570a1

Important

If nothing happens when you open Legacy Update setup on Windows XP, follow these steps to work around a Windows bug.

This release fixes some issues from Legacy Update 1.12. Refer to that release for the list of major changes in 1.12.

  • Fixes SSL connection errors on Windows 2000, Windows XP, and Windows Server 2003.
  • Fixes the website not detecting when a restart is required on Windows 2000.
  • Fixes setup not correctly resuming after restarting the system.
  • Fixes “Permission to access the Windows Update service was denied.” errors after clicking Yes on the User Account Control prompt.
  • Fixes a Windows bug causing the wallpaper from setup mode to persist into the user’s desktop.

Our code signing certificate expires less than a week from now. We are looking at free options, but may need to purchase the same certificate again for $369 USD. Your support is appreciated to help us reach this goal and continue working on Legacy Update for another 2 years.

Files
LegacyUpdate-1.12.1.exe
  • SHA1: 703200d55c0d070a558fb41d92f65210f0ca5a8d
  • SHA256: fd8d52754b00e8661b64c42739790b42d19cb24c4ddd2d33719ee23db9ab710c

Important

If nothing happens when you open Legacy Update setup on Windows XP, follow these steps to work around a Windows bug.

Legacy Update 1.12 features a significant rewrite of our ActiveX control, and a handful of other bug fixes.

The rewrite allows us to more easily work on the project, and ensures we can continue providing stable releases for the foreseeable future, despite Microsoft recently breaking the Windows XP-compatible compiler included with Visual Studio 2022.

A note about Windows 10: Support for Windows 10 ends on 14 October 2025. We currently don’t expect issues with any version of Windows 10 that will require us to add specific features for it. If you intend to continue using Windows 10, consider enrolling in the free Extended Security Updates (ESU) program to receive another year of security fixes.

  • Legacy Update’s ActiveX control has been rewritten to be built with the latest open-source MinGW compiler, rather than Microsoft’s Visual Studio. This brings 17 years of compiler improvements, and halves the (already small) installation size of Legacy Update.
  • Adds a partial workaround for very slow installation of .NET Framework updates on Windows 2000, XP, Vista, and 7. Rather than the global assembly cache (GAC) being rebuilt by each individual .NET Framework update, it will now be deferred until after the Installing Updates window is closed. This works for most, but not all, .NET Framework updates. (This issue was fixed in Windows 8.)
  • Adds a countdown timer before Legacy Update setup automatically restarts the computer. This also allows you to restart later.
  • Adds compatibility warning messages when One-Core-API is installed, or NNN Changer for NT 5.x (NNN4NT5) is active.
  • If you run into issues with Legacy Update setup during the Windows setup mode stage, you can now enter Safe Mode to break out of the process.
  • Windows 2000:
    • Fixes setup not correctly offering Service Pack 4 when running on Service Pack 3.
  • Windows XP and Windows Server 2003:
    • Fixes incorrect download being used for Windows XP SP1a for Chinese (Hong Kong).
    • Fixes setup redownloading the Windows Update Agent after upgrading Windows XP to SP3 or Windows Server 2003 to SP2.
    • Fixes incorrect OS names being displayed for some editions.
  • Windows Vista and Windows Server 2008:
    • Fixes setup incorrectly downloading Service Pack 1 for Windows Server 2008, which is already Service Pack 1.
    • Known issue: When installing Windows Vista Service Pack 1, Legacy Update will remain stuck at “Configuring updates…” forever. If this happens, wait for all hard drive activity to stop, then force restart your computer. You can run Legacy Update again to resume where it left off.
  • Windows 8 and Windows Server 2012:
    • Adds support for enabling receiving additional updates from Microsoft Update.
  • Windows 10 and Windows 11:
    • Fixes an unnecessary system restart when running setup while Windows has updates pending to be installed.
  • General fixes:
    • Fixes the ActiveX control not being updated when the Legacy Update website is open in 32-bit Internet Explorer on a 64-bit system.
      This particularly affects Internet Explorer 11, which runs as 32-bit by default.
    • Better handles “Unable to write to LegacyUpdate.dll” errors when the Legacy Update website is open in Internet Explorer.
    • Better handles detection of Internet Explorer being uninstalled, particularly on Windows XP, 10, and 11.
    • Fixes “Open File - Security Warning” dialog at the final stage of setup.
    • Fixes multiple Windows Update settings dialogs appearing when clicking “Settings” or “Pick a time to install updates” on the website.
    • Fixes the Notepad window being invisible when clicking “View Log File” on the website.
    • Updates NSIS to version 3.11, which addresses a privilege escalation vulnerability (CVE-2025-43715).

Our code signing certificate expires less than 2 weeks from now. We are looking at free options, but may need to purchase the same certificate again for $369 USD. Your support is appreciated to help us reach this goal and continue working on Legacy Update for another 2 years.

Files
LegacyUpdate-1.12.exe
  • SHA1: 1feb190a00df44ef7098bfda978a74aa11fd7b01
  • SHA256: 44ccf9df905b4e7736e9afbfc023f903e647a536d25d9b435824798a9e20711b

Important

If nothing happens when you open Legacy Update setup on Windows XP, follow these steps to work around a Windows bug.

Legacy Update 1.11 makes some quality-of-life improvements, and comes with numerous fixes for issues users have run into.

  • Features:
    • Reduces reboots required when installing updates from Legacy Update Setup.
    • Installation of root certificates has been rewritten with our own faster implementation, rather than using Microsoft’s.
    • Adds /v flag that makes the details log slightly more verbose.
  • Windows 2000:
    • Legacy Update Setup now installs Update Rollup 1 for Windows 2000 Service Pack 4, which includes all updates released for SP4 until April 2005.
    • Fixes the system freezing after Legacy Update restarts Windows into setup mode.
    • Works around “explorer.exe has generated errors and will be closed” errors after installing Internet Explorer 6. To continue Legacy Update Setup, you may need to manually log in after Windows restarts.
    • Better handles being used on Windows 2000 Datacenter Server. This edition is not officially supported by the Windows Update Agent, and installing it always fails. We’re looking into supporting it in future, but for now, Legacy Update can only help you to install Service Pack 4 on Datacenter Server.
    • Fixes the tooltip on the Legacy Update Start menu shortcut displaying incorrectly on Windows 2000.
  • Windows XP:
    • Adds support for displaying the correct operating system name in later variants of Windows XP and Server 2003. (Partly contributed by @Goldfish64 - thanks!)
  • Windows Vista:
    • Fixes “Not Found (404)” when downloading KB4490628 on Itanium Windows Server 2008 R2.
  • Windows 7:
    • Fixes infinite reboot loop when installing the initial set of updates on French, Portugese (Brazilian), Russian, and likely other language copies of Windows 7 SP1.
    • Fixes a “Forbidden (403)” when installing on Windows Embedded 7 and 8.
  • General fixes:
    • Fixes your selections not being saved when Legacy Update Setup needs to restart the system.
    • Fixes “Copy failed” warnings in the setup details log. These were harmless, but still confusing.
    • Fixes the uninstaller not being installed. (Contributed by @Mystyle-48 - thanks!)
    • Fixes incorrect detection of activation status on Windows Vista and later, and Windows XP Professional x64 Edition. (Contributed by @renodr and @Goldfish64 - thanks!)
    • Fixes “Restart” button on the website not working in some cases.
    • Fixes Legacy Update icon not appearing in the User Account Control dialog.
    • Fixes excessive “This website would like to run Legacy Update” and “A website wants to open web content using this program on your computer” prompts in Internet Explorer 11.
    • Fixes the system becoming locked out when running Legacy Update from Sysprep/Audit Mode.
    • Adds extra protection against DLL hijacking attacks.

Thanks for using Legacy Update! I’m currently looking at acquiring PowerPC, Windows Phone, Surface, and maybe even Windows Mixed Reality hardware to review what Legacy Update can do to improve these discontinued products, so your support is always appreciated.

Files
LegacyUpdate-1.11.exe
  • SHA1: 75f8a05ff04f725521f7f46ad9c50c454ea39d20
  • SHA256: b826a873c50c9cbf6cb52f6bfbf7efad03dbf56cf0928504e1b2b7100aab29ac