A third-party 32-bit app on Windows 2000 Server stops responding; CPU remains at 100% even after ending the app. Task Manager shows no apps and the process Application.exe is gone. To restore CPU usage to normal, what should you do next?

Introduction / Context: Sometimes a GUI task crashes, but helper components, services, or child processes that it spawned continue to consume CPU. On Windows 2000 Server, the Applications tab may be empty after ending the app, yet a background process can still peg a CPU. This question tests post-crash remediation: finding and terminating associated processes that persist after the visible program closes.

Given Data / Assumptions:

• Application.exe has been ended; CPU stays at 100%.
• No other “applications” are visible, but background processes can remain.
• The goal is to return CPU to the normal 20–30% range without rebooting.

Concept / Approach: Switch from the Applications tab to the Processes tab and sort by CPU usage. Identify any processes tied to the problematic application (e.g., helper EXEs, service-hosting processes if the app registered components) and terminate them in a controlled fashion. If the app used sub-processes, they may continue to run even when the parent exits. Stopping unrelated services like Server or Workstation does not address runaway CPU from an app component; restarting Explorer.exe is only relevant if Explorer is the offender.

Step-by-Step Solution:

Verification / Alternative check: After termination, CPU should return to baseline. Review Event Viewer and application logs to confirm no system service is looping due to the app crash.

Why Other Options Are Wrong:

• Restart Server/Workstation services: not targeted; unnecessary service disruption.
• Restart Explorer.exe: helps only if Explorer is at fault; not indicated here.
• None of above: incorrect; ending remaining child/background processes is appropriate.

Common Pitfalls: Looking only at the Applications tab; failing to sort by CPU; terminating critical system processes instead of the offending child; ignoring service-hosted components that need a service restart or server reboot if they cannot be cleanly ended.

Final Answer: Use Task Manager to end any related child processes.