Yes, I suggest trying a repair install.
And yes, this points up the problem with critical updates. The only reason
I install most of them is because I need to be able to see issues and I hope
find a way to deal with them. Unfortunately, it's not that simple. With so
many different setups and configurations it's difficult to create an update
that won't effect some users adversely.
As far as I'm concerned, as long as you have a firewall, antivirus software
and a router for good measure, you don't need most of the security updates.
If an update is specific to servers or networks of which the user is not a
part, it's a good bet it's safe to pass up the update.
One needs to have an understanding of why they are labeled critical and
that's because some hacker has found a way to exploit some part of the
operating system, hence, the hole is legitimate but the user may not
necessarily fall into a category of high danger.
If you are on an office network or any system that is open to the Internet
as in a server for web sites or commerce or just corporate communications,
by all means, install those updates or make sure the system administrator is
aware and installs them.
However, the average home user, even one with an always on broadband
connection likely doesn't need most of them. Read the information about the
update and see if it even applies to your setup or situation. As I said
above, if you have a firewall, antivirus software that you keep updated and
a router, you are pretty well protected. NOTE: If you do a lot of file
downloads, participate in chat, especially IRC chat, use file sharing sites
and software, these open gaping holes in your system and by all means, do
all the updates. Even if your system doesn't appear to be specifically
mentioned, the items I just mentioned place the home user in the same
category as enterprise users.
--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org:
http://www.dts-l.org/
"RICHARD.H.PITT" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> Thanks for the information.
> I tried the first method and up to press no blue screens however, now my
> monitor settings keep flashing up during start-up and on shutdown a white
> grid appears in addition to this it now takes an age to shut down.
> Why should installing critical updates cause this? and should we all steer
> clear of them.
> Would you suggest I now try a repair install.
> Help please this is driving me mad.
>
> Rich
>
> "Michael Solomon (MS-MVP-Windows Shell/User)" <user@#notme.com> wrote in
> message news:(E-Mail Removed)...
> > If this is a relatively recent issue, you might try using System Restore
> to
> > take you back to a time when this worked properly. If that doesn't
> resolve
> > it, try the information below.
> >
> > The following assumes you have an actual XP CD as opposed to a restore
CD
> or
> > restore partition supplied by your PC manufacturer.
> >
> > Go to Start, type sfc /scannow in the run box and press enter. Note,
> there
> > is a space between sfc and the forward slash. You will be asked for
your
> XP
> > CD. Be aware, upon inserting the CD the XP setup screen may appear,
this
> is
> > not a part of sfc /scannow, rather it is being invoked by autorun.
Simply
> > minimize the screen and allow sfc to continue.
> >
> > If the above fails to resolve the issue, try a repair install as
follows:
> > Be sure you are well backed up in case there is a problem from which you
> are
> > unable to recover. NOTE, while a repair install should leave your data
> > files intact, if something goes wrong during the repair install, you may
> be
> > forced to start over and do a clean install of XP. If you don't have
your
> > data backed up, you would lose your data should that eventuality occur.
> >
> > Boot from the CD. If your system is set to be able to boot from the CD,
> it
> > should detect the disk and give a brief message, during the boot up, if
> you
> > wish to boot from the CD press any key.
> >
> > Once you have pressed a key, setup should begin. You will see a
reference
> > asking if you need to load special drivers and another notice that if
you
> > wish to begin the ASR (Automatic Recovery Console) depress F2. Just let
> > setup run past all of that. It will continue to load files and drivers.
> >
> > Then it will bring you to a screen. Eventually, you will come to a
screen
> > with the option to (1) setup Windows or (2) Repair Windows Installation
> > using the Recovery console.
> >
> > The first option, to setup Windows is the one you want and requires you
to
> > press enter. When asked, press F8 to accept the end user agreement.
> Setup
> > will then search for previous versions of Windows. Upon finding your
> > version, it will ask if you wish to Repair your current installation or
> > install fresh. Press R, that will run a repair installation. From
there
> > on, follow the screens.
> >
> > --
> > Michael Solomon MS-MVP
> > Windows Shell/User
> > Backup is a PC User's Best Friend
> >
> > "RICHARD.H.PITT" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Ever since I downloaded and installed the latest XP critical updates I
> > have
> > > been getting the dreaded blue screen.
> > >
> > > This happens about once or twice a week and I have not installed any
new
> > > software.
> > > The problem seems to be caused by a driverX.sys file.
> > > The machine dumps memory and the counter gets to 100 and then boots
back
> > to
> > > the BIOS screen.
> > > The disk is checked and no errors found and then after a long delay xp
> > > resumes normal service.
> > >
> > > Any ideas would be helpful.
> > >
> > > Rich
> > >
> > >
> >
> >
>
>
Similar Threads
