[salpern]

When I try to register mshtml.dll, I get a message that says "mshtml.dll loaded, but DllRegisterServer entry point not found." I've searched everywhere for a solution but have gotten nowhere. Help! I can't update (or even register, after reinstalling, IE7 - not to mention uninstalling and trying to get IE6 back. Please email me at salpern@wideopenwest.com - unless this site also sends an email. Sandee

[devil_himself]

What is The Actual Problem .... Are Windows Update Not Installing

[salpern]

That's right - I can't use Microsoft Update - it won't, apparently, connect. I also couldn't ping the site, but I suppose Microsoft might have blocked pinging.

[devil_himself]

see if it helps

Some Solutions for fixing Windows Update
http://forums.techguy.org/windows-nt...ws-update.html

[devil_himself]

DllRegisterServer entry point not found

The DLL In Question is not a COM nor an ActiveX component.

COM and ActiveX components have registration -->DllRegisterServer and unregistration -->DllUnregisterServer functions that are called By --> Regsvr32.

[salpern]

I got your link - will explore. Thanks.

[salpern]

I did all you suggested on that page and I still can't reach www.update.microsoft.com, either via the Windows Update web page or by pinging. You told the other person that "the local Windows Update engine files" might be corrupted. I changed the two file names you suggested - was that the same thing? Please advise, what do I do now?

[devil_himself]

What Exactly Happens When You Navigate To - http://www.update.microsoft.com/

Is Automatic Updates Enabled

[ignatiusp]

OS: XP IE: 7
DllRegisterServer entry point not found
When I try to register mshtml.dll, I get a message that says "mshtml.dll loaded, but DllRegisterServer entry point not found."
-- Removed IE7 and Windows Desktop Search. I was bale to connect and update MS updates with IE6

[salpern]

It took a Microsoft Tech at 800-PCSAFETY to figure it out, but, as it turned out, I downloaded a too-early version of Eset's NOD32 antivirus, version 3.0, which I have since reinstalled (the updated version) and is working well, As a temporary fix, I uninstalled the defective upgrade and installed version 2.7 and, about 6 weeks later, reinstalled the upgrade which is now working quite well. All that happened in January and February. It is now August. Even the Microsoft tech had difficulty resolving the problem: I'm glad they don't charge for problems with Windows Update/Microsoft Update. It took a while!