Can't install because of SP2

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I want to install Windows Defender, but cannot install SP2 on my computer. I
have tried everything, but it just doesn't work. I have XP and all the
requirements. Does anyone know if Microsoft has fixed SP2? Thanks!!
 
SP2 doesn't need fixing--something about your particular Windows install
does. Can you say more about what happens when you try installing SP2? The
general recommendations are to get the machine clean of malware, and to use
the network administrator full install version, if possible.
 
Id advise to start by running System File Checker on your system, then try
installing SP2, although you may have tryed it, any error messages would help
further as Bill stated.

For anyone who doesnt know:

1. Get your Windows Media in your drive, (cancel any install options)
2. Click 'Start' then 'Run',
3. In the run box type "sfc /scannow". Without the " and a space after sfc
4. Go have a drink and maybe some food, The SFC box will go once finished.

Regards,
Tom
 
What happens is after I install sp2, the computer reboots and it seems to
work fine and then when it's at the screen where it says windows is starting,
(almost the end of the startup), it reboots itself and then it starts again
and then it goes to a black screen and says that windows can't load cause of
some new hardware maybe. It lists the safe modes I can use to get into
windows and then it says I can start windows normally. It just keeps going
in this cycle unless I go in with safe mode and just get rid of sp2!!! I
have an Athlon processor, maybe that's it? I have more than enough memory
and it's only 2 years old, so nothing is outdated that I know of. And, it's
a valid copy of windows, I've been getting harrassed about that!!! If you
can offer any insight, that would be great!!! Or else, I'm just going to
take it to my computer guy..........
 
It isn't the Athlon processor, unless, perhaps, the motherboard is set to
overclock something?

This does sound like a hardware or low level driver issue of some sort. I
think I'd check with the motherboard vendor to be sure that the newest
updates to drivers for motherboard-provided features and the chipsets
involved are in place.

--
 
Back
Top