re Settings -> System -> Storage
It seems as though Windows 10 can add some, but not necessarily all new or detected partitions to an aggregate capacity under the label This PC (C: ) Even if the partitions are empty NTFS or RAW (inc. Linux Swap?) also include them as usage: 'System & reserved.' I haven't able to discern a pattern of how Windows 10 determines if a new or empty formatted partition will be added to the aggregate Storage summary. At best it's confusing, and appears to be broken.
Further: deleting some partitions, or shutting down, unplugging disks and rebooting does not necessarily alter the reported aggregate that is shown for This PC (C: ) i.e. You would expect removing all drives and partitions to restore This PC (C: ) status to show only the Windows partition capacity - it doesn't and it continues to show 100s extra GB that are no longer present on the PC.
e.g. on my previous install I was seeing an impossible 239GB 'system & reserved' with 323GB 'capacity.'
- Windows 10 & 7 partitions each = 100GB
- Windows disk total capacity = 223GB
- Other disks, mix of NTFS, EXT4 (Mint 17, /home) Swap (Linux)
N.B. I've tried this a couple of ways with fresh installs on clean disks and see the same result. It doesn't make a difference if Windows 10 or Windows 7 is installed first. I have made the partition order: recovery|efi|msr|windows|other
Other things that make no difference:
At the moment I am unsure if this is merely a 'cosmetic' issue or something that might cause more serious functionality problems later e.g. not being able to install since Windows incorrectly thinks a drive or partitions are used or reserved.
- Removing or assigning new disk letters
- For both Windows 10 and Windows 7:
- Hibernation is disabled (from admin cmd terminal)
- Page-file management to be on C: only (other disks set to none)
I'm guessing this is multi-boot related, but does this strange Storage summary behaviour occur on anyone's system with Windows 10 only? Is anyone aware of this issue in dual/multi-boot PCs? is there a known bug or fix?