Consider the tradeoff first
Compression reduces storage needs at the cost of decompression work when the data is read. Whether that tradeoff helps depends on processor and storage performance. A PC with little storage is a different case from one that has plenty of free space but a runaway log or game download.
If Windows reports Compact OS already active, enabling it again is not a new cleanup opportunity. If status or suitability is unavailable, use the dialog's Microsoft documentation link rather than treating the missing result as a recommendation.
Understand the three commands
compact.exe /CompactOS:query checks the current state.
compact.exe /CompactOS:always enables system-binary compression.
compact.exe /CompactOS:never disables it and expands the binaries.
The dialog's Copy command buttons copy the enable or disable command. Open elevated command window... requests administrator approval and opens a window that queries the current state. You still decide whether to run a change command.
Disabling compression requires enough free space to expand the Windows binaries. Check Microsoft's compact command reference before changing the setting.
Verify the outcome
Wait for the Windows command to complete, then refresh Compact OS status and run a fresh disk scan. Compare actual free space rather than assuming a particular savings figure. The operation does not remove installer caches, application data, restore points, or personal files.
If free space keeps falling afterward, use saved scans or recent file activity to find the source of growth. Compact OS changes how system binaries are stored; it does not stop another program from generating files.