<<Two caveats: never interrupt a service pack installation and cleanup, ever. That could be one reason why things aren't going as they should. The same goes for any kind of Windows update really.>>
Just a comment about SP3. The first time I ran the SP3 update (when it was first available) I left the cleaning up process running for about 4 hours! I used the task mananger in desperaration in order to stop it and everything seemed to be OK. Searching on the internet I then found that this appeared to be a common problem and that many had this. Using the task manager to stop the process during cleanup was the ONLY way to exit the SP3 update for many. I have had no problems with Windows since until this new one now.
It shouldn't have been like that, but I guess a lot depends on available resources and whether or not other processes are running. How much memory (RAM) is installed and how much free hard drive space? The help article I wrote mentions that it's best to stop any unnecessary running processes during a service pack update, that would include Windows Defender along eith McAfee and anything else such as software updates, screensavers, email polling etc. Also Microsoft provides free support for problems with any update. They can be of great help and have been to me in the past.
I still have XP SP3 installed on 2 virtual machines here and remember when I was running it as a main system that the worst update was actually SP2. SP3 seemed much easier to me. But processes hanging seemingly for hours without end I know only too well and all I can say is be patient and eventually they will complete.
The fastest/easiest 'cure' for slowness such as this is to install more memory (RAM) hence my asking what memory you have installed. But one has to bear in mind that XP has limitations on how much RAM it can handle. I went from 512mb up to 4gb on my original XP PC and managed to utilise about 3.2gb of that with the help of my graphics card (a rather complicated relationship and slightly beyond my ability to explain). XP wont recognize anything higher due to system limitations. Spare hard drive space is the other factor as Windows needs space for temporary files whenever doing updates (& other processes).
You should perhaps enlist outside help or at least the help of a forum specialising in XP or Windows generally as it is vital you update. At the present time your system is at risk and is basically unsupported by Microsoft.
I'm sorry I don't have the time to go through it step-by-step here with you but there are forums out there that will and any local PC repair shop can do it for you for a modest fee I am sure. Better to be safe than sorry.
If I've misunderstood and you are using SP3, then ignore this.
Message was edited by: Ex_Brit on 06/06/11 8:16:10 EDT AM
An added thought that original warning about files being changed is most likely coming from the fact that any security software changes Windows Security Center settings and basically takes control of it. It should only be a one-time warning and should pass.Message was edited by: Ex_Brit on 06/06/11 7:04:21 EDT AM
<< It shouldn't have been like that, but I guess a lot depends on available resources and whether or not other processes are running. How much memory (RAM) is installed and how much free hard drive space? >>
In fact my computer updated to SP3 and I have been receiving all Windows updates since - this is no longer possible with XP SP2. I was of course not running Windows Defender then as this does not work with XP SP2 but needs SP3. My computer, whilst not up to the performance available with current machines is still quite good (3 GHz Intel Pentuium 4 with 2 GByte RAM and about 100 GByte free hard disc space at the time - still with about 70 GByte free).
I updated my wife's earler machine (with a slower Intel Pentium 4 and less RAM and a smaller hard drive - 80 GByte TOTAL) from SP1 to SP2 using a CD bought from Microsoft and then, after installing all the subsequent Windows updates needed first, installed SP3 from the same file I used on my computer.This sequence of processes worked on that machine without any problems.
So these updates do not seem relevant to the present problem.
Funny thing computers!
DerekMessage was edited by: DerekShaw
Funny thing computers!
Aren't they just!!
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: