FIX: Unregistering Msxml3.dll Leaves Msxml2.ServerXMLHTTP Key in the Registry

Article translations Article translations
Article ID: 291271 - View products that this article applies to.
This article was previously published under Q291271
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

Unregistering the Microsoft XML version 3.0 parser, Msxml3.dll, does not remove the following key from the registry:
HKEY_CLASSES_ROOT\Msxml2.ServerXMLHTTP
even though a message states that the DllUnregisterServer function in Msxml3.dll succeeded.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Microsoft XML 3.0 Service Pack 1.

For additional information on other fixes included in Microsoft XML 3.0 Service Pack 1, click the article number below to view the article in the Microsoft Knowledge Base:
292935 INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 1
For the latest information and downloads of MSXML, refer to the following MSDN Web site at:
http://msdn.microsoft.com/xml/default.asp

MORE INFORMATION

To unregister Msxml3.dll, run the following command from a command prompt:
regsvr32 -u msxml3.dll
Other registry entries specific to Microsoft XML (MSXML) 3.0 are removed, including the following:
HKEY_CLASSES_ROOT\Msxml2.ServerXMLHTTP.3.0

Properties

Article ID: 291271 - Last Review: February 27, 2014 - Revision: 1.4
APPLIES TO
  • Microsoft XML Parser 3.0
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbmsxml300sp1fix kbmsxmlnosweep KB291271

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com