Microsoft is making a small but welcome File Explorer change that should save Windows 11 users from doing mental math every time they review large files. In the Details view, the Size column is being updated so files can appear in the most appropriate unit, such as KB, MB, or GB, instead of showing everything only as kilobytes.

That sounds minor, but it addresses a long-running usability issue. A file that is several gigabytes in size is technically readable when shown as a large KB value, but it is not quickly understandable. For anyone cleaning a downloads folder, reviewing a user profile, comparing installer packages, or trying to recover disk space on a nearly full device, the new display format makes File Explorer more practical at a glance.

What is changing in File Explorer

Until now, Windows 11 File Explorer has generally shown file sizes in KB in the Details view. That behavior is precise enough for small files, but it becomes awkward for modern workloads where ISO images, virtual machine disks, game files, exported videos, and offline installers can easily run into many megabytes or gigabytes.

With the new behavior, File Explorer can choose the unit that best fits the file. Small files can still appear in KB, while larger items can be shown in MB or GB. The goal is not to remove kilobytes from Windows, but to stop forcing users to interpret very large KB numbers when a more readable unit is available.

For IT teams and power users, this is a useful quality-of-life improvement. It makes routine storage cleanup faster, reduces the chance of misreading a file size, and brings the Details view closer to how people already talk about storage capacity.

Why this matters for IT users

Storage troubleshooting is one of the most common support tasks on Windows PCs. A user may report that Windows Update cannot complete, Outlook is running slowly, OneDrive sync is stuck, or a line-of-business application has stopped saving files. Very often, the next step is to determine what is consuming disk space.

The practical benefit is faster triage when storage pressure is building. Instead of scanning a directory full of large KB values, a technician can sort by Size and immediately see whether the biggest items are 700 MB installers, 4 GB archives, or 40 GB virtual disks. That makes the first pass through a problem folder simpler and less error-prone.

The change is also helpful for less technical users. Many people understand MB and GB because those units appear in phone storage settings, cloud storage plans, and USB drive packaging. Fewer people are comfortable converting a multi-million-kilobyte value into something meaningful. Displaying sizes in familiar units makes File Explorer feel less dated and more approachable.

Availability and rollout expectations

Windows Latest reports that Microsoft referenced the change in release notes for Windows 11 KB5101684. As with many Windows 11 interface changes, availability may be gradual. Installing the relevant update does not necessarily mean every PC will show the new behavior immediately, because Microsoft frequently stages features through controlled rollout mechanisms.

That staged approach can be frustrating when you are testing a new capability across multiple devices. One machine may show the updated Size column while another, apparently similar system, still uses the older KB-only presentation. In managed environments, administrators should expect some variation unless Microsoft documents a specific policy, build requirement, or enablement package behavior.

If you support a fleet of Windows 11 PCs, the safest approach is to treat this as a usability enhancement rather than a change that requires urgent deployment action. It does not appear to alter file properties, disk usage calculations, or the actual storage consumed by files. It changes how File Explorer presents the value in one view.

Should you force-enable it?

Windows Latest notes that advanced users can enable the feature early with ViveTool using feature ID 61014711, and can disable it again with the same tool if needed. ViveTool is commonly used by Windows enthusiasts to turn on features that are present in the operating system but not yet enabled for a specific device.

For personal test machines, that may be acceptable if you understand the risks. For production PCs, especially business endpoints, it is better to wait for Microsoft’s normal rollout unless there is a specific testing need. Feature flags can exist for a reason: Microsoft may still be validating compatibility, telemetry, accessibility behavior, or localization details.

If you do test the change manually, use a non-critical machine first and document exactly what was enabled. Administrators should avoid applying unsupported feature toggles broadly through scripts unless they have a rollback plan and a clear reason to do so.

What to check after it appears

Once the updated Size column arrives on your PC, open File Explorer, switch a folder to Details view, and sort by Size. Test with a mix of small documents, photos, installers, compressed archives, and large media files. You should see that Windows presents sizes in units that are easier to scan quickly.

This is also a good time to review how your users are taught to clean up storage. Guidance that previously referenced large KB numbers may need to be updated. Help desk documentation can simply tell users to sort by Size and look for large MB or GB files, which is clearer and easier to follow.

Microsoft’s change will not solve storage management by itself, but it removes unnecessary friction from a task nearly every Windows user performs at some point. File Explorer remains one of the most important daily tools in Windows, and small improvements in readability can have an outsized impact.

Source: Windows Latest