Re: Real Fix for the update time issue...
From: HungryCharley (no.room_at_the.top)
Date: 05/05/04
- Next message: Cadderly: "RE: update time error..... how many more?"
- Previous message: HungryCharley: "Re: update time error..... how many more?"
- In reply to: Matthew330Ci: "Real Fix for the update time issue..."
- Next in thread: Nowa: "Re: Real Fix for the update time issue..."
- Reply: Nowa: "Re: Real Fix for the update time issue..."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 05 May 2004 02:36:30 -0400
This has been posted several times in the discussion today. Please
look around a little from time to time.
=========
This is a repost of information originally posted by Harold on
5/3/2004 at 3:16PM as "Workaround for Error 0x800c0008", with added
explanation by me.
Harold wrote:
"I found a workaround in Knowledge Base Article 830066. I added an S
to the end of the http:// - I checked ok in the security warning
boxes. Scan for updates then worked ok without any further Error
Mesages."
My notes:
What I found was that if the URL that appears at the top of the MS
update page:
http://v4.windowsupdate.microsoft.com/en/default.asp
is replaced with this (only an 's' is added to the http string:
https://v4.windowsupdate.microsoft.com/en/default.asp
it WORKS!!!
I have only tried this in Windows2000, but give it a shot.
hungrycharley
---- HungryCharley "A witty saying proves nothing" On Tue, 4 May 2004 23:21:50 -0700, "Matthew330Ci" <anonymous@discussions.microsoft.com> wrote: >Thanks but it doesn't help in my case since my internet >firewall has always been on. > >The self diagnosis thing recommends clearing out the >internet files and cookies, i cleared out the files but i >do not want to lose all of my cookies so i haven't deleted >the cookies, has anyone tried deleting the cookies and the >files and see if it made a difference? > > >>-----Original Message----- >>OK, here's how you can get rid of the issue and install >the updates. I didn't have the issue, by my parents did, >so I've been troubleshooting it for a couple hours now... >> >>This will work for XP Pro I believe (as it has a built-in >firewall). XP Home users see the bottom... >> >>Unplug your network cable from any network, and restart. >> >>Go into the Control Panel, Network Connections. Right- >click on your network connection, and click the "Advanced" >tab. >>If you don't see the advanced tab, it's because the >system doesn't think you are an administrator - you need >to reboot again. >> >>On the advanced tab, enable the firewall. Don't change >any settings, just click OK. Back on the network settings >page, your internet connection should now say "Enabled, >Firewalled". >> >>Now that you're firewalled, the Sasser virus can not get >in. No shutdowns, and windows update should run fine. Use >the Windows update to install that (and any other) >critical updates. >> >>Once updates are installed, you can remove the firewall, >but really, unless you're punching holes in it for special >apps, I'd leave it on. And while you're at it, turn on the >Windows automatic update facility (to prompt you), and >install when it asks you to. That helps to get updates to >you before the mass spread hits you. >> >> >>Now for those of you who have XP Home and do not have the >built-in firewall, you're still out of luck (I think, >don't have a copy here). You need a firewall router... >> >>Here's my soapbox rant for the night... >>This (and almost every other virus that's hit lately) can >be avoided with a simple addition of a firewall router to >your network. Even if you have no need for the "router" >part of the setup, you can add something like a D-Link DI- >604 router (about $50 CDN these days) between your modem >and your PC, and the firewall protection will be worth >every penny. My machine has never been hit, the main >reason is because it's "hidden" behind the router. Sasser >and others can't see my PC, they can only see the router, >and the hack doesn't get through. Yeah it's $50, but how >much time did you spend fighting with this damn virus, and >the last one, and the next one... ;-) >> >>Hope it helps a few of you, best of luck! >> >> >>. >> ---- HungryCharley "A witty saying proves nothing"
- Next message: Cadderly: "RE: update time error..... how many more?"
- Previous message: HungryCharley: "Re: update time error..... how many more?"
- In reply to: Matthew330Ci: "Real Fix for the update time issue..."
- Next in thread: Nowa: "Re: Real Fix for the update time issue..."
- Reply: Nowa: "Re: Real Fix for the update time issue..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|