Specifically, the file is C:\Windows\SysWOW64\msxml4.dll.  Version 4 of the MSXML file is no longer supported by Microsoft.

I don't believe MAS 500 used any of those DLLs.  Hopefully, someone from Sage is monitoring this forum and can give a definitive answer to that.  Is there a specific MAS 500 customization you are working on that used these DLLs?  If so, have you considered building COM complaint .NET Assemblies to do the XML work and simply set a reference to these within VB 6?

We installed msxml4 in Sage 500 ERP v7.40 and all current versions. MSXML6.0 is installed by the windows OS. (Refer: en.wikipedia.org/.../MSXML)

We do reference MSXML2.6, MSXML4.0 and MSXML 6.0 in the following projects. I don't know the specific use, if at all (and we just need to remove), or if we need to update. We periodically review our code but may not until we find an issue or a new feature to use.

This is a quick look at our build, not a review of the code and the usage.

MSXML 2.6

CI Rename IDs(ci/cizua001/cizua001.vbp)

CI Rename IDs Component (ci/cizubdl1/cizubdl1.vbp)

MSXML 4.0

SO External Shipment Integration (SO/soextshipintegration/soextshipintegration.vbp)

String Utilities (commondll/StringUtils/stringutils.vbp)

DataView Utilities (commondll/DataViewUtils/dataviewutils.vbp)

MSXML 6.0

Credit Card Helper (cc/CCHelper/cchelper.vbp)

Set Crystal Database Name UI (sm/Crystal Database Utility/User Services/prestocrystaldatabase.vbp)

Set Crystal Database Name Dll (sm/Crystal Database Utility/Business Services/prestocrystaldatabasebs.vbp)