PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutemsxml4-KB973688-enu.exe is the English-language installer for Microsoft XML Core Services (MSXML) 4.0 Service Pack 2 update KB973688. It is a legacy Microsoft security/update package, not a general Windows application. It is normally relevant only on a computer that has MSXML 4.0 SP2 installed.
The file is trustworthy when it was downloaded through Microsoft Update, the Microsoft Update Catalog, or a Microsoft-hosted download page and its digital signature identifies Microsoft. A filename by itself proves nothing, because any executable can be renamed. The manual checks and repair procedure below let you establish what you have, install the correct package, and decide whether an old installer can be removed.
As an Amazon Associate I earn from qualifying purchases.
What msxml4-KB973688-enu.exe is
MSXML is a Microsoft XML parser and runtime. Applications use it to read and process XML, XHTML, and related data. Some older business, media, administration, and setup programs were written for MSXML 4.0 rather than the XML components built into newer Windows releases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsKB973688 is an update for MSXML 4.0 Service Pack 2. The “enu” part of the filename identifies the English-language package. Microsoft’s Update Catalog lists KB973688 as a critical update for legacy releases including Windows XP, Windows Server 2003, Windows Vista, Windows 7, and Windows Server 2008 variants. Those catalog entries are split by processor architecture, so an x86 package and an x64 package are not interchangeable.
#1 Best Overall
| Filename element | Meaning |
|---|---|
msxml4 |
Microsoft XML Core Services 4.0 |
KB973688 |
The Microsoft Knowledge Base update identifier |
enu |
English-language installer |
.exe |
A Windows executable installer |
Installing this package does not turn MSXML into a general-purpose Windows feature. If no program on the computer uses MSXML 4.0 SP2, Windows may never offer KB973688 and an application may not need it. Microsoft support describes the update as being offered when MSXML 4.0 SP2 is present.
Is the file safe?
It can be safe, but the name is not proof. A copy obtained from Microsoft Update, the Microsoft Update Catalog, or a Microsoft-hosted Download Center page is the expected distribution path. A copy from an unknown mirror, a pop-up, an “EXE fixer” page, or an unsolicited attachment should be treated as untrusted until it passes verification.
Check where the file came from
- In File Explorer, right-click the executable, choose Properties, and note the full location. A file in your normal download folder can be legitimate if you deliberately downloaded it; a randomly named copy in a temporary or user-profile directory deserves more scrutiny.
- Compare the download source with Microsoft Update, the Microsoft Update Catalog, or a Microsoft-hosted download page. Do not use a third-party replacement when the catalog has the package.
Check the Microsoft signature
- Open the file’s Properties dialog.
- Select Digital Signatures.
- Select the signature, choose Details, and confirm that Windows reports a valid signature from Microsoft.
- If the tab is missing, the signature is invalid, or the signer is unexpected, do not run the file. Obtain a fresh package through Microsoft’s servicing channel instead.
A valid signature establishes who signed that particular file; it does not make every copy with the same filename legitimate. Keep current endpoint protection enabled and scan a suspicious copy before opening it. Microsoft’s Download Center describes the security rationale for an MSXML update this way: “A security issue has been identified in Microsoft XML Core Services (MSXML) that could allow an attacker to compromise your Windows-based system and gain control over it.”
Can you delete msxml4-KB973688-enu.exe?
Usually, you may delete the installer executable after a successful installation if it is only a copy in Downloads, Desktop, or a temporary folder. Removing that package file does not uninstall MSXML. Keep it temporarily if you expect to reinstall the update, need it for an offline repair, or are still diagnosing a failed installation.
Do not confuse the installer with the runtime
The installer name ends in .exe. The installed runtime includes files such as Msxml4.dll. Deleting the DLL manually can break legacy applications that depend on MSXML 4.0. Do not remove or rename that DLL merely because the update executable appears in a search result.
Safe cleanup procedure
- Confirm that the update completed and that Windows has been restarted if the installer requested it.
- Check the installer’s Properties and location so you do not select a system DLL or an application file with a similar name.
- If the file is an old download, delete it and empty the Recycle Bin only after you are satisfied that no repair or rollback requires it.
- If Windows Update continues to offer KB973688, deleting the old executable will not solve the problem; follow the installation and verification steps below.
Why KB973688 keeps failing or reinstalling
A repeated offer is generally an installation-state problem, not evidence that the executable itself is malware. Microsoft troubleshooting guidance identifies two common explanations: the installation failed, or a required file was not updated until after a restart.
The most common causes
- MSXML 4.0 SP2 is absent or damaged. The update targets that runtime. A computer that never had it may not be a valid target, while a partially removed installation can confuse servicing.
- Wrong architecture. The catalog supplies architecture-specific packages. An x86 package is not a substitute for an x64 package, and the applicable package depends on the Windows and MSXML installation.
- Restart pending. Files in use by an application or by Windows servicing may not be replaced until the computer reboots.
- Interrupted or incomplete servicing. A shutdown, installer interruption, or permissions problem can leave Windows believing that the update is still required.
- Application dependency. A legacy program may load MSXML while the update is being applied, preventing replacement of a file.
- Unsupported modern-system assumption. KB973688 is documented for legacy Windows and MSXML 4.0 SP2. On a newer Windows release, first identify which application installed MSXML and use that application’s supported maintenance instructions.
Information to record before changing anything
Write down the Windows edition and service-pack level, whether the system is x86 or x64, the exact text and number of the error, whether MSXML 4.0 SP2 appears to be installed, and whether the computer has restarted since the last attempt. Error 652 and similar servicing messages describe an installation state; they do not, by themselves, show that the executable is malicious.
Manual fix: install the correct KB973688 package
The documented recovery path is to obtain the matching package from Microsoft’s catalog or servicing infrastructure, install it with suitable rights, restart, and verify the MSXML file version. Perform these steps in order.
1. Establish that the update applies
- Identify the Windows edition and architecture in Settings or Control Panel > System. On older systems, the System window labels the operating system type as 32-bit or 64-bit.
- Check whether the computer or the affected application actually uses MSXML 4.0 SP2. If the runtime is not installed, KB973688 may not apply; installing a random copy merely because the filename appeared in a search is not a solution.
- Close programs that may parse XML or use the affected legacy application. Save work before beginning the installation.
2. Obtain the package from Microsoft
- Open the Microsoft Update Catalog or the Microsoft servicing/download channel that supplied the update.
- Search for KB973688 and read the product, operating-system, language, and architecture details for each result.
- Select the English package that matches the installed MSXML 4.0 SP2 and the computer’s architecture. Do not assume that the first result is correct.
- Save the executable locally, then inspect its Properties and Digital Signatures tab before running it. The signer should be Microsoft and the signature should be valid.
3. Run the installer with appropriate rights
- Right-click the downloaded executable and choose Run as administrator when that option is available. Supply administrator credentials if Windows requests them.
- Follow the installer’s prompts. If it reports that the update is not applicable, stop and recheck the operating-system, architecture, and MSXML 4.0 SP2 details rather than forcing a different package.
- For supported deployment scenarios, Microsoft’s security bulletin documents the installer switches
/quietand/norestart./quietsuppresses the normal user interface;/norestartprevents an automatic restart so an administrator can schedule one. Use switches only when you understand the deployment context and can restart afterward.
4. Restart Windows
Restart when the installer requests it, even if the desktop appears usable. A reboot allows Windows to replace files that were locked by a running service or application. Do not interrupt the restart and do not immediately delete the installer while Windows is completing pending servicing.
5. Verify the installed file
- After the restart, open File Explorer and enter
%SystemRoot%System32in the address bar. - Locate
Msxml4.dll, right-click it, choose Properties, and open the Details tab. - Check the file version. Microsoft’s troubleshooting guidance cites 4.20.9870.0 as the version to confirm after manual installation.
- Run the application that originally reported the MSXML error. If it still fails, record the new message rather than repeatedly installing the same executable.
The cited version check is a practical confirmation for the documented legacy scenario. If your package, operating system, or architecture places the runtime differently, use the package’s Microsoft documentation rather than deleting files or copying a DLL from another machine.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do if the update still fails
If Windows Update offers KB973688 again
First verify that the computer was restarted and that Msxml4.dll reports the expected version. If the version is correct but Windows still displays the offer, record the update history entry and the exact operating-system and architecture details. A repeated offer can reflect stale detection data or a package that did not update the file Windows is checking; it is not fixed by deleting a download from the Downloads folder.
If the installer reports that it is not applicable
Recheck whether MSXML 4.0 SP2 is installed, whether the language is English, and whether the x86 or x64 package matches the system. KB973688 is not a general update for every MSXML release. Installing MSXML 4.0 SP2 or another version solely to make this executable run can create a new application-compatibility problem, so identify the program’s documented prerequisite first.
Best Value
If files are in use
Close the application that uses XML, stop only services you recognize as belonging to that application, and retry after a restart. Do not terminate random Windows processes or delete Msxml4.dll to force the installer through. If a security or management product blocks the package, consult that product’s event log and your organization’s administrator rather than disabling protection indiscriminately.
If an error code persists
There is no single universal fix for every KB973688 error across the legacy Windows versions listed in the catalog. Keep the exact code, installer log if available, Windows edition, architecture, MSXML version, and restart status together. Those details determine whether the next step is a Microsoft servicing repair, an application-specific repair, or removal of an obsolete application that no longer needs MSXML.
MSXML errors after installation
An application can still display an MSXML error even when KB973688 installed correctly. The program may require a different MSXML major version, a different processor architecture, a particular registration state, or another dependency. The update only addresses the MSXML 4.0 SP2 package it targets; it is not a repair for every XML-related failure.
- If one older program fails while other programs work, check that program’s vendor documentation and installer requirements.
- If several programs fail after a system change, review the update history and the version of
Msxml4.dllbefore changing files. - If the problem began after removing software, reinstall the affected application through its supported installer rather than downloading a standalone DLL.
- If the computer is now running a modern Windows release, identify the legacy application that brought MSXML 4.0 onto the system and follow its current support guidance. The historical KB973688 package should not be treated as a universal modern-Windows component.
Choosing a recovery route
| Route | Source trust | Architecture control | Dependency check | Best use |
|---|---|---|---|---|
| Windows Update | Microsoft servicing channel | Windows selects the applicable package | Usually detects the installed prerequisite | Normal supported update flow |
| Microsoft Update Catalog, manual install | Microsoft catalog | You select the matching x86 or x64 entry | You must confirm MSXML 4.0 SP2 and the operating system | Repeated offers, failed automatic installation, or controlled deployment |
| Unknown mirror or “fixer” download | Not established | May be mislabeled | May bundle the wrong runtime or altered executable | Not recommended when Microsoft’s package is available |
When to stop troubleshooting
Stop and seek platform or application-specific support if the Microsoft signature is invalid, the package does not match the operating system, the file version remains unchanged after a restart, or the affected program is business-critical. Provide the exact error, Windows edition and architecture, MSXML installation state, package source, and the version shown for Msxml4.dll. That evidence is more useful than repeatedly downloading files with similar names.
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can look for common Windows issues, adjust selected system settings, clean temporary and cache files, and provide an app-crash log. It complements antivirus software rather than replacing it; results vary and no tool repairs every crash. It runs on Windows 11, 10, 8, and 7, with a free trial by category for at least two days before a subscription.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
