"Windows Error (0x800A138F)" On Win2000pro Update Attempt.

  • Thread starter Thread starter EtAl
  • Start date Start date
E

EtAl

I noticed I wasn't the only one who got this error. My PC
is:

Intel(R) Pentium
(R) 4 CPU 1.70GHz
AT/AT Compatible
523.760KB RAM

So it may not be specific to any one device.
 
Did you ever find a solution to this problem??
I am having the same problem myself. I would really
appreciate a solution if you have one! Please e-mail me at
(e-mail address removed)- I would really appreciate that!

Naomi
 
We need to check to see if any errors are being reported.

Let's view the Windows Update log file
Copy and paste "%windir%\windows update.log" (w/o the quotes)
into the Internet Explorer address bar and hit Enter.
Scroll down to the current date and look for the error being reported.
Next, Look for the error message in the Windows Update Troubleshooter:
http://v4.windowsupdate.microsoft.com/troubleshoot/
Please try the suggestions listed. If error persists please post the error
message from the log file.
 
hello.

i don't see "0x800C0005" on the Windows Update Troubleshooter: any
tips?


thanks









page On Mon, 3 Nov 2003 15:09:04 -0800, "Lucy [MS]"
 
Are you behind a squid proxy server?

Big J said:
hello.

i don't see "0x800C0005" on the Windows Update Troubleshooter: any
tips?


thanks









page On Mon, 3 Nov 2003 15:09:04 -0800, "Lucy [MS]"
We need to check to see if any errors are being reported.

Let's view the Windows Update log file
Copy and paste "%windir%\windows update.log" (w/o the quotes)
into the Internet Explorer address bar and hit Enter.
Scroll down to the current date and look for the error being reported.
Next, Look for the error message in the Windows Update Troubleshooter:
http://v4.windowsupdate.microsoft.com/troubleshoot/
Please try the suggestions listed. If error persists please post the error
message from the log file.
Click to expand...
Click to expand...
 
Andrew Paiti said:
Are you behind a squid proxy server?
Click to expand...

We are and we get error 0x800A138F. I remember this has to do
something with the cache not updating the new uident.cab from the
windowsupdate site. Maybe clearing the cache will work.
 
Back
Top