error 0x800c005 (Jupiter's fixes don't help) part 2

[Jupiter Jones [MVP]]

Doug;
1. How did you Repair IE6?
Add/Remove Programs Repair option?
Download again from this link and install:
http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.asp
Reboot computer
Disable all unnecessary applications including antivirus.
Install IE6
Reboot

2. Create a new profile with Administrator access

3. Make sure you followed everything on this list including all of
Step P "Windows Update Checklist":
http://www3.telus.net/dandemar/0x800c0005.htm

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/

"DougBiss" <anon...@discussions.microsoft.com> wrote in message
news:3B09FAC6-38BE-4227...@microsoft.com...
> (Posted as new thread so it doesn't get lost)
>
> Thanks for the reply... I will be as complete as possible in my
descriptions to see if anyone notices something unusual. Sorry if it's
a bit long. :)
>
> I'm running Windows 2000 with all updates installed up to and
including last weeks.
> I'm on a corporate network. We run the windows updates on machines
individually. We also run Symantec Anti-Virus, which I have completely
uninstalled (including removing the
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec entry as suggested).
>
> My problem started sometime after installing the most recent batch
of updates. I cannot be sure that it was immediately after the
updates, but I'm fairly certain it was. A few other users here are
having the same problems. The ones who aren't having the problem may
be people who haven't been on top of their updates.
>
> I have not installed any new software since windows update was
working properly. There have not been any network changes since it was
working properly. My only apparent symptom is an inability to access
ANY https site. When checking the windows update log, the only error
is "Querying software update catalog from
https://v4.windowsupdate.microsoft.com/getmanifest.asp (Error
0x800C0005)".
>
> I have done the following:
> Checked for viruses using the most recent definitions.
> Ran the latest Adaware version, which came up clean.
> Uninstalled my Google popup blocker.
> Uninstalled (and cleaned the registry) of Symantec Anti-Virus.
> Uninstalled the most recent Hotfixes. Tested for change (there was
none) and reinstalled them manually.
> Ran Q831167.exe to eliminate the Wininet possibility.
> Verified that Cipher Strength was 128.
> Cleared the cache, cookies and history.
> Verified correct system date and time.
> Checked the IE language setting.
> Uninstalled and reinstalled IE6. Repair failed, giving these
reasons:
> Error occurred calling "DllRegisterServer" in
"C:\WINNT\system32\dxtrans.dll". (HRESULT = 80040154)
> Error occurred calling "DllRegisterServer" in
"C:\WINNT\system32\dxtmsft.dll". (HRESULT = 80040154)
> Error occurred calling "DllRegisterServer" in
"C:\WINNT\system32\tdc.ocx". (HRESULT = 80040154)
> I subsequently renamed these files, removed IE6 again, and
reinstalled. New files of the same name reappeared and the repair
option generated identical errors.
> I ran Sfc.exe and there were no problems reported.
> I went through all IE settings and found none that disagreed with
anything I have seen here or elsewhere.
> I entered the following at the run line:
> regsvr32 softpub.dll
> regsvr32 wintrust.dll
> regsvr32 initpki.dll
> regsvr32 dssenh.dll
> regsvr32 rsaenh.dll
> regsvr32 gpkcsp.dll
> ** regsvr32 sccbase.dll
> ** regsvr32 slbcsp.dll
> ** regsvr32 cryptdlg.dll
> Those last three did NOT work when I attempted it. Since these were
suggested as an XP fix and not a Win2K fix, I don't know if this is
relevant.
> I looked into the FIPS setting but did not find one on Win2K.
Perhaps it is XP only.
> I also attempted to Clear SSL State under Certificates, as suggested
somewhere, but could not find this option in Win2K.
>
> I think that is everything I've tried so far. The only other idea I
have is to create a different account on this machine to see if it has
the same problem, but that hasn't been done yet.
> Are there any other suggestions or anything that I did wrong or may
have missed?
>
> Thanks again,
> Doug
>