That's what DU figures out, but it is just a very small portion of all disk usage for Windows folder.
By the way, windows disk cleanup doesn't work, it only find very very small files in kb range.
(base) PS C:\Apps\DU> du -nobanner -c -l 1 C:\Windows | ConvertFrom-Csv | select Path,@{Name="DirectorySize";expression={$_.DirectorySize / 1GB }} | Where-Object { $_.DirectorySize -gt 1 } | Sort-Object { $_.DirectorySize } -descending
Path DirectorySize
---- -------------
c:\windows 16.5982748987153
c:\windows\System32 6.4668475612998
c:\windows\Installer 2.13524127006531
c:\windows\WinSxS 2.02410347945988
c:\windows\assembly 1.37638363521546
c:\windows\servicing 1.24389411974698
c:\windows\SysWOW64 1.01788134872913
By the way, windows disk cleanup doesn't work, it only find very very small files in kb range.
(base) PS C:\Apps\DU> du -nobanner -c -l 1 C:\Windows | ConvertFrom-Csv | select Path,@{Name="DirectorySize";expression={$_.DirectorySize / 1GB }} | Where-Object { $_.DirectorySize -gt 1 } | Sort-Object { $_.DirectorySize } -descending
Path DirectorySize
---- -------------
c:\windows 16.5982748987153
c:\windows\System32 6.4668475612998
c:\windows\Installer 2.13524127006531
c:\windows\WinSxS 2.02410347945988
c:\windows\assembly 1.37638363521546
c:\windows\servicing 1.24389411974698
c:\windows\SysWOW64 1.01788134872913