Press Ctrl + Shift + Esc, open Processes, and select the Disk column until the busiest process is first. Match that process to the four states below and stop when Disk usage falls and Windows responds normally. Do not disable SysMain, Windows Search, Microsoft Defender, or the page file as a universal fix.
Update, scan, install, or copyLet the named task finish
One ordinary app stays firstClose and update that app
The Windows drive is nearly fullReview Cleanup recommendations
Unknown process or no clear causeScan, check health, then isolate
1
Find the process using the disk
Press Ctrl + Shift + Esc, select Processes, and select the Disk heading until the largest number is at the top. Watch it while the PC is slow and record the process name, total Disk percentage, and what you were doing; do not end System, Service Host, or another process you do not recognize.
2
Let a named Windows task finish
If the top process belongs to a file copy, installer, Microsoft Defender scan, cloud sync, or Windows Update that visibly says it is running, let that task finish and test again. For Windows Update, open Settings > Windows Update and restart only when its status asks you to; if Disk usage drops and the PC responds normally, stop.
3
Close only the identified app
If one ordinary app remains first after its active work should be finished, close that app with its normal Exit or Close command and watch the Disk reading again. If that resolves the slowdown, install the app's current publisher-supported update before reopening it; do not stop an unfamiliar Windows process or disable a service for every startup.
4
Free space when the drive is nearly full
Open File Explorer > This PC and check the free space on the Windows drive. If it is low, open Settings > System > Storage > Cleanup recommendations, review each category, remove only files you recognize, then return to Task Manager and repeat the idle check.
5
Scan an unfamiliar process
If the process is unfamiliar or the sustained activity began unexpectedly, search Start for Windows Security and open Virus & threat protection > Quick scan. Keep real-time protection enabled, follow only the result Windows Security reports, and recheck Task Manager when the scan finishes.
6
Check Windows health before repairs
Open Windows Security > Device performance & health and read the current Health report. Follow only a reported Storage capacity or App and software recommendation; if the drive disappears, reports a hardware error, or makes unusual mechanical noises, stop, back up important files, and use the PC or drive maker's diagnostic instead of running repeated repair scans.
7
Use a clean boot as the last isolation
If Disk remains at 100% while the PC is otherwise idle and the earlier checks found no cause, follow Microsoft's linked clean-boot procedure and record every startup item you disable. If the problem disappears, re-enable items in the documented groups to find the owner; if it remains, restore normal startup and give the PC or drive maker the process name, drive model, Health report, and test result.
If Disk reaches 100% only during a known copy, install, update, or security scan and returns to normal afterward, do not keep changing Windows. The completion result is the important distinction.
If System or Service Host stays first, do not end it. Record the expanded service name, time, and Windows Update or security status, then use Microsoft's support guidance or the PC maker's support channel with that evidence.
If the issue began immediately after a storage or chipset driver update, use the PC maker's documented rollback or replacement package. Do not install a driver from a download mirror.
Do not disable SysMain, Windows Search, Connected User Experiences, Microsoft Defender, or virtual-memory management as a universal cure. Those changes can hide the responsible process, reduce Windows functionality, or weaken protection without repairing the drive.
ⓘ Sources and verification
Checked against official documentation on . Scope: Windows.
Source-checked against current Microsoft documentation. Registered capture 207 was rejected after full-resolution inspection because it is sorted by Memory and shows 1% Disk, not the 100%-disk diagnostic state. The reader's own Disk-sorted process list is the decisive evidence, so this revision is intentionally image-free.
