Freezes When Logging Out/switching Users/shutdown

I'm using a Windows XP PRO Service Pack 2 with 512RAM and 400GB (300 available) and I've never had this problem before, it started right after I got back from my vacation. My computer was left unused for 1½ month and when I returned I faced this problem. When I try to logout the computer freezes at the blue screen while it's saying "Logging out.." for about 5-10 minutes. Shutdown freezes for about 30 minutes and switching users for about 1-2 minutes. What causes this? I've never had this problem in 2 years. Thanks in advance, Fality

Long-Shot — ? Since you were away for 1 1/2 months, you may have missed out on quite a few critical updates and patches. Typically the "automatic" setting for MS Updates uses the time just after the users "signs out" (turn off) to download and install MS Updates. this may be happening to you. Unhappily, during that same time, Microsoft Installer went through an Update, which didn't always install itself properly. Further, during that time, Microsoft offered updates for .Net Framework 1.1 and 2.0 These .Net Framework updates suffered download and installation failures for large numbers of users. You may be experiencing repeated attempts of AutoUpdate to download the same failing files (Installer, and .Net Framework) ________ I'd recommend that you do a manual update (not express) and get these items (particularly Installer) properly updated onto your machine. If you experience download or installation failures of these updates during your manual updating at MS, then please notice exactly which updates fail to install (write down their exact name and reference information) Then download and run the MS Installer Cleanup Utility, targeting these failed update installation particularly and not targeting any other installations displayed in the list. After you run the Installer Cleanup Utility, re-visit the MS Updates to attempt a successful manual installation of those items. Best Regards

Long-Shot — ?

Since you were away for 1 1/2 months, you may have missed out on quite a few critical updates and patches.
Typically the "automatic" setting for MS Updates uses the time just after the users "signs out" (turn off) to download and install MS Updates.

this may be happening to you.

Unhappily, during that same time, Microsoft Installer went through an Update, which didn't always install itself properly.
Further, during that time, Microsoft offered updates for .Net Framework 1.1 and 2.0
These .Net Framework updates suffered download and installation failures for large numbers of users.

You may be experiencing repeated attempts of AutoUpdate to download the same failing files (Installer, and .Net Framework)
________

I'd recommend that you do a manual update (not express) and get these items (particularly Installer) properly updated onto your machine.

If you experience download or installation failures of these updates during your manual updating at MS, then please notice exactly which updates fail to install (write down their exact name and reference information)

Then download and run the MS Installer Cleanup Utility, targeting these failed update installation particularly and not targeting any other installations displayed in the list.

After you run the Installer Cleanup Utility, re-visit the MS Updates to attempt a successful manual installation of those items.

Best Regards

Thanks for the help, but I did all possible updates I could think of including anti-virus, Ad-aware, Spybot, Windows Defender etc.

I wasn't able to edit my post but I've had Auto-Update turned off for a long while.

The "defining event" that you have stated is the 1 1/2 months of computer inactivity.
That downtime is very unlikely to have "caused" the problem you are facing.
More likely is that "something else" has occurred, or that "something happened" during that 1 1/2 month period.

Something else happened possibilities ….
Extreme heat
Extreme cold
Extreme moisture/humidity
Debris or insects entered the case tower
(no offense meant to you individually, but I've seen some towers with paper-wasp, mud-wasp, cockroach, and ant infestation that have physically blocked the air intake and or fans, or have bridged across components or from motherboard to grounded case structure, or filled the spaces between the heatsink fin elements or damaged wiring and switch components.)
(I've seen cases with excessive dustbunnies run just fine when kept warm and active, but after a period of inactivity with high humidity the dust/debris may fall upon other components, or become hardened, locking up a fan.)
Admittedly these may sound like extreme cases, but it can happen in the best of households.

–Therefore please check inside the case for damage or debris.
____________________

It is also possible that your location experienced a power-surge during the 1 1/2 months that could have invaded your machine through modem, router, printer or other peripherals that may have been left connected and possibly powered on. Power-surge damage can happen whether or not a machine is turned on.
You probably wouldn't know about a power-surge, except maybe if the kitchen microwave settings had changed, or if various digital clocks had become reset or left blinking.

The more likely version of "something else happened" is that a new hardware or software application has been added after your returned. Any chance there?
Or that you've run an application that you hadn't run recently, whose program or drivers had become corrupted but undetected because it hadn't been run.

Since all of the above are "unlikely", this is going to be a detective process, ruling out one possiblity at at time.
The most likely is a Hardware issue or a hardware Driver.
Next most likely is incompatible or conflicting software.

Here is the best Guide for your detective work.
I suppose I could keep guessing, and you could keep telling me that my guess doesn't apply.

Probably better for you to go at it in a systematic way.
Here ya go:
http://www.aumha.org/win5/a/shtdwnxp.php

Keep us posted with your progress. We can all learn from your success.

Best Regards

I've cleaned inside the case and I do it once a month. I also pulled all the cables before I left (including TVs, microwaves, videos etc.) Thanks for the guide, I'll read it and see what I can do.

No success, but turning off the welcome screen bypassed the problem.