Post Win10 upgrade - cleanup

On Sat, 6 Jun 2020 09:04:44 +0200, occam wrote:

I ran cleanmgr.exe, but the returned options did not include anything
that resembled the 17.9GB that needs to be cleaned.

On Sat, 06 Jun 2020 04:11:10 -0400, Paul wrote:

Click the "System" button, the dialog box disappears
and comes back, and then it works at the second level.
It will then list the Windows.old item.

Paul is correct.

I ran the cleanmgr with and without that "clean system files" button.
o It cleaned almost nothing without that "clean system files" checkmark.

But after hitting "clean system files", it added & checked a new box.
o Which, in effect, wiped out the "Windows.old" directory.

Here are my before-and-after-cleanmgr results just now:
o After conversion of Win10Sv1909 to Win10Hv1909 to Win10v2004
and after running cleanmgr _without_ hitting the "clean system files"
button:
https://i.postimg.cc/cCggQb09/smode08.jpg
o After disk cleanup (and after pressing [Clean System Files])
https://i.postimg.cc/2jbPtNjH/smode09.jpg

These are the build numbers:
(1) Win10S Version 1909 (OS Build 18363.836)
(2) Win10Home Version 1909 (OS Build 18363.836)
(3) Win10Home Version 2004 (OS Build 19041.264)

I wasn't worried about sizes, but to help out with the datapoints,
here's the rough end result after conversion of
Win10S - Win10H - Win10H v2004 - Win10H v2004 system cleanup.

(1) Win10S = Used space = 18.8GB
(2) Win10H = I didn't check the space
(3) Win10H v2004 before diskcleanup = Used space = 34.8GB
o C:\$SysReset = 66.2 MB, 13 Files, 6 folders
o C:\$WinREAgent = 0 bytes, 0 files, 1 folder
o C:\hp = 1.22 MB, 161 files, 115 folders
o C:\OneDriveTemp = 0 bytes, 0 files, 1 folder
o C:\PerfLogs = 0 bytes, 0 files, 0 folders
o C:\Program Files = 394 MB, 809 files, 189 folders
o C:\Program Files (x86) = 163 MB, 1,534 files, 430 folders
o C:\Program Data = 298 MB, 644 files, 458 folders
o C:\SWSetup 0 MB = 33.1 MB, 1 files, 1 folder
o C:\System.sav = 170 MB, 800 files, 121 folders
o C:\Users = 372 MB, 2,245 files, 2,223 folders
o C:\Windows = 17.0 GB, 90,424 files, 21,562 folders
o C:\Windows.old = 26.3 GB, 202,338 files, 51,649 folders

Then I ran "Win+R cleanmgr" with all boxes checked.
o Specifically I hit the "clean system files" button.

(4) Win10H v2004 after diskcleanup = Used space = 18.9GB
o C:\$SysReset = 66.2 MB, 13 Files, 6 folders
o C:\$WinREAgent = 0 bytes, 0 files, 1 folder
o C:\hp = 1.22 MB, 161 files, 115 folders
o C:\OneDriveTemp = 0 bytes, 0 files, 1 folder
o C:\PerfLogs = 0 bytes, 0 files, 0 folders
o C:\Program Files = 394 MB, 809 files, 189 folders
o C:\Program Files (x86) = 163 MB, 1,534 files, 430 folders
o C:\Program Data = 298 MB, 644 files, 458 folders
o C:\SWSetup 0 MB = 33.1 MB, 1 files, 1 folder
o C:\System.sav = 170 MB, 800 files, 121 folders
o C:\Users = 356 MB, 1,971 files, 2,200 folders
o C:\Windows = 16.8 GB, 90,227 files, 21,494 folders
o C:\Windows.old = (this was the only directory wiped out)
--
I'll need to look up more about how best to delete the system folders.
C:\$SysReset
C:\$WinREAgent
o C:\SWSetup
o C:\System.sav

On Sat, 6 Jun 2020 09:47:30 +0100, Andy Burns wrote:

I ran cleanmgr.exe, but the returned options did not include anything
that resembled the 17.9GB that needs to be cleaned.

run it "as admin" it'll offer to clean-up more

I just ran cleanmgr as admin, and it didn't do anything it didn't already
do as a user (who had admin privileges by default).

1. Win+R cmd{control+shift+enter}
2. cleanmgr

Here's a screenshot of that process run moments ago:
https://i.postimg.cc/CMt0T9P3/smode10.jpg
--
The trick isn't running as adming; it's selecting "clean system files".

On 06/06/2020 10:11, Paul wrote:
occam wrote:
On 05/06/2020 16:58, philo wrote:
On 6/5/2020 3:50 AM, Andy Burns wrote:
occam wrote:

Andy Burns wrote:

If you leave it a month, it'll go by itself ...
Thanks. By what mechanism will that happen? Is it a default setting
somewhere I have not noticed?
If you were going to delete it manually, the clean way is to use the
disk cleanup wizard, not sure if the automatic method is a task
scheduler calling the same wizard, or if it just nukes the windows.old
folder directly.





Correct.
Must use the wizard and have it look for system files.

It will initially disappear for maybe ten minutes while it searches.


I ran cleanmgr.exe, but the returned options did not include anything
that resembled the 17.9GB that needs to be cleaned.

I'll wait for the necessary 30 days - and then revisit the issue if
windows.old is still there.

The old installation will not just go away on it's own nor is it
possible to manually delete from within Windows


The cleanmgr interface has two levels.

The first level does not list the Windows.old folder.

Click the "System" button, the dialog box disappears
and comes back, and then it works at the second level.
It will then list the Windows.old item.

https://i.postimg.cc/Df47BWFG/cleanmgr.gif


Brilliant, thanks Paul.

On 06/06/2020 10:53, Arlen Holder wrote:
On Sat, 6 Jun 2020 09:47:30 +0100, Andy Burns wrote:

I ran cleanmgr.exe, but the returned options did not include anything
that resembled the 17.9GB that needs to be cleaned.

run it "as admin" it'll offer to clean-up more

I just ran cleanmgr as admin, and it didn't do anything it didn't already
do as a user (who had admin privileges by default).

1. Win+R cmd{control+shift+enter}
2. cleanmgr

Here's a screenshot of that process run moments ago:
https://i.postimg.cc/CMt0T9P3/smode10.jpg


In search box: 'cleanmgr'
Click 'Run as administrator'
https://www.dropbox.com/s/3pebpvmpt7...08.00.png?dl=0

Click 'OK'
https://www.dropbox.com/s/5p723wq5iz...08.20.png?dl=0

(Longish delay)

Seek and tick 'Previous Windows installation(s)'
https://www.dropbox.com/s/g3x2izqv5l...09.11.png?dl=0

On Sat, 6 Jun 2020 13:30:34 +0100, Patrick wrote:

Click 'Run as administrator'

Hi Patrick,

I openly question whether there is any advantage to running cleanmgr.exe as
administrator, when the user already has administrator privileges, given I
didn't see _any_ difference when I tested it today for occam & Paul.

Since I can't run the exact test twice (given the user deleted as much as
the administrator, but I ran the user cleanmgr.exe first), I'll let others
confirm whether running as administrator adds any value whatsoever.

Bear in mind _all_ users will have administrator permissions in my use
model, but in some (extremely highly restricted) use models, I recognize
that the users have very few permissions.

But I'm asking about a tyical single-user setup where there are no real
distinctions between the single user and the administrator.
--
Usenet is a wonderful way to learn more about Windows 10 and how it works.

Paul wrote:

The cleanmgr interface has two levels.

The first level does not list the Windows.old folder.

Click the "System" button, the dialog box disappears
and comes back, and then it works at the second level.
It will then list the Windows.old item.

https://i.postimg.cc/Df47BWFG/cleanmgr.gif

Or run cleanmgr.exe with admin privileges in the first place instead of
loading it in user mode and then clicking the "system" button to reload
it in admin mode.