5 ms·

tbf... almost all of WinSXS is hardlinks, there is very little actual duplication. It's just that explorer doesn't understand that and reports it as duplication

by leeter 10y ago

tbf... almost all of WinSXS is hardlinks, there is very little actual duplication. It's just that explorer doesn't understand that and reports it as duplication.

rasz_pl 10y ago
easily disproved: C:\WINDOWS\system32>dism /Online /Cleanup-Image /AnalyzeComponentStore Windows Explorer Reported Size of Component Store : 8.18 GB Actual Size of Component Store : 7.78 GB
- acqq 10y ago
  The next line of the output from the command you specified but which you didn't quote and that gives almost 5 GB on the machine in the example it is named "Shared with Windows" https://technet.microsoft.com/en-us/library/dn251566.aspx https://technet.microsoft.com/en-us/library/dn251566.aspx "This value provides the size of files that are hard linked so that they appear both in the component store and in other locations (for the normal operation of Windows). This is included in the actual size, but shouldn’t be considered part of the component store overhead."
  - rasz_pl 10y ago
    1 you specifically said "WinSXS is hardlinks", this is not true 2 still leaves up to 5GB of redundant garbage in WinSXS, things like multiple versions of random DLLs nobody ever uses, 360MB for ~11 versions of 'getting started' package consisting of same movie files, color calibration data for obscure scanners on bare minimal install etc Turning drive compression omits this directory while happily compressing files in /system.
    - acqq 10y ago
      > you specifically said No, you communicated before with somebody else. > still leaves up to 5GB of redundant garbage No, if you read that example, there is less than 1 GB which is stale (the diff between the first and the third number): >> Windows Explorer Reported Size of Component Store : 4.98 GB >> Actual Size of Component Store : 4.88 GB >> Shared with Windows : 4.38 GB As I've said, you intentionally didn't quote your machine's third line but I'm sure it's not a 5 GB difference. Moreover, that difference can be purged if necessary. Which you can also do on your machine with just a single command, per link on the same page: https://technet.microsoft.com/en-us/library/dn251565.aspx https://technet.microsoft.com/en-us/library/dn251565.aspx There is a trade-off, the probable case why nobody does it unless really necessary: "All existing service packs and updates cannot be uninstalled after this command is completed"

by leeter 10y ago

tbf... almost all of WinSXS is hardlinks, there is very little actual duplication. It's just that explorer doesn't understand that and reports it as duplication.

rasz_pl 10y ago

easily disproved: C:\WINDOWS\system32>dism /Online /Cleanup-Image /AnalyzeComponentStore Windows Explorer Reported Size of Component Store : 8.18 GB Actual Size of Component Store : 7.78 GB

acqq 10y ago
The next line of the output from the command you specified but which you didn't quote and that gives almost 5 GB on the machine in the example it is named "Shared with Windows" https://technet.microsoft.com/en-us/library/dn251566.aspx https://technet.microsoft.com/en-us/library/dn251566.aspx "This value provides the size of files that are hard linked so that they appear both in the component store and in other locations (for the normal operation of Windows). This is included in the actual size, but shouldn’t be considered part of the component store overhead."
- rasz_pl 10y ago
  1 you specifically said "WinSXS is hardlinks", this is not true 2 still leaves up to 5GB of redundant garbage in WinSXS, things like multiple versions of random DLLs nobody ever uses, 360MB for ~11 versions of 'getting started' package consisting of same movie files, color calibration data for obscure scanners on bare minimal install etc Turning drive compression omits this directory while happily compressing files in /system.
  - acqq 10y ago
    > you specifically said No, you communicated before with somebody else. > still leaves up to 5GB of redundant garbage No, if you read that example, there is less than 1 GB which is stale (the diff between the first and the third number): >> Windows Explorer Reported Size of Component Store : 4.98 GB >> Actual Size of Component Store : 4.88 GB >> Shared with Windows : 4.38 GB As I've said, you intentionally didn't quote your machine's third line but I'm sure it's not a 5 GB difference. Moreover, that difference can be purged if necessary. Which you can also do on your machine with just a single command, per link on the same page: https://technet.microsoft.com/en-us/library/dn251565.aspx https://technet.microsoft.com/en-us/library/dn251565.aspx There is a trade-off, the probable case why nobody does it unless really necessary: "All existing service packs and updates cannot be uninstalled after this command is completed"