Please state your full Windows version (e.g., WinXP SP3) when posting to
this newsgroup. In this case, also state your IE version.
Is Automatic Updates enabled? If not, can you enable it, reboot, and find
it still enabled?
What anti-virus application or security suite is installed and is your
subscription current? What anti-spyware applications (other than Defender)?
What third-party firewall (if any)?
Has a(another) Norton or McAfee application ever been installed on this
machine (e.g., a free-trial version that came preinstalled when you bought
it)?
Error message when you try to install updates from the Windows Update Web
site on a Windows XP-based computer: "Windows Update has encountered an
error and cannot display the requested page":
http://support.microsoft.com/kb/914226
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
www.banthecheck.com
Simon wrote:
> When I try to check for updates, (going to http://update.microsoft.com
> who then resolves to
> http://update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us), the
> page is blank and never complete loading, (in IE8 the circle just turns
> for a good 2-3 minutes).
> Then I get an error "Internet Explorer cannot display the webpage"
>
> And that's all. I have Win XP pro SP3 and I am admin on the machine.
> I can go to http://www.microsoft.com and other sites without any problems.
>
> How can I run my updates?
>
> Simon
To use Windows Updates in XP you need Background Intelligent Transfer
Service (BITS) & Automatic Updates started otherwise it comes up with an
error message that one of those two services isn't running. As you are an
MVP-IE you should have known that
Usually a black page signifies an activex not running as the security
settings are set too high or a firewall is blocking an activex from running
Anyway, the OP should post his/her question to the correct newsgroup given
by myself in my original reply & then cross posted by you to get your number
of replies up
--
SPAMCOP User
"PA Bear [MS MVP]" <PABe...@gmail.com> wrote in message
news:OUG6VO5F...@TK2MSFTNGP02.phx.gbl...
I am not sure what else I need to supply, I already mentioned what you
are asking for, Win XP PRO SP3 with IE8
> Is Automatic Updates enabled? If not, can you enable it, reboot, and
> find it still enabled?
I have the 'third' automatic update option enabled, notify me when there
is an update but don't download anything until I say so.
>
> What anti-virus application or security suite is installed and is your
> subscription current? What anti-spyware applications (other than
> Defender)? What third-party firewall (if any)?
I only have Defender, and my AV is Trend Micro, all up to date.
>
> Has a(another) Norton or McAfee application ever been installed on this
> machine (e.g., a free-trial version that came preinstalled when you
> bought it)?
No.
>
> Error message when you try to install updates from the Windows Update
> Web site on a Windows XP-based computer: "Windows Update has encountered
> an error and cannot display the requested page":
> http://support.microsoft.com/kb/914226
As I said, I get no errors, nothing, only a blank page.
As I said, I eventually get "Internet Explorer cannot display the webpage"
Regards,
Simon
Did the problem start immediately after installing IE8? Did you disable TM
AV prior to installing IE8?
Simon wrote:
> I am not sure what else I need to supply, I already mentioned what you
> are asking for, Win XP PRO SP3 with IE8
>
> I have the 'third' automatic update option enabled, notify me when there
> is an update but don't download anything until I say so.
>
> I only have Defender, and my AV is Trend Micro, all up to date.
>>
>> Has a(another) Norton or McAfee application ever been installed on this
>> machine (e.g., a free-trial version that came preinstalled when you
>> bought it)?
>
> No.
>
> As I said, I get no errors, nothing, only a blank page.
> As I said, I eventually get "Internet Explorer cannot display the webpage"
>
<paste>
PA Bear [MS MVP] wrote:
> [crosspost to Windows Update newsgroup]
>
> Please state your full Windows version (e.g., WinXP SP3) when posting to
> this newsgroup. In this case, also state your IE version.
>
> Is Automatic Updates enabled? If not, can you enable it, reboot, and find
> it still enabled?
>
> What anti-virus application or security suite is installed and is your
> subscription current? What anti-spyware applications (other than
> Defender)?
> What third-party firewall (if any)?
>
> Has a(another) Norton or McAfee application ever been installed on this
> machine (e.g., a free-trial version that came preinstalled when you bought
> it)?
>
> Error message when you try to install updates from the Windows Update Web
> site on a Windows XP-based computer: "Windows Update has encountered an
> error and cannot display the requested page":
> http://support.microsoft.com/kb/914226
>
> Simon wrote:
>> When I try to check for updates, (going to http://update.microsoft.com
>> who then resolves to
>> http://update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us), the
>> page is blank and never complete loading, (in IE8 the circle just turns
>> for a good 2-3 minutes).
>> Then I get an error "Internet Explorer cannot display the webpage"
I carried on with the instructions,
http://update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us
loaded, once and told me I had to install some ActiveX and then reboot.
After rebooting I got the same problem.
Now, even repeating the steps does not help.
>
> Did the problem start immediately after installing IE8? Did you disable
> TM AV prior to installing IE8?
No, it did work for a short while, but I am not sure when it stopped
working, most of the time I use the dialog box that pops up when windows
tells me that some updates are ready to download.
Simon
[edit] Because iexplorer.exe was open, (the one with the instructions),
I guess it was part of the problem.
So I used Firefox to read and follow the instructions, rebooted.
And it all seems to work fine now.
Thanks
Simon
Try later or tomorrow.
--
Disclaimer: The information has been posted "as is" with no warranties or
guarantees and doesn''t give any rights.
TaurArian wrote:
> I'm also having problems on two computers (one at work and one at home) -
> I'm putting it down to the servers (at MS' end) being
> overloaded/overwhelmed or something.
>
> Try later or tomorrow.
>
>
At the moment the page isn't even loading. When it did load at one stage, it
got so far and then IE said it couldn't load the page etc etc.
This is on two computers, one at home and one at work, one is WinXP SP3 IE8
and the other is out of date WinXP SP2 - IE6 (work of course).
I allowed the updates to auto download on the first computer, lost the icon
at somewhere at 23%. Shut down without installing the updates that had
downloaded.
At this stage, I haven't even tried the Vista laptop.
I think there's a problem with the site/servers rather than the computers
involved, perhaps they're just a little overwhelmed at the moment. It'll
happen, I'm not worried about it.
Kaylene
--
Disclaimer: The information has been posted "as is" with no warranties or
guarantees and doesn''t give any rights.
Work computer set for Windows updates only.
Home computer set for Microsoft updates.
K
--
Disclaimer: The information has been posted "as is" with no warranties or
guarantees and doesn''t give any rights.
> I think there's a problem with the site/servers rather than the computers
> involved, perhaps they're just a little overwhelmed at the moment.
Well, it's happening for weeks and months for several users/systems
now. This may depend on the provider/DNS server used. Strange enough,
*if* you can manage to get WU/MU displayed and do a scan, the down-
load of the updates themselfes is running in normal speed. The same
applies for Auto Update of course. There definitly seems to be an
issue with WU/MU *site* "only".
I urge users running into the "slow" Windows Update site reaction to
contact Microsoft Support and open a call (which is free):
https://support.microsoft.com/oas/default.aspx?gprid=6527&st=1
http://www.google.de/microsoft?hl=de&q=%22Windows+Update%22+site+slow&as_qdr=m
shows the results for postings about the issue in the last 4 weeks
only. As you can see, it's a widespreded issue.
And no, "Security Applications" runing in the background and blocking
"something" aren't the culprits this time.
Bye,
Freudi
P.S.: Yes, of course I've opened a case with MS Germany already and
am asking other users having the same issue to the same. I've
an (German languaged) article about that running on my little
site since Friday: http://patch-info.de/artikel/2009/08/07/666
> Vista SP2 (which I should hope is currently throttled) and the server demand
> due to the 9-10 August updates notwithstanding,
... which is a good idea, since the *download* of updates runs at
normal speed, while the Windows Update *site* does show up *slow*
since some weeks/months even *before* being able to scan the system
for missing updates, ...
> perhaps things will improve after
> http://blogs.technet.com/mu/archive/2009/07/10/upcoming-update-for-windows-update.aspx ?
As you've read in the article on my little site <g>, I hope so.
But looking at the issues with the Windows Update *site*, I would
really be surprised. Looks like a possible DNS pollution/blocking
issue for update.microsoft.com from my end. Since ist seems to be
a more or less global issue occuring with all sorts of providers
(and their DNS servers), it's most likely an issue origin at MS's
end.
Bye,
Freudi
> There definitly seems to be an issue with WU/MU *site* "only".
Just for the doubters:
A short session overview from Fiddler2. Windows XP SP3, IE8, Cache
cleared before running the test, DSL 16Mbit/s. The test consists of
choosing "Windows Update" from the Security -ehm- menu out of IE8,
no scanning etc, just the plain WU site:
Request Count: 84
Bytes Sent: 81.773
Bytes Received: 612.964
ACTUAL PERFORMANCE
--------------
Requests started at: 20:36:11:9531
Responses completed at: 20:38:28:4218
Aggregate Session time: 00:02:51:3437
Sequence (clock) time: 00:02:16.4687500
DNS Lookup time: 312ms
TCP/IP Connect time: 2.999ms
RESPONSE CODES
--------------
HTTP/200: 84
RESPONSE BYTES (by Content-Type)
--------------
application/octet-stream: 22.206
application/x-javascript: 407.416
text/html: 79.387
image/x-icon: 25.214
text/css: 17.863
image/jpeg: 26.210
~headers: 23.055
text/plain: 218
image/gif: 11.395
As you can see, it took >2 minutes this time to just get the WU site
displayed in IE. I've saved the Fiddler session (and the nXpert report
too).
Some examples? Okay, here we go:
GET /windowsupdate/v6/default.aspx HTTP/1.1
ServerGotRequest: 21:02:19:2500
ServerBeginResponse: 21:02:40:9531
= ~21 seconds
GET /windowsupdate/v6/default.aspx?ln=de HTTP/1.1
ServerGotRequest: 21:02:41:2656
ServerBeginResponse: 21:03:03:7812
= ~22 seconds
GET /windowsupdate/v6/shared/js/resultslist.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:04:2968
ServerBeginResponse: 21:03:27:7500
= ~23 seconds
GET /windowsupdate/v6/shared/js/spupdateids.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:04:8125
ServerBeginResponse: 21:03:27:0312
= ~22 seconds
GET /microsoftupdate/v6/shared/js/webcomtop.js?633857617[snipped] HTTP/1.1
ServerGotRequest: 21:03:06:7812
ServerBeginResponse: 21:03:30:2031
= ~23 seconds
GET /microsoftupdate/v6/toc.aspx?ln=de HTTP/1.1
ServerGotRequest: 21:03:31:0000
ServerBeginResponse: 21:03:48:2343
= ~17 seconds
GET /microsoftupdate/v6/shared/js/tgar.js?633857618[snipped] HTTP/1.1
ServerGotRequest: 21:03:51:1875
ServerBeginResponse: 21:04:10:7500
= ~12 seconds
In total ~140 seconds it took for several actions until the
server(!) responded to client's (browser / IE) requests.
> I urge users running into the "slow" Windows Update site reaction to
> contact Microsoft Support and open a call (which is free):
> https://support.microsoft.com/oas/default.aspx?gprid=6527&st=1
Yeah,
Freudi
Since I love to communicate with myself, just now it looks okay
right now. I don't know, if that lasts but I hope so.
After the first attempt failing completely (no response from
/windowsupdate/v6/default.aspx), another session startet a few
seconds later showed normal behaviour and performance:
Request Count: 88
Bytes Sent: 42.959
Bytes Received: 569.775
ACTUAL PERFORMANCE
--------------
Requests started at: 04:46:07:7812
Responses completed at: 04:46:20:8750
Aggregate Session time: 00:00:22:8125
Sequence (clock) time: 00:00:13.0937500
DNS Lookup time: 265ms
TCP/IP Connect time: 2.589ms
I really hope it's not related to the load balancer farm managing
the incoming requests to Windows Update. Otherwise would be like
playing Jjepoardy to get a reponsive server while accessing the WU
site.
FWIW,
Freudi
> After the first attempt failing completely (no response from
> /windowsupdate/v6/default.aspx), another session startet a few
> seconds later showed normal behaviour and performance:
>
> Request Count: 88
> Bytes Sent: 42.959
> Bytes Received: 569.775
>
> ACTUAL PERFORMANCE
> --------------
> Requests started at: 04:46:07:7812
> Responses completed at: 04:46:20:8750
> Aggregate Session time: 00:00:22:8125
> Sequence (clock) time: 00:00:13.0937500
> DNS Lookup time: 265ms
> TCP/IP Connect time: 2.589ms
>
> I really hope it's not related to the load balancer farm managing
> the incoming requests to Windows Update. Otherwise would be like
> playing Jjepoardy to get a reponsive server while accessing the WU
> site.
Well, I hate to be correct (not only) this time:
Request Count: 88
Bytes Sent: 42.959
Bytes Received: 474.486
ACTUAL PERFORMANCE
--------------
Requests started at: 05:34:58:0468
Responses completed at: 05:36:42:0468
Aggregate Session time: 00:03:48:4375
Sequence (clock) time: 00:01:44
DNS Lookup time: 267ms
TCP/IP Connect time: 2.671ms
Load balancer?
The story continues,
Freudi
Or the rest of Europe's just starting to wake up, most of North & South
America has gone to bed, and it's lunchtime in Asia?
Well that would be really surprising and couldn't have been expected.
That's what a load balancer is for. And of course, the WU site worked
all the years - in case there hasn't been trouble on the servers end.
I consider creating a EWS report right now.
Bye,
Freudi
> I consider creating a EWS report right now.
Done:
https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=483115&SiteID=470
Bye,
Freudi