Windows 10: In Task Manager, Disk full doesn't match display

When I check task manager it says 99% disk, but the highest capacity is 0.7MB, and if you compute them all you get a total of 2.3MB being used. Definitely this is not 99% full. Seldomly, another thing will appear in there that says like 20MB, but as I look at it I cannot figure out how all the memory is being used. This is confusing to me. The usage should be higher if the amount is that great.

Imgur: The magic of the Internet

:)

 

Windows 10 Install 10-second prep churns

Installing through the Control Panel and Windows Update went through the installation process OK, or at least seemed to. The system boots to the point of displaying the login screen, but churns after that point, turning the screen on and off as it displays
the app shortcut icons, first as blanks, then with the actual icon, then back to blanks. The number of app shortcuts, and their arrangement, seems to match the original display.

The task tray displays the start menu icon, the search field, the task view icon, and the notification icon, but doesn't complete the boot process.

Ctrl-Alt-Del from the keyboard works, and I can bring up the Task Manager,or do a reboot or shutdown. The Task Manager display shows the usual long list of system processes, with some varying widely in memory and disk usage.

Any suggestions for getting past the churn?

 

Windows 10 on multiple hard drives.

Is you disk full or is the usage at 100%? The two are completely different.

If you are looking at Task Manager and seeing 100% "Disk" on the Performance tab, it's saying windows is using the disk constantly.

If it's the free space that you see in Explorer, then it's full and you need to do something.

 

Hello ironfist, *Smile

The 99% you see in your screenshot is for the "Total utilization across all physical drives" instead of how much drive space is used. Basically for activity.

 

Right. But what is the reason it is 99% when few things are being listed? Select the link I posted to observe a screenshot.

 

You definitely have something causing a lot of disk activity.

Click on the "Performance" tab in Task Manager, click on the "Open Resource Monitor" link at the bottom, and then click on the "Disk" tab in Resource Monitor. It'll give you a more detailed idea of what is causing disk activity.

 

This is being the situation again. Disk usage is at 100% but if you compute all the things that are using space it's about under 7MB.

 

Is it possible the disk usage is being confused with disk space [storage]? Right-clicking the drive letter in File Explorer then clicking Properties will give the disk space used and available for a rough total [some things are hidden and not always added to the result].

 

As a test, start killing the process of each item one at a time and checking a bit after each one to see if the disk activity goes back to normal. If it does right after killing a process, then that may be the culprit.

If you kill something that cripples Windows, you can just restart the computer.

Just to rule out an issue with the drive, run check disk on the drive to see what it reports.

 

Suggestion.

Run the right slide bar down so we can see what else you have running.

Also from Task Manager tick on "Startup" and post what is there.

It would also be very helpful to completely fill in your system specs.

Here is a tutorial by Brink that will help you do that.

System Specs - Fill in at Ten Forums Site Use Tutorials

Jack

 

Here comes a screenshot from resource monitor during a time when disk was 98%. First it was blank but that might have been because my computer was slow:




next it showed what you see here

 

Have you changed anything here.





Jack

 

I do not even know which menu has those settings.

 

Now it's happening again and I have barely anything running.

 

You might want to shut off utorrentie and other processes associated with it (if not uninstalling uTorrent altogether) and see if the problem persists to eliminate it as a cause. I'm not saying definitively that uTorrent is the culprit, just that it's one of the first things I'd try to take out of the equation.