How to correct the compact view that isn't compact and reverse the increased row padding in File Explorer

Hello Michelle Neil,

You are accurately identifying a byproduct of the architectural shift in the Windows 11 shell. Unlike Windows 10, which utilized the legacy DirectUI framework for File Explorer, Windows 11 implements the Windows App SDK (WinUI) with XAML-based command bars and views. This modern framework enforces a larger default "touch-friendly" hit target and padding structure. While the "Compact view" option toggles a state to reduce this padding, the XAML grid definitions for the "Compact" state in Windows 11 still carry higher pixel density values than the native Win32 controls used in Windows 10. Consequently, even with Compact view correctly enabled, the row height will be mathematically taller than what you experienced in the previous OS.

To ensure you are achieving the maximum density possible within these constraints, we must verify the configuration is writing to the registry correctly, as the UI toggle can sometimes fail to persist across sessions or get overridden by tablet posture states. Open the Registry Editor (regedit.exe) and navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced. Locate the DWORD value named UseCompactMode. Ensure this Value data is set to 1. If this key is missing or set to 0, the system is defaulting to the standard "comfortable" padding. Furthermore, you should check HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell for a value named TabletMode and ensure it is set to 0, as Windows 11 can sometimes erroneously flag a desktop as a tablet device, forcing the expanded UI regardless of your Explorer settings.

If UseCompactMode is already set to 1 and the density remains insufficient for your workflow, there is no native, supported "permanent fix" or hidden registry key to revert the rendering engine to the exact Windows 10 dimensions. The spacing is hardcoded into the Explorer frame's resource definitions (specifically the UI.xaml resources within explorerframe.dll and related package dependencies), which cannot be altered without replacing system files or injecting code, actions that violate your limited access environment and Microsoft's security integrity policies. You are currently viewing the limit of the operating system's native information density.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Hello Michelle Neil,

I'm checking in to see if the explanation regarding the architectural shift to XAML-based WinUI in the Windows 11 shell clarified the behavior you are seeing. As mentioned, the increased padding is intrinsic to the new framework's resource definitions and distinct from the legacy DirectUI used in Windows 10, meaning row heights will mathematically remain larger even in "Compact" mode. Verifying that the UseCompactMode DWORD is set to 1 in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced confirms you have enabled the maximum information density currently supported by the operating system without modifying system files.

If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP