Hi We have noticed our windows server 2016 standard Server is using a lot of space on D drive
This server hosts 4 VM machines on HyperV.
Since the 17/7/20 the D drive has used 1Tb or storage, the odd thing is when we drill down into the D drive folders and select them all the size is only 1.05Tb therefore the space is being used elsewhere. I have checked the hidden files and nothing major shows.
The total space of the D drive is 3.5Tb and under Computer it’s now showing with only 1.16Tb free. Any ideas? Thanks
VirtualizationWindows 10Windows Server 2016Operating SystemsAzure
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
@McKnife: Good suggestion about System vs. Administrator account. Interestingly, TreeSizeFree when run as an Administrator (at least, it asks if it should be run as an Admin... maybe it really means System?) does see System Volume Information.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
McKnife
Interesting observation. You are right, @CompProbSolv - they use system. That wasn't true some years go, they have changed that. So it's no longer needed to run as system, it seems.
Jim Dettman (EE MVE)
As the others have said, run Tree Size, but I usually find that either:
1. The Winsxs folder has gotten out of control - You can clean this up with Disk Cleanup (run as 'admin'). On Windows Server 2016, you'll need the Desktop Experience installed in order to have it. This should be your first stop and is something I'd do no matter what. You can easily have 10's of GB's being chewed up.
2. The CBS.LOG's (Component Based Servicing) have gotten out of control. You can delete them. Just be aware that you are deleting some info that you may possibly want in the event of an install problem. At the very least, I'd save the last one depending on what you find.
3. The software distribution folder has gotten out of control. Again, you can delete this without fear, but it will re-download anything that's needed, so you might want to do this in off-hours. There is a bit of a procedure to follow in order to delete the directory, so leave this to last.
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
Open in new window
(must be executed on an elevated command line). The system account will see all files, even those that the admin account might not have access to.