On 07/08/2018 07:29 PM, Brian Gregory wrote:
On 07/07/2018 18:51, Paul wrote:
Art wrote:
freface wrote in newsho1la$1h34$1
@adenine.netfront.net:

Win 7 Pro.Â* All updates.

C:\ is full.
Deleted obvious stuff but only got 200MB freed.
Googled and got confused.

Please a little spoon feeding would help me.

WinSxS has 13G in the folder.

I do not see any other large file areas taking up space.

TreeSizeFree being used to look at C:

Suggestions please.


I found that Resetting your restore point back to Zero free up a lot
of Gigs for me.

Yes, but while you're in System control panel and the
System Protection area, you should adjust the slider for
a smaller maximum space. That prevents "abuse" by
the System Protection feature. For example, I might set
it to 3GB, rather than 300GB.

Some backup programs use VSS Shadows, and those could
be lurking in a similar storage area. They're in
C:\System Volume Information. If you're using fancy
backup software, you should check whether there
are any "space" settings for when the tool uses
space on your disk drive. I thought the default on
some of these, was around 30-35%.

The worst part of Windows, is there is really *no*
utility that shows all allocations. I would have to
conclude from this behavior, that when you use a
backup program (even Macrium), it doesn't actually
copy everything, and there will be a few items that
don't get backed up.

I used to think nfi.exe (Microsoft) could see everything,
but it's missing at least four files.

Viewing NTFS from Linux can be educational, but you
also have to be careful. I had a Windows 7 C: trashed
while doing that. I was looking in System Volume Information
and specifically at VSS Shadow Files (which aren't "normal"
files). So if you do go on a serious hunt for stuff to remove,
you should have a *backup* in hand, before you begin. I
tried to reproduce the failure case a couple of months
ago, and couldn't succeed in getting it to happen
a second time. But for me, one incident is enough.
Since I'd made a backup only two hours before the
incident, I was well prepared, but... purely by accident.
I didn't actually do the backup because I was expecting
trouble. I did the backup because it had been
several months since the last one. It's possible that
some leftovers from the backup operation, actually
primed the failure case to happen.

Viewing NTFS from Linux now, also suffers from problems
caused by Windows 10. Windows 10 creates partitions with
damaged $MFTMIRR, which prevents Linux from mounting.
Windows 7 CHKDSK can fix it. Windows 10 also uses a
new compression reparse point type, and Linux gets
"I/O error" or similar if it hits one of those. Windows 10
makes a Swiss Cheese out of the Linux ability to help.
And when stuff like this happens, it's not an accident.
(Windows 7 created partitions, are still perfectly usable.
And Windows 7 can prepare a GPT disk for you too.)

Â*Â*Â* Paul

I generally give System Protection around 15% of my C: drive to start
off. Then I wait for it to fill up and see how far back the oldest
restore point is. If it seems way too old reduce percentage, if it seems
way to recent increase percentage. I like to be able to go back at least
a week if I should need to.

Good idea if you install or change things 3 times a day. But what
about the person that loads one program a month, and the monthly
updates, well that's 2. I would like to keep either 5 or restore
points or a week, whichever I hit first.

Al