Windows Update Thinks My OS Is A Mac

Thanks, Glen. Like Brian, I have noticed that some urls work better
than others but currently when broken (like now)none get me in ever.
Just like the weather in Colorado, wait 5 minutes and it might be an
entirely different story. Oddly for me it's the v5 and v6 urls that
work best!
var V5Site = "http://v5.windowsupdate.microsoft.com";
var V6Site = "http://update.microsoft.com/windowsupdate";

Also the first try is almost always a wash but the second or more
tries even with the same url or other shortcut method may work
perfect. There is also the Windows Update link in Tools of the
toolbar to try in addition to the Start Menu|Settings|Windows Update
shortcut. I need to backdate my problem's start date - it's the same
date as redirect.js file - 2/22/07 at 5:56 PM, that's three thursdays
as of tomorrow and I'm begining to believe that this is way it ends at
WinUP for 9x boxes. RIP sniffle

Lee

On Mar 12, 10:18 pm, "glee" wrote:
FWIW, MVP Brian Sesko reports that his experience thus far has been that if he
copy/pastes the URL below to his browser address box, he consistently (so far) gets
through successfully:http://v4.windowsupdate.microsoft.com/en/default.asp

He states, do not use the Windows Update icon in the Start menu, use only the link
above. It would seem a good thing to test.
--
Glen Ventura, MS MVP Shell/User, A+http://dts-l.org/http://dts-l.org/goodpost.htm

"Lee" wrote in message

oups.com...



snip
I'm sorry it's none of those. I'm running IE 5.5 SP2 and sometimes I
get in and sometimes I don't all depending on the redirect.js files.
There is this copy:
http://v4.windowsupdate.microsoft.co...js/redirect.js
which is a 17k text file and then there is this one:
http://windowsupdate.microsoft.com/redirect.js
which is a 4k binary and NOT a text file at all when the site is
broken for 98 like right now. Using either the WinUP site or the
Catalog gets both files, exactly why I have no clue but there they are
in your TIF folder - take a look.

When the site works I suspect that the second link above is to a valid
16k text file that is slightly different than the first file, but the
site has not been working when I've tried it to verify that as it
appears to still be catch as catch can since 2/27/07 when I first came
across this problem. The WinUP folks sadly appear to be completely in
the dark this time around, we didn't have much time left at WinUP site
anyway...

Things I've learned reading the redirect.js file.
Win2K is NT 5.0
WinXP is NT 5.1
Win2003 is NT 5.2
Longhorn is NT 6.0
or
Vista is NT 6.0
all depending on which version of redirect.js file you are reading.
They really should get on the same page I would think, use one or the
other but not both.- Hide quoted text -

- Show quoted text -

:-) Hi Lee,
Yep, I got to WU with no problem a little while ago, but then got the Mac message a
while after that. Similarly, at work, I got to WU and also to the WU Corporate
site, where I downloaded some updates for offline installation, but then shortly
after that I got the Mac message on the same system, and none of the suggested
workarounds worked.

FWIW, the word I got was that when some MVPs asked some folks at MS about this
issue, they were unaware of it. Why does that not surprise me......
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/
http://dts-l.org/goodpost.htm


"Lee" wrote in message
oups.com...
Thanks, Glen. Like Brian, I have noticed that some urls work better
than others but currently when broken (like now)none get me in ever.
Just like the weather in Colorado, wait 5 minutes and it might be an
entirely different story. Oddly for me it's the v5 and v6 urls that
work best!
var V5Site = "http://v5.windowsupdate.microsoft.com";
var V6Site = "http://update.microsoft.com/windowsupdate";

Also the first try is almost always a wash but the second or more
tries even with the same url or other shortcut method may work
perfect. There is also the Windows Update link in Tools of the
toolbar to try in addition to the Start Menu|Settings|Windows Update
shortcut. I need to backdate my problem's start date - it's the same
date as redirect.js file - 2/22/07 at 5:56 PM, that's three thursdays
as of tomorrow and I'm begining to believe that this is way it ends at
WinUP for 9x boxes. RIP sniffle

Lee

On Mar 12, 10:18 pm, "glee" wrote:
FWIW, MVP Brian Sesko reports that his experience thus far has been that if he
copy/pastes the URL below to his browser address box, he consistently (so far)
gets
through successfully:http://v4.windowsupdate.microsoft.com/en/default.asp

He states, do not use the Windows Update icon in the Start menu, use only the
link
above. It would seem a good thing to test.
--
Glen Ventura, MS MVP Shell/User, A+http://dts-l.org/http://dts-l.org/goodpost.htm

"Lee" wrote in message

oups.com...



snip
I'm sorry it's none of those. I'm running IE 5.5 SP2 and sometimes I
get in and sometimes I don't all depending on the redirect.js files.
There is this copy:
http://v4.windowsupdate.microsoft.co...js/redirect.js
which is a 17k text file and then there is this one:
http://windowsupdate.microsoft.com/redirect.js
which is a 4k binary and NOT a text file at all when the site is
broken for 98 like right now. Using either the WinUP site or the
Catalog gets both files, exactly why I have no clue but there they are
in your TIF folder - take a look.

When the site works I suspect that the second link above is to a valid
16k text file that is slightly different than the first file, but the
site has not been working when I've tried it to verify that as it
appears to still be catch as catch can since 2/27/07 when I first came
across this problem. The WinUP folks sadly appear to be completely in
the dark this time around, we didn't have much time left at WinUP site
anyway...

Things I've learned reading the redirect.js file.
Win2K is NT 5.0
WinXP is NT 5.1
Win2003 is NT 5.2
Longhorn is NT 6.0
or
Vista is NT 6.0
all depending on which version of redirect.js file you are reading.
They really should get on the same page I would think, use one or the
other but not both.- Hide quoted text -

- Show quoted text -

I wonder if this might not be an issue with transparent proxies,
recent M$ server changes and cache time-outs.

I've just been trying to update a fresh Windows 98SE installation (on
an old machine that can't run anything newer) and found that when I
changed to an open proxy (the Telstra one, if you're in Australia),
everything suddenly started working. I suspect therefore that my ISP
(WestNet) is running a transparent proxy that has been breaking
Windows Update. Could others be having the same problem without
realising it?

(Yes, I upgraded IE, hacked my registry, played with trusted sites,
killed cookies + downloaded files, rebooted several hundred times,
etc. before making this discovery.)

Could be... All I know is that perseverance pays off. If I hit the error, I
close all instances of IE and try again. Usually get in within four or five
tries.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

wrote in message
ps.com...
I wonder if this might not be an issue with transparent proxies,
recent M$ server changes and cache time-outs.

I've just been trying to update a fresh Windows 98SE installation (on
an old machine that can't run anything newer) and found that when I
changed to an open proxy (the Telstra one, if you're in Australia),
everything suddenly started working. I suspect therefore that my ISP
(WestNet) is running a transparent proxy that has been breaking
Windows Update. Could others be having the same problem without
realising it?

(Yes, I upgraded IE, hacked my registry, played with trusted sites,
killed cookies + downloaded files, rebooted several hundred times,
etc. before making this discovery.)