Member Avatar for BTVS

Hi, I have a GW4500, WinXP SP2, 2 gig mem. After working on the PC for awhile when I select Start>Shutdown I then have to wait almost 2 minutes for the "Shut Down Windows" to appear. This is happening to 3 of my users. It began about 1 week ago, no changes had been made to their desktops prior. I have 150 others with the same image that are fine. Any ideas?

  • 3 Contributors
  • 2 Replies
  • 218 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Member #533276

Dani AI

Generated

Brief expert summary (for ): three GW4500 desktops (WinXP SP2, 2 GB) pause ~2 minutes before the “Shut Down Windows” dialog appears while ~150 identical-image PCs are fine. Start by isolating third‑party software and services (clean‑boot/msconfig), then look for environmental differences (network/printer mappings, AV, drivers, local updates) between the affected machines and the working image. As suggested, a clean boot is the best first step. How to perform a clean boot (msconfig). (support.microsoft.com)

Quick diagnostic checklist to reproduce/isolate the hang:

  • Check Event Viewer System/Application entries for the shutdown timestamp (look for driver, spooler, service errors).
  • Temporarily unplug the network cable and try shutdown; if the delay disappears, a mapped drive, printer or server dependency is likely. Microsoft KBs note mapped drives and desktop‑update components can stall shutdown. ()

If the above finds nothing, try targeted tests (on one machine first): stop the Print Spooler, disable nonessential AV services, and do a clean boot to narrow the offending service/startup. If those point to an app or service that won’t close promptly, a conservative registry timeout tweak can help (backup registry first). Common keys and safe starter values are below; restart required for changes to take effect.

HKCU\Control Panel\Desktop
  AutoEndTasks = "1"
  HungAppTimeout = "1000"
  WaitToKillAppTimeout = "2000"

HKLM\SYSTEM\CurrentControlSet\Control
  WaitToKillServiceTimeout = "2000"

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
  ClearPageFileOnShutdown = "0"

Guidance and background on these registry entries and risks: How‑To‑Geek explains the HungApp/AutoEndTasks/WaitToKillAppTimeout edits, and Microsoft KBs document WaitToKillServiceTimeout behavior and the pagefile‑clearing policy (which can add minutes if enabled). Test changes conservatively and watch for data‑loss risk when forcing apps/services to close. (howtogeek.com)

Because only three machines are affected, compare what differs from the 150 working systems: installed software, printer mappings, NIC drivers, recent Windows updates or local GPO scripts, and user profile differences. Capture msinfo32 and the Event Viewer logs from an affected and a working PC and compare timestamps — that comparison is usually the fastest way to spot the root cause.

Recommended Answers

All 2 Replies

Member Avatar for shyamogoti

possible reason is some of the programs are not closing.Open msconfig to check startup programs and see that they are working properly.

Member Avatar for Member #533276

Hi...

Like shya* said.. and check this out... :

1.

2.

3.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.