SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: nspolar who wrote (43211)9/30/2004 9:13:07 AM
From: Lost1  Read Replies (2) of 110652
 
WIN XP update first gives you : We've made improvements to our website. To download the new version of the software and begin using Windows Update, please click Install Now.

after attempting I get:

[Error number: 0x80070002]
Windows Update has encountered an error and cannot display the requested page. You may find the following resources helpful in resolving the problem:


a google search yields
support.microsoft.com

"Error Code: 0x80070002" error message cites license-checking issue after upgrade on Dell computer
View products that this article applies to.
This article was previously published under Q310794
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
When you start Microsoft Windows XP, you may receive the following error message:

A problem is preventing Windows from accurately checking the license for this computer. Error code: 0x80070002.
CAUSE
This issue can occur if one of the following conditions is true:
The default security provider in Windows XP has been changed.
The system drive letter has changed.
The security provider issue has been reported with Dell computers on which the Dell Assistant software is installed.

NOTE: This issue can be caused by any software that changes the default security provider. It is not limited to Dell computers or the Dell Assistant software.
WORKAROUND
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this issue, use the appropriate method.
Reset the Default Security Provider in Windows XP
To reset the default security provider in Windows XP, delete the relevant keys in the Windows registry. To do this:
Start the computer. Press the F8 key during startup to start the computer in Safe mode.
Start Registry Editor (Regedt32.exe).
Delete the following keys in the Windows registry:
HKEY_USERS\.DEFAULT\Software\Microsoft\Cryptography\Providers
HKEY_USERS\S-1-5-20\Software\Microsoft\Cryptography\Providers

Quit Registry Editor.
Restart the computer.


only problem is that the system in question isn't a DELL

further investigation turned up this:
updatexp.com

What Is The 0x800A138F problem?

I do NOT want to get too technical in this support article. Simply because most of you reading this, want a solution and not a technical briefing! Also, many of you are new(ish) to Windows XP and I am not here to confuse you either...

Essentially when your computer communicates with the Windows Update website. It uses TWO technologies called:

Active X - to interact with the Microsoft site. The first time you visit the Update website, using your profile, you are asked if you will accept the Windows Update Control Package (the Active X control) onto your machine.

SSL (Secure Socket Layer) - A method of data encryption used by Internet Explorer.

Now this general error message 0x800A138F, that some folks get when they visit Windows Update, has been around for a while. BUT, when the MSBlast virus was unleashed Microsoft changed a few things at the main update website. One of them was to use Akamai for additional bandwidth and this connectivity is exclusively using HTTPS (SSL) for the downloading of the update catalogue. It is since then that we have seen an escalation in the number of 0x800A138F error messages!

TIP:

The following steps will help many of you... BUT

What would be REALLY helpful to anyone trying to support you, is if you go to the "Windows Update Log" and look for any "Errors". This gives a clearer indication as to the exact nature of the problem. (The 0x800A138F error message is a "General" error THE real error number is in the log. A list of possible error messages is in a table at the bottom of this page.)

The windows update log is in the following places:

C:\Windows\Windows Update.log (Win XP & Win98/Me)
C:\WINNT\Windows Update.log (Windows 2000)

Just copy and paste the above in Windows Explorer to open the log file...


I'm in the same boat...nothing worked out as of yet
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext