No, Win10 doesn't currently combine gigabyte and gibibyte units. It uses standard byte measurements.
No, Win10 doesn't currently combine gigabyte and gibibyte units. It uses standard byte measurements.
It seems this could be an outdated topic, and I might have overlooked a conversation about it. I noticed that Windows Explorer displays varying GB figures compared to the properties page for the same file. For instance, a file might show 35.6GB in Explorer while its property page lists 33.9GB. This inconsistency is quite confusing and seems unusual.
The report includes both the file’s actual dimensions and its storage footprint. I believe the file manager displays the disk size. Because of how disks are structured, a file often needs more space than its physical measure. Would you like me to provide a screenshot of this file?
Sure, I can clarify that. Would you like me to provide a visual example or describe what the comparison looks like?
Windows typically displays disk capacity in GiB, though GB is commonly used as an abbreviation. When you insert a 1TB drive, it might appear as 931GB, which equals 931GiB or 1TB. On the properties page, this could stem from compression settings or the disk's sector size.
Not quite. Here's example + screenshot. It shows 12,835,615kB in the explorer which converts to 12,8 Gigabyte if google is to be believed. However in properties it shows, well...something very different which is 13,143,669,496 Bytes or 12.2 GB which is again slightly different from file size on disk. I'm confused.
From what I recall, it was always this way, even with Windows 7. No updates.
Windows displays values in kB while the actual capacity is in KiB. Google applies a standard conversion of 1000, which aligns with SI measurements, whereas Windows uses traditional PC units where the factor is 1024. This ensures the displayed figures match real-world storage sizes.