Windows Update fails with Error number: 0x80072EFF

Anybody else encountering problems with Windows Update since 22 Jan 2009.

Attempting to perform Windows Updates results in the 0x80072EFF error or the
site just times out.

Trying a tracert to update.microsoft.com times out somewhere after it gets
to the msn.net routers. Here's the output from tracert (origin IP masked):

C:\>tracert update.microsoft.com

Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
over a maximum of 30 hops:

1 8 ms <10 ms <10 ms 192.168.1.2
2 * 32 ms 59 ms
ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
n [122.***.**.*]
3 30 ms 30 ms 29 ms
ABTS-KK-Static-***.**.**.122.airtelbroadband.in
[122.***.**.***]
4 51 ms 31 ms 33 ms
ABTS-KK-Static-009.32.166.122.airtelbroadband.in
[122.166.32.9]
5 29 ms 30 ms 29 ms 122.175.255.29
6 38 ms 39 ms 39 ms 125.21.167.74
7 277 ms 270 ms 271 ms 59.145.11.170
8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
[207.46.33.2
9]
9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
[207.46.41.22
]
10 279 ms 279 ms 279 ms 10.22.112.121
11 276 ms 277 ms 277 ms 10.22.112.70
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

That's not an uncommon tracert result. Since there are 'certain
elements' who would dearly love to bring down the update servers, one
can not tracert to them. My system can still update and tracert to
update.microsoft.com yields the same result as your system does.

0x80072EFF ERROR_INTERNET_CONNECTION_Reset

The error may be caused by network congestion or a network problem. It
may even be related to the worm that's taken control of over 9 million
systems, Conficker.B also known as “Downadup.”
4 or 5 years ago the issue stemmed from script blocking. If there is no
script blocking going on, and this would include the prohibition of
ActiveX running via a router hardware firewall, then I suspect the issue
is network related.

MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============


sepl wrote:

> Anybody else encountering problems with Windows Update since 22 Jan 2009.
>
> Attempting to perform Windows Updates results in the 0x80072EFF error or the
> site just times out.
>
> Trying a tracert to update.microsoft.com times out somewhere after it gets
> to the msn.net routers. Here's the output from tracert (origin IP masked):
>
> C:\>tracert update.microsoft.com
>
> Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> over a maximum of 30 hops:
>
> 1 8 ms <10 ms <10 ms 192.168.1.2
> 2 * 32 ms 59 ms
> ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> n [122.***.**.*]
> 3 30 ms 30 ms 29 ms
> ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> [122.***.**.***]
> 4 51 ms 31 ms 33 ms
> ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> [122.166.32.9]
> 5 29 ms 30 ms 29 ms 122.175.255.29
> 6 38 ms 39 ms 39 ms 125.21.167.74
> 7 277 ms 270 ms 271 ms 59.145.11.170
> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> [207.46.33.2
> 9]
> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> [207.46.41.22
> ]
> 10 279 ms 279 ms 279 ms 10.22.112.121
> 11 276 ms 277 ms 277 ms 10.22.112.70
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.
>

Thanks for the reply. However, there is no firewall restriction on ActiveX,
no script blocking at the firewall and update.microsoft.com is in IE's
Trusted Sites list at the Default Level.

I have tried this from three different networks/connections and Windows
Update and tracert consistently fail on all of them, where they were working
fine until a couple or three days ago.

I wonder if this is an India only problem, since several other colleagues in
India on other ISP's and networks have confirmed that they too cannot get
Windows Update to run. As you indicated, network congestion might be a
problem.

I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
for the past 3 days now, with no success.

Are there any alternate Microsoft Windows Update sites or a site where we
can get a list of patches with the download URL's? I can have colleagues
in the USA, where Windows Update seems to be working fine, download the
patches and send them across to us.
..
"MowGreen [MVP]" wrote:

> That's not an uncommon tracert result. Since there are 'certain
> elements' who would dearly love to bring down the update servers, one
> can not tracert to them. My system can still update and tracert to
> update.microsoft.com yields the same result as your system does.
>
> 0x80072EFF ERROR_INTERNET_CONNECTION_Reset
>
> The error may be caused by network congestion or a network problem. It
> may even be related to the worm that's taken control of over 9 million
> systems, Conficker.B also known as “Downadup.”
> 4 or 5 years ago the issue stemmed from script blocking. If there is no
> script blocking going on, and this would include the prohibition of
> ActiveX running via a router hardware firewall, then I suspect the issue
> is network related.
>
> MowGreen [MVP 2003-2009]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> sepl wrote:
>
> > Anybody else encountering problems with Windows Update since 22 Jan 2009.
> >
> > Attempting to perform Windows Updates results in the 0x80072EFF error or the
> > site just times out.
> >
> > Trying a tracert to update.microsoft.com times out somewhere after it gets
> > to the msn.net routers. Here's the output from tracert (origin IP masked):
> >
> > C:\>tracert update.microsoft.com
> >
> > Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> > over a maximum of 30 hops:
> >
> > 1 8 ms <10 ms <10 ms 192.168.1.2
> > 2 * 32 ms 59 ms
> > ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> > n [122.***.**.*]
> > 3 30 ms 30 ms 29 ms
> > ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> > [122.***.**.***]
> > 4 51 ms 31 ms 33 ms
> > ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> > [122.166.32.9]
> > 5 29 ms 30 ms 29 ms 122.175.255.29
> > 6 38 ms 39 ms 39 ms 125.21.167.74
> > 7 277 ms 270 ms 271 ms 59.145.11.170
> > 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> > [207.46.33.2
> > 9]
> > 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> > [207.46.41.22
> > ]
> > 10 279 ms 279 ms 279 ms 10.22.112.121
> > 11 276 ms 277 ms 277 ms 10.22.112.70
> > 12 * * * Request timed out.
> > 13 * * * Request timed out.
> > 14 * * * Request timed out.
> > 15 * * * Request timed out.
> > 16 * * * Request timed out.
> > 17 * * * Request timed out.
> > 18 * * * Request timed out.
> > 19 * * * Request timed out.
> > 20 * * * Request timed out.
> > 21 * * * Request timed out.
> > 22 * * * Request timed out.
> > 23 * * * Request timed out.
> > 24 * * * Request timed out.
> > 25 * * * Request timed out.
> > 26 * * * Request timed out.
> > 27 * * * Request timed out.
> > 28 * * * Request timed out.
> > 29 * * * Request timed out.
> > 30 * * * Request timed out.
> >
> > Trace complete.
> >
>

First, try another attempt at accessing Windows Update. When that fails,
close IE. Then open the WindowsUpdate.log located in %windir%.
Scroll all the way to the bottom for the most recent entries.
Post at least the last 50 or so lines of the log into your reply, please.
Next, flush the dns cache from a Command Prompt
ipconfig /flushdns

Close Command Prompt.
Delete the temporary Internet Files from within Control Panel > Internet
Options.

Reboot the system and try to access Windows Updates once more.
All update content for each month is listed here:

Description of Software Update Services and Windows Server Update
Services changes in content for 2009
http://support.microsoft.com/kb/894199

2008 Description of Software Update Services and Windows Server Update
Services changes in content for 2007
http://support.microsoft.com/kb/961825

There are links under the content that will lead you to where you can
download the content from.
EX: Tuesday, January 13, 2009
New security content:

* MS09-001: Security Update for Windows (KB958687)
If you click the forwarding link you'll be taken to the Security
bulletin for that update -
http://www.microsoft.com/technet/sec.../ms09-001.mspx
Just click the link for Windows Server 2003 x64 Edition and Windows
Server 2003 x64 Edition Service Pack 2 to be taken to the download page.

Most updates are available at the Microsoft Update Catalog, too:
http://catalog.update.microsoft.com/v7/site/Home.aspx

HTH,

MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============



sepl wrote:
> Thanks for the reply. However, there is no firewall restriction on ActiveX,
> no script blocking at the firewall and update.microsoft.com is in IE's
> Trusted Sites list at the Default Level.
>
> I have tried this from three different networks/connections and Windows
> Update and tracert consistently fail on all of them, where they were working
> fine until a couple or three days ago.
>
> I wonder if this is an India only problem, since several other colleagues in
> India on other ISP's and networks have confirmed that they too cannot get
> Windows Update to run. As you indicated, network congestion might be a
> problem.
>
> I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
> for the past 3 days now, with no success.
>
> Are there any alternate Microsoft Windows Update sites or a site where we
> can get a list of patches with the download URL's? I can have colleagues
> in the USA, where Windows Update seems to be working fine, download the
> patches and send them across to us.
> .
> "MowGreen [MVP]" wrote:
>
>
>>That's not an uncommon tracert result. Since there are 'certain
>>elements' who would dearly love to bring down the update servers, one
>>can not tracert to them. My system can still update and tracert to
>>update.microsoft.com yields the same result as your system does.
>>
>>0x80072EFF ERROR_INTERNET_CONNECTION_Reset
>>
>>The error may be caused by network congestion or a network problem. It
>>may even be related to the worm that's taken control of over 9 million
>>systems, Conficker.B also known as “Downadup.”
>>4 or 5 years ago the issue stemmed from script blocking. If there is no
>>script blocking going on, and this would include the prohibition of
>>ActiveX running via a router hardware firewall, then I suspect the issue
>>is network related.
>>
>>MowGreen [MVP 2003-2009]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>sepl wrote:
>>
>>
>>>Anybody else encountering problems with Windows Update since 22 Jan 2009.
>>>
>>>Attempting to perform Windows Updates results in the 0x80072EFF error or the
>>>site just times out.
>>>
>>>Trying a tracert to update.microsoft.com times out somewhere after it gets
>>>to the msn.net routers. Here's the output from tracert (origin IP masked):
>>>
>>>C:\>tracert update.microsoft.com
>>>
>>>Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
>>>over a maximum of 30 hops:
>>>
>>> 1 8 ms <10 ms <10 ms 192.168.1.2
>>> 2 * 32 ms 59 ms
>>>ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
>>>n [122.***.**.*]
>>> 3 30 ms 30 ms 29 ms
>>>ABTS-KK-Static-***.**.**.122.airtelbroadband.in
>>> [122.***.**.***]
>>> 4 51 ms 31 ms 33 ms
>>>ABTS-KK-Static-009.32.166.122.airtelbroadband.in
>>> [122.166.32.9]
>>> 5 29 ms 30 ms 29 ms 122.175.255.29
>>> 6 38 ms 39 ms 39 ms 125.21.167.74
>>> 7 277 ms 270 ms 271 ms 59.145.11.170
>>> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
>>>[207.46.33.2
>>>9]
>>> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
>>>[207.46.41.22
>>>]
>>> 10 279 ms 279 ms 279 ms 10.22.112.121
>>> 11 276 ms 277 ms 277 ms 10.22.112.70
>>> 12 * * * Request timed out.
>>> 13 * * * Request timed out.
>>> 14 * * * Request timed out.
>>> 15 * * * Request timed out.
>>> 16 * * * Request timed out.
>>> 17 * * * Request timed out.
>>> 18 * * * Request timed out.
>>> 19 * * * Request timed out.
>>> 20 * * * Request timed out.
>>> 21 * * * Request timed out.
>>> 22 * * * Request timed out.
>>> 23 * * * Request timed out.
>>> 24 * * * Request timed out.
>>> 25 * * * Request timed out.
>>> 26 * * * Request timed out.
>>> 27 * * * Request timed out.
>>> 28 * * * Request timed out.
>>> 29 * * * Request timed out.
>>> 30 * * * Request timed out.
>>>
>>>Trace complete.
>>>
>>

Thanks for the help. Tried as suggested. Now, I get Error Number: 0x80072EE2.

As requested here are the last 50 lines of the WindowsUpdate.log file:

2009-01-27 09:38:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:38:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:40:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:40:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:43:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:43:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:45:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:45:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 ECP: Failed to download cab file from
http://www.download.windowsupdate.co...44865a617b.cab with error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 ECP: This roundtrip contained some
optimized updates which failed. New Update count = 23, Old Count = 30
2009-01-27 09:45:01+0530 840 3b4 Sync of Updates: 0x8024402f
2009-01-27 09:45:01+0530 840 3b4 WU client failed Searching for update with
error 0x8024402f
2009-01-27 09:45:01+0530 840 36c Search Callback Failed, hr is 0x8024402f
2009-01-27 09:45:01+0530 840 36c Setting next AU detection timeout to
2009-01-27 09:15:01
2009-01-27 09:45:01+0530 840 36c Unable to detect updates for more than 48
hours
2009-01-27 09:45:01+0530 840 36c Setting AU scheduled install time to
2009-01-27 09:30:00
2009-01-27 09:45:01+0530 840 36c WU client calls back to search call
AutomaticUpdates with code Call failed and error 0x8024402f
2009-01-27 09:45:01+0530 840 36c WU client completed and deleted call
{B7DA535A-6528-4610-A62E-E0EDE6B3A3B2}
2009-01-27 09:45:01+0530 840 3b4 REPORT EVENT:
{20403249-852B-4056-BB26-FA5326791FF6} 2009-01-27
09:36:50+0530 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80072ee2 SelfUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 Successfully initialized event uploader
for server 9482f4b4-e343-43b6-b170-9a65bc822c77.
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 Created new event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{04653FED-8F22-4A15-94BE-47161932B826}.bin for writing.
2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
{4B409098-200A-442D-B3CE-6B027C0DB870} 2009-01-27
09:45:01+0530 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024402f AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8024402f
2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
{519AA1CB-1A40-427C-A94C-A3E72FE89740} 2009-01-27
09:45:01+0530 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software
Synchronization 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.
2009-01-27 09:45:06+0530 840 3b4 Successfully initialized event uploader
for server (null).
2009-01-27 09:46:46:546 2268 8d4 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: +0530) ===========
2009-01-27 09:46:46:546 2268 8d4 Misc = Process: C:\Program Files
(x86)\Internet Explorer\iexplore.exe
2009-01-27 09:46:46:546 2268 8d4 Misc = Module:
C:\WINDOWS\SysWOW64\wuweb.dll
2009-01-27 09:46:46:546 2268 8d4 WUWeb FATAL: CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3
2009-01-27 09:46:46+0530 840 3c0 WU client succeeds
CClientCallRecorder::EnumerateService
2009-01-27 09:47:39:125 2268 8d4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
2009-01-27 09:47:39:265 2268 8d4 Misc Microsoft signed: Yes
2009-01-27 09:49:25:140 2612 a30 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: +0530) ===========
2009-01-27 09:49:25:140 2612 a30 Misc = Process: C:\Program Files
(x86)\Internet Explorer\IEXPLORE.EXE
2009-01-27 09:49:25:140 2612 a30 Misc = Module:
C:\WINDOWS\SysWOW64\wuweb.dll
2009-01-27 09:49:25:140 2612 a30 WUWeb FATAL: CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3
2009-01-27 09:49:25+0530 840 384 WU client succeeds
CClientCallRecorder::EnumerateService
2009-01-27 09:49:36:328 2612 a30 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
2009-01-27 09:49:36:390 2612 a30 Misc Microsoft signed: Yes


"MowGreen [MVP]" wrote:

> First, try another attempt at accessing Windows Update. When that fails,
> close IE. Then open the WindowsUpdate.log located in %windir%.
> Scroll all the way to the bottom for the most recent entries.
> Post at least the last 50 or so lines of the log into your reply, please.
> Next, flush the dns cache from a Command Prompt
> ipconfig /flushdns
>
> Close Command Prompt.
> Delete the temporary Internet Files from within Control Panel > Internet
> Options.
>
> Reboot the system and try to access Windows Updates once more.
> All update content for each month is listed here:
>
> Description of Software Update Services and Windows Server Update
> Services changes in content for 2009
> http://support.microsoft.com/kb/894199
>
> 2008 Description of Software Update Services and Windows Server Update
> Services changes in content for 2007
> http://support.microsoft.com/kb/961825
>
> There are links under the content that will lead you to where you can
> download the content from.
> EX: Tuesday, January 13, 2009
> New security content:
>
> * MS09-001: Security Update for Windows (KB958687)
> If you click the forwarding link you'll be taken to the Security
> bulletin for that update -
> http://www.microsoft.com/technet/sec.../ms09-001.mspx
> Just click the link for Windows Server 2003 x64 Edition and Windows
> Server 2003 x64 Edition Service Pack 2 to be taken to the download page.
>
> Most updates are available at the Microsoft Update Catalog, too:
> http://catalog.update.microsoft.com/v7/site/Home.aspx
>
> HTH,
>
> MowGreen [MVP 2003-2009]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> sepl wrote:
> > Thanks for the reply. However, there is no firewall restriction on ActiveX,
> > no script blocking at the firewall and update.microsoft.com is in IE's
> > Trusted Sites list at the Default Level.
> >
> > I have tried this from three different networks/connections and Windows
> > Update and tracert consistently fail on all of them, where they were working
> > fine until a couple or three days ago.
> >
> > I wonder if this is an India only problem, since several other colleagues in
> > India on other ISP's and networks have confirmed that they too cannot get
> > Windows Update to run. As you indicated, network congestion might be a
> > problem.
> >
> > I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
> > for the past 3 days now, with no success.
> >
> > Are there any alternate Microsoft Windows Update sites or a site where we
> > can get a list of patches with the download URL's? I can have colleagues
> > in the USA, where Windows Update seems to be working fine, download the
> > patches and send them across to us.
> > .
> > "MowGreen [MVP]" wrote:
> >
> >
> >>That's not an uncommon tracert result. Since there are 'certain
> >>elements' who would dearly love to bring down the update servers, one
> >>can not tracert to them. My system can still update and tracert to
> >>update.microsoft.com yields the same result as your system does.
> >>
> >>0x80072EFF ERROR_INTERNET_CONNECTION_Reset
> >>
> >>The error may be caused by network congestion or a network problem. It
> >>may even be related to the worm that's taken control of over 9 million
> >>systems, Conficker.B also known as “Downadup.”
> >>4 or 5 years ago the issue stemmed from script blocking. If there is no
> >>script blocking going on, and this would include the prohibition of
> >>ActiveX running via a router hardware firewall, then I suspect the issue
> >>is network related.
> >>
> >>MowGreen [MVP 2003-2009]
> >>===============
> >> *-343-* FDNY
> >>Never Forgotten
> >>===============
> >>
> >>
> >>sepl wrote:
> >>
> >>
> >>>Anybody else encountering problems with Windows Update since 22 Jan 2009.
> >>>
> >>>Attempting to perform Windows Updates results in the 0x80072EFF error or the
> >>>site just times out.
> >>>
> >>>Trying a tracert to update.microsoft.com times out somewhere after it gets
> >>>to the msn.net routers. Here's the output from tracert (origin IP masked):
> >>>
> >>>C:\>tracert update.microsoft.com
> >>>
> >>>Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> >>>over a maximum of 30 hops:
> >>>
> >>> 1 8 ms <10 ms <10 ms 192.168.1.2
> >>> 2 * 32 ms 59 ms
> >>>ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> >>>n [122.***.**.*]
> >>> 3 30 ms 30 ms 29 ms
> >>>ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> >>> [122.***.**.***]
> >>> 4 51 ms 31 ms 33 ms
> >>>ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> >>> [122.166.32.9]
> >>> 5 29 ms 30 ms 29 ms 122.175.255.29
> >>> 6 38 ms 39 ms 39 ms 125.21.167.74
> >>> 7 277 ms 270 ms 271 ms 59.145.11.170
> >>> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> >>>[207.46.33.2
> >>>9]
> >>> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> >>>[207.46.41.22
> >>>]
> >>> 10 279 ms 279 ms 279 ms 10.22.112.121
> >>> 11 276 ms 277 ms 277 ms 10.22.112.70
> >>> 12 * * * Request timed out.
> >>> 13 * * * Request timed out.
> >>> 14 * * * Request timed out.
> >>> 15 * * * Request timed out.
> >>> 16 * * * Request timed out.
> >>> 17 * * * Request timed out.
> >>> 18 * * * Request timed out.
> >>> 19 * * * Request timed out.
> >>> 20 * * * Request timed out.
> >>> 21 * * * Request timed out.
> >>> 22 * * * Request timed out.
> >>> 23 * * * Request timed out.
> >>> 24 * * * Request timed out.
> >>> 25 * * * Request timed out.
> >>> 26 * * * Request timed out.
> >>> 27 * * * Request timed out.
> >>> 28 * * * Request timed out.
> >>> 29 * * * Request timed out.
> >>> 30 * * * Request timed out.
> >>>
> >>>Trace complete.
> >>>
> >>
>

You're not dreaming. I can't confirm a start date of Jan 22. But yesterday
Jan 26 I tried two different clean installs of Windows 2003 R2 SP2 in both 32
and 64 bit, and both couldn't get past the update phase of the
post-installation dialogue. I was using the same installation media,
hardware, method etc. etc. that I've used a hundred times before.

The update process in IE ran VERY slowly, failed numerous times with the
0x80072EFF error, and partially downloaded the current versions of the
Windows or Microsoft update software before siezing. I double checked all the
usual security options that might prevent download and they were fine. No
firewalls are in play.

Last night around 9:30 PM EST I finally concluded the problem was on the
Microsoft end. So I shut the server with the latest install off and went to
bed.

This morning, I got up, booted up that server, and updated with no problem
or intervention!

So something between here and Microsoft changed between last night and this
morning.

Geoff

"sepl" wrote:

> Anybody else encountering problems with Windows Update since 22 Jan 2009.
>
> Attempting to perform Windows Updates results in the 0x80072EFF error or the
> site just times out.
>
> Trying a tracert to update.microsoft.com times out somewhere after it gets
> to the msn.net routers. Here's the output from tracert (origin IP masked):
>
> C:\>tracert update.microsoft.com
>
> Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> over a maximum of 30 hops:
>
> 1 8 ms <10 ms <10 ms 192.168.1.2
> 2 * 32 ms 59 ms
> ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> n [122.***.**.*]
> 3 30 ms 30 ms 29 ms
> ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> [122.***.**.***]
> 4 51 ms 31 ms 33 ms
> ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> [122.166.32.9]
> 5 29 ms 30 ms 29 ms 122.175.255.29
> 6 38 ms 39 ms 39 ms 125.21.167.74
> 7 277 ms 270 ms 271 ms 59.145.11.170
> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> [207.46.33.2
> 9]
> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> [207.46.41.22
> ]
> 10 279 ms 279 ms 279 ms 10.22.112.121
> 11 276 ms 277 ms 277 ms 10.22.112.70
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.
>

Error 0x80072EE is being caused by this FATAL error

2009-01-27 09:49:25:140 2612 a30 WUWeb FATAL: CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3

0x800401f3 CO_E_CLASSSTRING Invalid class string

Suggest you attempt reregistering these files, depending upon whether
the system is opted into Microsoft Update[MU], or just uses Windows
Update [WU]
the mu___.dll is for MU; wu___.dll for WU

Open a Command Prompt, type in the following, pressing Enter after each
command

net stop wuauserv
regsvr32 muweb.dll
regsvr32 wuweb.dll
net start wuauserv
exit

REMEMBER, you don't need to register both .dll files, just the one that
the system is using to access the update page, be it MU or WU.

Restart the system and see if it can update.

*** QED: Has either of these updates been installed yet ? ***

MS09-001: Vulnerabilities in SMB could allow remote code execution
http://support.microsoft.com/kb/958687

MS08-067: Vulnerability in Server service could allow remote code execution
http://support.microsoft.com/kb/958644

IF they both have not been installed yet, then *strongly* suggest you
contact MS for *no-charge* assistance in getting it/them installed:

" How to obtain help and support for this security update
For home users, no-charge support is available by calling 1-866-PCSAFETY
in the United States and Canada or by contacting your local Microsoft
subsidiary. For more information about how to contact your local
Microsoft subsidiary for support issues with security updates, visit the
Microsoft International Support Web site:
http://support.microsoft.com/common/....aspx?rdpath=4 "


MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============



sepl wrote:

> Thanks for the help. Tried as suggested. Now, I get Error Number: 0x80072EE2.
>
> As requested here are the last 50 lines of the WindowsUpdate.log file:
>
> 2009-01-27 09:38:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
> Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
> 2009-01-27 09:38:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
> <http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
> 2009-01-27 09:38:59+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
> 2009-01-27 09:38:59+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072ee2
> 2009-01-27 09:38:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
> with 0x80072ee2
> 2009-01-27 09:40:59+0530 840 3b4 Send failed with hr = 80072ee2.
> 2009-01-27 09:40:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
> Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
> 2009-01-27 09:40:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
> <http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
> 2009-01-27 09:40:59+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
> 2009-01-27 09:40:59+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072ee2
> 2009-01-27 09:40:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
> with 0x80072ee2
> 2009-01-27 09:43:00+0530 840 3b4 Send failed with hr = 80072ee2.
> 2009-01-27 09:43:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
> Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
> 2009-01-27 09:43:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
> <http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
> 2009-01-27 09:43:00+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
> 2009-01-27 09:43:00+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072ee2
> 2009-01-27 09:43:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
> with 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 Send failed with hr = 80072ee2.
> 2009-01-27 09:45:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
> Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
> 2009-01-27 09:45:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
> <http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
> with 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 ECP: Failed to download cab file from
> http://www.download.windowsupdate.co...44865a617b.cab with error 0x80072ee2
> 2009-01-27 09:45:00+0530 840 3b4 ECP: This roundtrip contained some
> optimized updates which failed. New Update count = 23, Old Count = 30
> 2009-01-27 09:45:01+0530 840 3b4 Sync of Updates: 0x8024402f
> 2009-01-27 09:45:01+0530 840 3b4 WU client failed Searching for update with
> error 0x8024402f
> 2009-01-27 09:45:01+0530 840 36c Search Callback Failed, hr is 0x8024402f
> 2009-01-27 09:45:01+0530 840 36c Setting next AU detection timeout to
> 2009-01-27 09:15:01
> 2009-01-27 09:45:01+0530 840 36c Unable to detect updates for more than 48
> hours
> 2009-01-27 09:45:01+0530 840 36c Setting AU scheduled install time to
> 2009-01-27 09:30:00
> 2009-01-27 09:45:01+0530 840 36c WU client calls back to search call
> AutomaticUpdates with code Call failed and error 0x8024402f
> 2009-01-27 09:45:01+0530 840 36c WU client completed and deleted call
> {B7DA535A-6528-4610-A62E-E0EDE6B3A3B2}
> 2009-01-27 09:45:01+0530 840 3b4 REPORT EVENT:
> {20403249-852B-4056-BB26-FA5326791FF6} 2009-01-27
> 09:36:50+0530 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80072ee2 SelfUpdate Failure Software
> Synchronization Error: Agent failed detecting with reason: 0x80072ee2
> 2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
> 2009-01-27 09:45:01+0530 840 3b4 Successfully initialized event uploader
> for server 9482f4b4-e343-43b6-b170-9a65bc822c77.
> 2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
> 2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
> 2009-01-27 09:45:01+0530 840 3b4 Created new event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{04653FED-8F22-4A15-94BE-47161932B826}.bin for writing.
> 2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
> {4B409098-200A-442D-B3CE-6B027C0DB870} 2009-01-27
> 09:45:01+0530 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024402f AutomaticUpdates Failure Software
> Synchronization Error: Agent failed detecting with reason: 0x8024402f
> 2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
> {519AA1CB-1A40-427C-A94C-A3E72FE89740} 2009-01-27
> 09:45:01+0530 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software
> Synchronization 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.
> 2009-01-27 09:45:06+0530 840 3b4 Successfully initialized event uploader
> for server (null).
> 2009-01-27 09:46:46:546 2268 8d4 Misc =========== Logging initialized
> (build: 7.2.6001.788, tz: +0530) ===========
> 2009-01-27 09:46:46:546 2268 8d4 Misc = Process: C:\Program Files
> (x86)\Internet Explorer\iexplore.exe
> 2009-01-27 09:46:46:546 2268 8d4 Misc = Module:
> C:\WINDOWS\SysWOW64\wuweb.dll
> 2009-01-27 09:46:46:546 2268 8d4 WUWeb FATAL: CreateObject for
> Microsoft.Update.AgentInfo failed: error 0x800401f3
> 2009-01-27 09:46:46+0530 840 3c0 WU client succeeds
> CClientCallRecorder::EnumerateService
> 2009-01-27 09:47:39:125 2268 8d4 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
> 2009-01-27 09:47:39:265 2268 8d4 Misc Microsoft signed: Yes
> 2009-01-27 09:49:25:140 2612 a30 Misc =========== Logging initialized
> (build: 7.2.6001.788, tz: +0530) ===========
> 2009-01-27 09:49:25:140 2612 a30 Misc = Process: C:\Program Files
> (x86)\Internet Explorer\IEXPLORE.EXE
> 2009-01-27 09:49:25:140 2612 a30 Misc = Module:
> C:\WINDOWS\SysWOW64\wuweb.dll
> 2009-01-27 09:49:25:140 2612 a30 WUWeb FATAL: CreateObject for
> Microsoft.Update.AgentInfo failed: error 0x800401f3
> 2009-01-27 09:49:25+0530 840 384 WU client succeeds
> CClientCallRecorder::EnumerateService
> 2009-01-27 09:49:36:328 2612 a30 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
> 2009-01-27 09:49:36:390 2612 a30 Misc Microsoft signed: Yes
>
>
> "MowGreen [MVP]" wrote:
>
>
>>First, try another attempt at accessing Windows Update. When that fails,
>>close IE. Then open the WindowsUpdate.log located in %windir%.
>>Scroll all the way to the bottom for the most recent entries.
>>Post at least the last 50 or so lines of the log into your reply, please.
>>Next, flush the dns cache from a Command Prompt
>>ipconfig /flushdns
>>
>>Close Command Prompt.
>>Delete the temporary Internet Files from within Control Panel > Internet
>>Options.
>>
>>Reboot the system and try to access Windows Updates once more.
>>All update content for each month is listed here:
>>
>>Description of Software Update Services and Windows Server Update
>>Services changes in content for 2009
>>http://support.microsoft.com/kb/894199
>>
>>2008 Description of Software Update Services and Windows Server Update
>>Services changes in content for 2007
>>http://support.microsoft.com/kb/961825
>>
>>There are links under the content that will lead you to where you can
>>download the content from.
>>EX: Tuesday, January 13, 2009
>>New security content:
>>
>> * MS09-001: Security Update for Windows (KB958687)
>>If you click the forwarding link you'll be taken to the Security
>>bulletin for that update -
>>http://www.microsoft.com/technet/sec.../ms09-001.mspx
>>Just click the link for Windows Server 2003 x64 Edition and Windows
>>Server 2003 x64 Edition Service Pack 2 to be taken to the download page.
>>
>>Most updates are available at the Microsoft Update Catalog, too:
>>http://catalog.update.microsoft.com/v7/site/Home.aspx
>>
>>HTH,
>>
>>MowGreen [MVP 2003-2009]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>
>>sepl wrote:
>>
>>>Thanks for the reply. However, there is no firewall restriction on ActiveX,
>>>no script blocking at the firewall and update.microsoft.com is in IE's
>>>Trusted Sites list at the Default Level.
>>>
>>>I have tried this from three different networks/connections and Windows
>>>Update and tracert consistently fail on all of them, where they were working
>>>fine until a couple or three days ago.
>>>
>>>I wonder if this is an India only problem, since several other colleagues in
>>>India on other ISP's and networks have confirmed that they too cannot get
>>>Windows Update to run. As you indicated, network congestion might be a
>>>problem.
>>>
>>>I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
>>>for the past 3 days now, with no success.
>>>
>>>Are there any alternate Microsoft Windows Update sites or a site where we
>>>can get a list of patches with the download URL's? I can have colleagues
>>>in the USA, where Windows Update seems to be working fine, download the
>>>patches and send them across to us.
>>>.
>>>"MowGreen [MVP]" wrote:
>>>
>>>
>>>
>>>>That's not an uncommon tracert result. Since there are 'certain
>>>>elements' who would dearly love to bring down the update servers, one
>>>>can not tracert to them. My system can still update and tracert to
>>>>update.microsoft.com yields the same result as your system does.
>>>>
>>>>0x80072EFF ERROR_INTERNET_CONNECTION_Reset
>>>>
>>>>The error may be caused by network congestion or a network problem. It
>>>>may even be related to the worm that's taken control of over 9 million
>>>>systems, Conficker.B also known as “Downadup.”
>>>>4 or 5 years ago the issue stemmed from script blocking. If there is no
>>>>script blocking going on, and this would include the prohibition of
>>>>ActiveX running via a router hardware firewall, then I suspect the issue
>>>>is network related.
>>>>
>>>>MowGreen [MVP 2003-2009]
>>>>===============
>>>> *-343-* FDNY
>>>>Never Forgotten
>>>>===============
>>>>
>>>>
>>>>sepl wrote:
>>>>
>>>>
>>>>
>>>>>Anybody else encountering problems with Windows Update since 22 Jan 2009.
>>>>>
>>>>>Attempting to perform Windows Updates results in the 0x80072EFF error or the
>>>>>site just times out.
>>>>>
>>>>>Trying a tracert to update.microsoft.com times out somewhere after it gets
>>>>>to the msn.net routers. Here's the output from tracert (origin IP masked):
>>>>>
>>>>>C:\>tracert update.microsoft.com
>>>>>
>>>>>Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
>>>>>over a maximum of 30 hops:
>>>>>
>>>>> 1 8 ms <10 ms <10 ms 192.168.1.2
>>>>> 2 * 32 ms 59 ms
>>>>>ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
>>>>>n [122.***.**.*]
>>>>> 3 30 ms 30 ms 29 ms
>>>>>ABTS-KK-Static-***.**.**.122.airtelbroadband.in
>>>>>[122.***.**.***]
>>>>> 4 51 ms 31 ms 33 ms
>>>>>ABTS-KK-Static-009.32.166.122.airtelbroadband.in
>>>>>[122.166.32.9]
>>>>> 5 29 ms 30 ms 29 ms 122.175.255.29
>>>>> 6 38 ms 39 ms 39 ms 125.21.167.74
>>>>> 7 277 ms 270 ms 271 ms 59.145.11.170
>>>>> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
>>>>>[207.46.33.2
>>>>>9]
>>>>> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
>>>>>[207.46.41.22
>>>>>]
>>>>>10 279 ms 279 ms 279 ms 10.22.112.121
>>>>>11 276 ms 277 ms 277 ms 10.22.112.70
>>>>>12 * * * Request timed out.
>>>>>13 * * * Request timed out.
>>>>>14 * * * Request timed out.
>>>>>15 * * * Request timed out.
>>>>>16 * * * Request timed out.
>>>>>17 * * * Request timed out.
>>>>>18 * * * Request timed out.
>>>>>19 * * * Request timed out.
>>>>>20 * * * Request timed out.
>>>>>21 * * * Request timed out.
>>>>>22 * * * Request timed out.
>>>>>23 * * * Request timed out.
>>>>>24 * * * Request timed out.
>>>>>25 * * * Request timed out.
>>>>>26 * * * Request timed out.
>>>>>27 * * * Request timed out.
>>>>>28 * * * Request timed out.
>>>>>29 * * * Request timed out.
>>>>>30 * * * Request timed out.
>>>>>
>>>>>Trace complete.
>>>>>
>>>>

Well, Windows Update all of a sudden worked last afternoon and I was able to
bring the server to the current patch level. I did not make any changes to
the OS or anything else.

I however noticed this morning that yet another server is now unable to get
the patches off the Windows Update site. Looks like something weird is going
on with Windows Update can't seem to figure out what though.

I guess, we will have to just wait and keep trying in the hope that the
Windows Update site will suddenly become available and the patches can be
downloaded. Pity.

"Geoff D" wrote:

> You're not dreaming. I can't confirm a start date of Jan 22. But yesterday
> Jan 26 I tried two different clean installs of Windows 2003 R2 SP2 in both 32
> and 64 bit, and both couldn't get past the update phase of the
> post-installation dialogue. I was using the same installation media,
> hardware, method etc. etc. that I've used a hundred times before.
>
> The update process in IE ran VERY slowly, failed numerous times with the
> 0x80072EFF error, and partially downloaded the current versions of the
> Windows or Microsoft update software before siezing. I double checked all the
> usual security options that might prevent download and they were fine. No
> firewalls are in play.
>
> Last night around 9:30 PM EST I finally concluded the problem was on the
> Microsoft end. So I shut the server with the latest install off and went to
> bed.
>
> This morning, I got up, booted up that server, and updated with no problem
> or intervention!
>
> So something between here and Microsoft changed between last night and this
> morning.
>
> Geoff
>
> "sepl" wrote:
>
> > Anybody else encountering problems with Windows Update since 22 Jan 2009.
> >
> > Attempting to perform Windows Updates results in the 0x80072EFF error or the
> > site just times out.
> >
> > Trying a tracert to update.microsoft.com times out somewhere after it gets
> > to the msn.net routers. Here's the output from tracert (origin IP masked):
> >
> > C:\>tracert update.microsoft.com
> >
> > Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> > over a maximum of 30 hops:
> >
> > 1 8 ms <10 ms <10 ms 192.168.1.2
> > 2 * 32 ms 59 ms
> > ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> > n [122.***.**.*]
> > 3 30 ms 30 ms 29 ms
> > ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> > [122.***.**.***]
> > 4 51 ms 31 ms 33 ms
> > ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> > [122.166.32.9]
> > 5 29 ms 30 ms 29 ms 122.175.255.29
> > 6 38 ms 39 ms 39 ms 125.21.167.74
> > 7 277 ms 270 ms 271 ms 59.145.11.170
> > 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> > [207.46.33.2
> > 9]
> > 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> > [207.46.41.22
> > ]
> > 10 279 ms 279 ms 279 ms 10.22.112.121
> > 11 276 ms 277 ms 277 ms 10.22.112.70
> > 12 * * * Request timed out.
> > 13 * * * Request timed out.
> > 14 * * * Request timed out.
> > 15 * * * Request timed out.
> > 16 * * * Request timed out.
> > 17 * * * Request timed out.
> > 18 * * * Request timed out.
> > 19 * * * Request timed out.
> > 20 * * * Request timed out.
> > 21 * * * Request timed out.
> > 22 * * * Request timed out.
> > 23 * * * Request timed out.
> > 24 * * * Request timed out.
> > 25 * * * Request timed out.
> > 26 * * * Request timed out.
> > 27 * * * Request timed out.
> > 28 * * * Request timed out.
> > 29 * * * Request timed out.
> > 30 * * * Request timed out.
> >
> > Trace complete.
> >