Losing Disk Space By The GBs

vanp said:

Megahertz, I assume you're talking about the "Currently allocated" number on the Virtual Memory panel which I show in post #26. I don't understand what you mean by "(fixed value=min=Max) + set", especially the "set" part. Could you explain the whole thing for me, please? Is the bottom line that I'm supposed to set the "Currently allocated" number to 16384? Thank you.

You select Custom size, add 16384 MB to Initial size and to the Maximum size and press SET to take effect.

"The component store (WinSxS folder) contains all the components that make-up Windows to allow you operate your system. These components are kept to rollback any problematic change or to repair a file that becomes corrupted."

In other words, don't make any changes on WinSxS folder.

Look at this angle:
- The computer is working good.
- There are no freezes or BSOD.
- The HDD is healthy and has a lot of free space.

Why do you care about 1 to 2% of disk space used by system files?

I suggest you use CCleaner once a week and after the cleaning, compare the free space with the one you had a week before.
If the free space begins to drop drastically, it may be a sign of a dying drive. Run Disk info once a month.

If you want to improve your computer, install a SSD
1T SATA SSDs

vanp said:

RickC, I'm not a programmer and can't do a lot of 'command line' type stuff; it has to be pretty simple. After a little looking I've found FolderSizes by Key Metric Software. I will contact them and see if their product is appropriate for what I need. Thanks for responding.

Apologies for the delay in replying. It takes time preparing step-by-step instructions with screenshots.

Understandably, FolderSize purveyors give you a free 'view' version but rarely a chance to track changes without paying for a 'Pro' version.

I could provide a URL to a PowerShell script but you're not a programmer (nor me) and you may have never used PowerShell before... so, how about trying a very, very simple process using the version of PowerShell that is already baked into Windows 10 so you understand exactly what each step does...?

1. Open PowerShell as admin
Right-click on the Start button and choose Windows PowerShell (Admin) from the context menu, then accept the change by clicking on the Yes button on the dialog that appears. This will invoke a PowerShell console with elevated privileges needed to query system folders (like Windows). The console prompt will show PS followed by the current directory - C:\Windows\system32 - and that's not where we need to be, so we'll change that.

2. CD to the root of C:
Change the directory/folder by typing and entering cd.. i.e. Change Directory. The double-dots just tells PowerShell to move up a level in the directory/folder structure.

Type it again (or just use the UP arrow key to repeat the last command) then ENTER until the PowerShell prompt just shows this (a):



You are now where you need to be in order to query the folder structure of your entire C: (system) drive.

3. Change Execution-Policy
Now let's let PowerShell have the permissions it needs to install a module from the PowerShell Gallery for this session only.

Type or copy/paste the following command at the prompt then press the ENTER/RETURN key (b):
Set-ExecutionPolicy unrestricted

You'll see a query... type and enter y (c).



All this means is to relax PowerShell security for this session only.

4. Install the module from the PowerShell Gallery
Now lets let PowerShell install the PSFolderSize module and run a function contained within that module.

Type or copy/paste the following command at the prompt then press the ENTER/RETURN key (d):

Code:

Install-Module PSFolderSize

All this means is to install the NuGet commandline downloader engine that is used to install a PowerShell module to your PC from the online PowerShell Gallery repository... a 'store' much like the Windows Store. The module contains a PowerShell function that contains all the scripting needed. (See here for more info and example of usage.) You'll see the following notification about NuGet:



Just press ENTER/RETURN ('cos the default is Y, i.e. Yes) (e).

You'll see a brief flash of a progress bar then a warning that the repository is currently untrusted:

Press y then ENTER/RETURN to trust the PowerShell Gallery for this session only (f).



The PowerShell module will be installed and the prompt will return to showing PS C:\>

5. Type or copy/paste the following command (g):

Code:

Get-FolderSize | Format-Table -AutoSize > "$Home\Desktop\foldersizes.txt"

What this will do is use the PSFolderSize function in the module you installed earlier to query the starting folder (in this case the root of C:). There will be a delay so be patient... but when the prompt reappears there will be a TXT file on your desktop called foldersizes.txt.

6. Open this TXT file in Notepad and you'll see a listing of foldersizes (in descending order of size) in the root of C:

Next time you see a change in used filespace, use the following command, noting the addition of '1' to the filename:

Code:

Get-FolderSize | Format-Table -AutoSize > "$Home\Desktop\foldersizes1.txt"

You can compare foldersizes.txt with foldersizes1.txt manually or using something like Notepad++'s 'Compare' function to automate the comparison.

You can do this as many times as you like, incrementing the filename as you go.

The point is... you will be able to see exactly what folders are increasing in size. That, IMO, is your starting point.

Once you know what folders are increasing in size without you being responsible, then you can amend the PowerShell query to drill down until you find the culprit.

For example, if you see the size of C:\Windows increasing, change directory to Windows (h):



... and re-run the query (i) as:

Code:

Get-FolderSize | Format-Table -AutoSize > "$Home\Desktop\foldersizes2.txt"

Make sure you wait until the prompt returns before opening the new TXT file.

Hope this helps...

vanp said:

I did the steps to analyze WinSxS. It says no change is recommended, so that settles that issue. Apparently this thing cleans itself on some basis.

Whether analysis recommends cleaning or not, there is almost always something that can be cleaned up. Clean up the component store anyway, typically you could get back up to 1GB. There is no harm in running the clean up using DISM as often as you like, if the store is already clean it will realise that at at 20% and go no further.

And no, WinSxS is not cleaned up automatically. It is only cleaned when you run the clean up, either from the command line using DISM, or if/when Disk Clean up offers 'Windows update cleanup' in 'Clean up system files'.

vanp said:

Megahertz:


If it's not too much of a burden, I still would like to have answers to the 2 questions in my previous post you did not provide answers for.

I think I did. Could you please repeat the questions?

You didn't answer my question: Why do you care about 1 to 2% of disk space used by system files?

vanp said:

RickC:

I have used command-line type stuff like Run and PowerShell under other peoples' direction, so I'm not completely incompetent or unfamiliar with these things. I appreciate the time you spent constructing your post. It's pretty detailed; I'll have to dive into it later, maybe tonight when I get home from work.

No suggestion of incompetency whatsoever. I chose to detail the instructions so I could re-use sections elsewhere over and over... and I was taught, whilst learning to be an Adult Ed tutor, to not make assumptions.