0x80072F8F

[ckwong1...@yahoo.com]

hi

I have the problem on the window update and the following are the step have
been make

1)make sure the time are correctly
2)Start > Run and type regsvr32 MSXML3.DLL
Do the same for
SOFTPUB.DLL
INITPKI.DLL
MSSIP32.DLL
URLMON.DLL
WINTRUST.DLL

and the machine have been rebooted, but i still get the same
error.Appreciate if anybody can give me a help.

[Raki]

ckwong1...@yahoo.com wrote:

If you receive the 0x80072F8F error code, the date and the time on your
computer may vary too much from the valid date and time of the Secure
Sockets Layer (SSL) certificates that are used by the Windows Update Web
site.
RESOLUTION
0x80072F8F error code
To resolve this error, verify that the date and time settings for your
computer are accurate. To do this, follow these steps:
Click Start, click Run, type timedate.cpl, and then click OK.
Set the date and time to the correct values for your time zone, and then
click OK.
HTH

Raki

[ckwong1...@yahoo.com]

hi

I have do the same for the time and I am sure the time is correct
accoordingly,what else can be done on the server

[Pumpkin]

Yes I have had the same problem as you and trust me nothing has worked for
me, I have had this since before xmas and I cant update cause of it the last
update was nov 28th that was the last time I updated my computer.. So now I
have just given up in trying anything cause nothing works......

[ckwong1...@yahoo.com]

hi,

On ur machine do you try to upgrade the xml to version 4, this i havent
try.Dont know that it will help or not

[TaurArian [MS-MVP]]

Did you check Time Zone Tab to make sure you had the correct time zone?

Also open IE, Select the Tools menu, Internet Options
Choose the Advance tab
Unselect 'check for server certificate revocation'
reboot

Try again.

--
===========================
TaurArian [MS-MVP] 2005-2006
===========================
http://www.dts-l.org/goodpost.htm
"Need more help? http://support.microsoft.com/?scid=ph;en-us;6527

<ckwong1...@yahoo.com> wrote in message
news:D2C68DB0-5284-4473...@microsoft.com...

[ckwong1...@yahoo.com]

hi

Yes I have did that,what else I havent do kindly advise?

[TaurArian [MS-MVP]]

0x80072F8F -2147012721
ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong
One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server.

Check this article
http://support.microsoft.com/?id=326253
You cannot view updates on the Windows Update site using secure socket layer

--
===========================
TaurArian [MS-MVP] 2005-2006
===========================
http://www.dts-l.org/goodpost.htm
"Need more help? http://support.microsoft.com/?scid=ph;en-us;6527

<ckwong1...@yahoo.com> wrote in message
news:DBC796B0-7135-4D41...@microsoft.com...

[ckwong1...@yahoo.com]

hi,

But if the failure on the SSL or the SSL is missing what are the recommended
sollution?

[ckwong1...@yahoo.com]

hi,

I did the same thing but it wont work, I dont know how to fix it.

"John Page" wrote:

> Hi, I had this problem when an automatic update was interrupted early on by
> a hibernation event, complaint that date/time were wrong on certificate.
> Checked date/time, ran regsvr32 softpub.dll as suggested - no joy. Assumed
> that re-started update not initialised properly, so restarted system -
> problem
> cleared.

[Donté Henry]

This issue had been a big problem on the W2K3 servers in our environment and
nothing I found online would provide the right answer to resolve the issue.
Turns out the issue was caused by *not* having our servers access the
Microsoft Windows Update site through our ISA proxy server. I believe this
has something to do with how the Update site establishes a secure connection
with the client attempting to receive updates. We had to ensure that all
secure connections were proxied by the proxy server (Internet Options -
Connections - LAN Settings - Advanced). Once we did that, Windows Update
worked fine!

This KB article was helpful in finding the right answer for us:

http://support.microsoft.com/?id=326253

I hope it's helpful to you too!

[Donté Henry]

This issue had been a big problem on the W2K3 servers in our environment and
nothing I found online would provide the right answer to resolve the issue.
Turns out the issue was caused by *not* having our servers access the
Microsoft Windows Update site through our ISA proxy server. I believe this
has something to do with how the Update site establishes a secure connection
with the client attempting to receive updates. We had to ensure that all
secure connections were proxied by the proxy server (Internet Options -
Connections - LAN Settings - Advanced). Once we did that, Windows Update
worked fine!

This KB article was helpful in finding the right answer for us:

http://support.microsoft.com/?id=326253

I hope it's helpful to you too!

[Donté Henry]

This issue had been a big problem on the W2K3 servers in our environment and
nothing I found online would provide the right answer to resolve the issue.
Turns out the issue was caused by *not* having our servers access the
Microsoft Windows Update site through our ISA proxy server. I believe this
has something to do with how the Update site establishes a secure connection
with the client attempting to receive updates. We had to ensure that all
secure connections were proxied by the proxy server (Internet Options -
Connections - LAN Settings - Advanced). Once we did that, Windows Update
worked fine!

This KB article was helpful in finding the right answer for us:

http://support.microsoft.com/?id=326253

I hope it's helpful to you too!

[YASSINE]

Hi,

I also had the same problem on a virtual machine where I installed
Smartfilter and which is located behind a Sidewinder firewall. With this
setup, I'm having problems with Https sites due to smartfilter and I
contacted the secure computing support to solve this problem. Meanwhile I
tried to update my virtual machine and face this error. I firest checked the
date of my computer, OK. And then the firewall, I found it wrong and I fixed
it but still having the same problem. I used another Internet connection with
another firewall and choosed the option Windows Update instead of Microsoft
update and it worked!!!!
So I suggest you check your firewall settings. Good Luck.

Yassine

[S.@discussions.microsoft.com Dave S.]

Hi!

Over the last couple of days I've been scouring the net for ways to deal with
0x80072F8F and subsequently 0x80072EE2 errors being returned when trying to
update my system at Microsoft Update. I probably poured over a couple of
hundred
postings and a good number of support.microsoft.com notifications. Like most
folks who got involved with postings and replies to postings, all solutions
offered failed. Then I stumbled onto a solution that had no relation to these
error codes. I tried a "swag" system solution and now I can access Microsoft
Update.

I'm not saying that "this is _the_ solution", but it certainly bears looking
into.

The real culprit generating these errors from Microsoft Update was in no way
related to time synchronization, DLL re-registering, or settings in IE
Internet
Options. It was my security suite's firewall (Kaspersky Internet Security 7)
that was gumming up the works!8=O. I did not shut down Kaspersky as in these
times I think anyone who does that is just borrowing more trouble!;)

Getting down to what I actually did:

1) Turn on Microsoft's firewall in the Security center.

2) Turn off Kaspersky's firewall.

Antispam, virus checking, process integrity, web and file monitoring, and
registry
watch were still operational in Kaspersky. The only thing that changed was
which
firewall to use.

At the end of this simple firewall substitution, I tried Microsoft Update
again.

It was working!8-O

Like I said, I don't propose this as the solution for everyone. But since it
is
so simple to do, and does not requier rebooting, a person has nothing to
really
lose beyond, say, 2 minutes to effect the firewall swap.

HTH:

thx,
Dave S.

[PA Bear [MS MVP]]

You may receive an "Error 0x80072EE2," "Error 0x80072EE7," "Error
0x80072EFD," "Error 0x80072F76," or "Error 0x80072F78" error message when
you try to use the Windows Update Web site or the Microsoft Update Web site
["Step 2: Verify your personal firewall program settings..."]
http://support.microsoft.com/kb/836941
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

[Cleaner Guy@discussions.microsoft.com Roof Cleaner Guy]

In My case the solution to the problem was NOT the time.
It was a missing CA certificate.

My configuration: Windows VISTA, Home Premium, Compaq Presario 5505F from
Best Buy, Windows Update Error

What tipped me off was using Internet Explorer V7 I would get certificate
warnings from completely secure sites (sites that I could reach from the same
machine using firefox 3.0):
http://www.usps.gov , http://www.cleanertoday.com and
http://www.canadapost.com all warned of certificate problems
(These are among the most trusted sites around. Cleaner Today even uses the
EV-SSL certificate. The common thread I would later learn was that IE was
missing a GTE CyberTrust Global Root Cert ).

More errors and clues you might see:

On screen error messages:
0x80072F8F and 80072F8F in Windows Update,and Windows Defender.

System EventLog Error:
Unable to Connect: Windows is unable to connect to the automatic updates
service and therefore cannot download and install updates according to the
set schedule. Windows will continue to try to establish a connection.

WindowsUpdate.log:
The error in the WindowsUpdate.log showed as a 0x80072F8F, which again
unfortunately, when searched for, yields some trivial and incorrect KBs
( http://support.microsoft.com/kb/929458 and posts related to the time on
the problem computer being out of sync with the Update server(s). While that
would cause problems, that isn't what was going on in my case.)

The WindowsUpdate.log included an attempt (and 0x80072F8F failure) to
connect to the following URL:
Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx

Solution:

In my case, the Microsoft Windows Update web server SSL cert was untrusted
due to a missing root CA cert.
GTE CyberTrust Global Root cert was not installed. (It needed to be in the
Trusted Root Certificates store)
Rather than mess with the individual missing certificates, I decided to
directly download the current (July 2008 CAs).
I bypassed windows update and download the current certificates directly
based on this KB article:
http://support.microsoft.com/kb/931125

Final Notes:
The firewall (norton internet security 2008) had nothing to do with this
situation.
Of course the frustration was this machine was just take out of the box and
had these problems (probably in the build).

I hope that my 3 days of digging and exhausting support from HP and
Microsoft will save others some headaches.

[Jun Wang]

Wow, this fixed my problem at last! Thanks Cleaner guy!

Before trying the whole root CA cert package as you suggested, I did look
around and end up exporting/importing the same GTE CyberTrust Global Root
Cert but it didn't work.

Although this CA cert package KB claims to apply to only Win XP, it
apparently works on my Win7 too!

[greggarcher]

Thanks for this post, Roof Cleaner Guy! I was going crazy until I downloaded
the current certificates as described in your post and the KB article, and
now my Windows Update is back up and running.

[Tourf00]

I had the same persistent error, and it was frustrating to see this message
"please check data and time", as obviously this was checked easily. The
problem was on the company's internet PROXY messing with certificates. I used
an alternate PROXY (you know, the one that only the IT dept knows about?)
and now it works! No re-boot!

Cheers