Well, yesterday I downloaded my last ever Windows critical Update.

As I have previously posted, I never download a critical update that is less than three months old.  This is to give Microsoft time to detect the inevitable flaws and fix the original update.  Yesterday, I went to the Windows download site and found a couple of critical updates from May.  I downloaded and installed them and now my PC refuses to restart.  I can go to Start > Shut Down and close the thing down OK, but if I go to Start > Shut Down > Restart, it just  hangs at the closing down screen and I have to turn off the power and switch back on and then sit there while Scandisk does its stuff.

Microsoft sucks big time!

Hi, Simon.

Yes it's Win98SE.

Hi again, Simon.  Thanks for the link.

I've been playing around for a couple of hours and have traced the source of the problem.  As Windows shuts down properly, but will not just simply restart, I figured that some running program was not closing down quickly enough in restart mode.  I went into Safe Mose several times, and restart worked without a problem.  That confirmed my suspicion.  I then tried restarting by closing down one running program in each attempt and eventually discovered my firewall is the culprit.  If I Cntl-Alt>Delete and end the firewall, restart works without a problem.

The only thing bothering me now is that 24 hours ago I didn't have this problem until I downloaded a critical update.  Why it should stop my firewall from closing properly, I don't know.  I suppose that's critical updates for you.  The very word "critical" is totally appropriate.  Downloading them is literally feeding the computer poison.   Even the healthiest system can end up in a critical condition after a Microsoft update.

 

Which firewall were you using, out of interest, Dave?  You really don't want to be without one at the moment, especially with this Blaster thing flying about.

I love conspiracy theories Adept.      

Yeah, I use Sygate as well, and it's one that I would recommend, however, it is worth going into the Applications list, right clicking on Generic Host Process for Win32 Services, selecting Properties > Advanced, and un-ticking the 'act as server' box.  This will ensure that your Port 135 (which is the one that this Blaster worm is targetting) is fully stealthed, according to the Shields Up test at www.grc.com.

So far you are ok Dave but who knows what "son of mad blast" will be or do and to which OS.
If any port is open unnecessarily you are better off closing it if you can :doggie: