Microsoft XML Parser (MSXML) and XML Core Services


A vulnerability is encountered when manually installing the agent for the Microsoft XML Parser (MSXML) or XML Core Services.


Manually installing the Unitrends agent creates an alert for a vulnerability in the OS related to the the Microsoft XML Parser (MSXML) or XML Core Services similar to:


The remote host contains one or more unsupported versions of the Microsoft XML Parser (MSXML) or XML Core Services.


Lack of support implies that no new security patches for the product will be released by the vendor. As a result, it is likely to contain security vulnerabilities.


Note that support for MSXML 3.0 and 6.0 is based on the support policy of the operating system on which it is installed. Support for MSXML 5.0 is based on the Microsoft Office lifecycle policy.


Upgrade the software packages responsible for the unsupported DLL versions or upgrade to a supported version of Windows (Vista / 2008 or later). Alternatively, uninstall the outdated MSXML or XML Core Services.

See Also


  • Path : C:\Windows\SysWOW64\msxml4.dll
  • File version : 4.20.9818.0
  • XML Core version : 4.0 Post SP3 (KB2758694)
  • EOL date : 2014/04/12
  • EOL announcement :
  • Supported versions : 5.20.1076 (Office 2007) / 6.0 or later on a supported version of Windows (Vista / 2008 or later).


These components are included in our universal agent in order to support some 2000/2003 server systems as well as XP. The components are necessary to launch our client-side UI used for Legacy SQL support, Baremetal media creation, and more. At this time we are unable to remove these components while we continue to support some legacy OS. We expect in the future to depreciate support for some OS that are no longer supported by Microsoft itself and at that time we can remove those components, but a timeline has not been communicated at this time.


On most systems, after installing our agent you can upgrade to the current msxml release, then safely remove the msxml4.dll without production impact if the security risk is not currently acceptable.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section