Windows installations are notorious for accumulating junk. Over time, update remnants, restore points, indexing databases, and preinstalled bloatware can consume tens of gigabytes and slow down even modern machines. On compact laptops with just 128 GB of storage, every wasted byte is a crisis. But reclaiming that space doesn't require a reinstall—if you approach the cleanup with a methodical, risk-aware strategy.

The PCWorld "12 tweaks" guide, expanded here with verification and community insights, lays out a practical playbook: start with safe, built-in tools like Disk Cleanup and Storage Sense, then move to system compression and index tuning, and only then consider extreme measures like custom ISOs or debloat scripts. This layered method ensures you get maximum benefit without sacrificing Windows' ability to update or run your apps reliably. In this article, we'll walk through each tweak, verify key technical details, and flag the pitfalls that can turn a speed boost into a support nightmare.

Quick Wins: Built-In Cleanup and Startup Hygiene

Before reaching for third-party tools, use what Windows already offers. Disk Cleanup (cleanmgr) is the obvious first step. Run it as administrator, select "Clean up system files," and enable every option—especially "Update cleanup"—to strip out gigabytes of temporary installers and old Windows versions. Just avoid the Downloads folder unless you’ve confirmed its contents. Storage Sense, found under Settings > System > Storage, can be configured to auto-delete temporary files and empty the Recycle Bin on a schedule, preventing future pile-ups.

Next, tackle startup apps and bloatware. Open Task Manager > Startup and disable any nonessential programs that launch with Windows. Then head to Settings > Apps and uninstall anything you don’t need—OEM trialware, bundled games, redundant utilities. These actions are low-risk, instantly reversible, and often free up more than just disk space by reducing CPU and memory overhead.

Indexing and Reserved Storage: Taming Hidden Space Hogs

Two less visible culprits can balloon silently: the Windows Search index and reserved storage for updates.

Windows Search Index (Windows.edb)

The Windows.edb file (or Windows.db in Windows 11) lives under %ProgramData%\Microsoft\Search\Data\Applications\Windows. Depending on how many files you index, it can swell to multiple gigabytes. Microsoft warns that indexing large PST files or more than 400,000 items can bloat the database. If you rely on a faster, leaner alternative like Everything for file search, you can safely disable the Windows Search service and delete the file, instantly reclaiming that space. If you still need indexed search, open Indexing Options, remove unnecessary folders, and rebuild the index. For advanced users, an offline defragmentation with esentutl.exe /d can compact the database without losing functionality.

Reserved Storage

Windows reserves up to 7 GB for future feature updates, but on tight drives that’s precious real estate. You can reclaim it by running PowerShell as administrator: Set-WindowsReservedStorageState -State Disabled (or DISM /Online /Set-ReservedStorageState /State:Disabled). The trade-off: future updates will demand enough free space upfront, so you’ll need to keep a careful eye on capacity. Wait until all pending updates are installed and the system is idle before running the command; an error means maintenance tasks are in progress. This is a trade-off worth making only if you’re struggling for space and can manage update logistics manually.

System Compression: CompactOS and Selective Folder Squeeze

When native cleanup isn’t enough, transparent file compression can squeeze extra gigabytes from the OS and your program folders.

CompactOS

Windows’ built-in CompactOS feature compresses system binaries without breaking anything. Run compact /compactOS:always in an elevated command prompt to enable it. Typical savings range from 2 to 6 GB. The performance hit depends on your hardware: modern SSDs and fast CPUs barely notice, but older spinning disks might suffer from added decompression overhead. The operation is fully reversible with compact /compactOS:never, so testing is painless. Always run compact /compactOS:query first to see the current state.

CompactGUI and Compactor

For more granular control, third-party tools like CompactGUI and Compactor wrap Windows’ compression APIs with friendly interfaces. CompactGUI uses the familiar compact.exe backend and integrates with the Explorer context menu. Compactor, written in Rust, goes further: it analyzes files before compression, skipping incompressible ones (like SQLite databases or VM images), and keeps a hash database to speed up future passes. Both support algorithms from fast XPRESS4K to high-ratio LZX, with LZX often achieving 40–60% size reduction on game folders and developer SDKs—Compactor’s GitHub documents squeezing Visual Studio from 9.6 GB to 4.7 GB.

But compression isn’t free. DirectStorage games under Windows 11 should be excluded, as decompression negates the GPU pipeline advantage. Large databases and active VM files can also suffer performance penalties. Always exclude critical paths, test your most-used apps after compression, and keep a log so you can revert any problematic folder.

Rebuild and Debloat: From Custom ISOs to Ultra-Light Builds

If you’re still starved for space or determined to eliminate every unnecessary process, the nuclear options await—but they come with serious caveats.

Tiny11 and Tiny11 Builder

Tiny11 is a community-crafted Windows 11 image stripped of TPM requirements, online accounts, and most bloatware. The latest builds, based on Windows 11 24H2, claim a footprint as low as 3.5 GB with LZX compression. The safest route is not to download prebuilt ISOs from untrusted sources, but to run the Tiny11 Builder PowerShell script on your own official Windows ISO. The script uses DISM to remove components, keeping the process as transparent and auditable as possible. An even more aggressive “Core” profile removes Windows Update, Defender, and recovery, creating an unpatchable system suited only for isolated test VMs. Verify every executable in any script before running it, and never rely on a gutted image as your daily driver without a full backup.

WinUtil and Automated Minimal Images

Chris Titus’s WinUtil automates the creation of trimmed, preconfigured Windows images that bypass TPM checks, online account setup, and many installation tasks. It’s popular for lab machines and VMs, but the resulting installations might not support normal servicing. Use it only if you understand the trade-offs and are willing to reimage if updates break.

For a safer custom ISO, NTLite loads an official Windows image and lets you remove languages, optional features, and drivers while integrating updates. This yields a slim image that remains fully serviceable—provided you don’t over-remove. Microsoft’s servicing stack depends on certain components; blind deletion of WinSxS or System32 will break future updates. NTLite’s documentation offers templates for cleaning telemetry and unwanted apps without compromising the upgrade path. For low-risk experimentation, install Windows into a virtual hard disk (VHD) using WinNTSetup. You can boot into the VHD like a normal system, test tweaks, and simply discard the file if something goes wrong.

Aggressive Debloat Scripts and Core Builds

Tools like Win11Debloat, Win Reduce, and the extreme Tiny11 Core mode go further, removing system apps, recovery tools, and even defending services. Win Reduce can shrink WinSxS and System32 folders by brute force, but the result is an un-updateable husk. These are strictly for test environments or advanced users with a willingness to reinstall. Always create a full disk image beforehand, and prefer scripts that create a preflight restore point and clearly document what they remove.

A Staged Checklist for Every User

To bring order to the chaos, here’s a priority-ordered checklist that balances risk and reward.

  1. Back up – Create a system image or at least a restore point before any major change.
  2. Run Disk Cleanup – Select “Clean up system files” and tick all boxes except Downloads.
  3. Enable Storage Sense – Set it to clean automatically weekly.
  4. Audit startup and apps – Disable unnecessary startup items via Task Manager; uninstall bloatware via Settings.
  5. Review the Search index – Modify indexed locations or disable the service if you use Everything. Compact the database if it’s bloated.
  6. Assess CompactOS – Run compact /compactOS:query; if disabled, enable with compact /compactOS:always and benchmark your workload.
  7. Selectively compress large folders – Use Compactor or CompactGUI on game directories and heavy SDKs, excluding DirectStorage games and VMs.
  8. If radical downsizing is needed – Build a custom ISO with NTLite or Tiny11 Builder, always using DISM-based scripts and testing in a VM first.
  9. Avoid Core builds and WinSxS hacking – Unless you’re on a disposable test machine.

What Can Go Wrong: Pitfalls and Unverified Claims

  • Update failures – Removing components that Windows Update expects can block both cumulative and feature updates. Keep at least 20–30 GB free before major updates if you’ve disabled reserved storage.
  • Performance regressions – LZX compression on a weak CPU or spinning disk can slow app launches and file access. Always measure, don’t assume.
  • Compatibility quirks – Compressed folders can confuse antivirus, backup tools, and certain games. Exclude databases and DirectStorage paths.
  • Trust issues – Community ISOs have historically included opaque binaries. Stick to builder scripts that leverage official Microsoft tools and avoid unsigned executables.
  • Illustrative numbers – Claims like “Tiny11 uses only 3.5 GB” are best-case samples; actual sizes vary with drivers, language packs, and build version. Validate in your own test VM.

The Verdict: A Tiered Approach Wins

PCWorld’s 12-step checklist is not a single prescription but a menu of escalating aggression. The overwhelming consensus from community testing and official documentation is that you will get the most stable, performant results by working through the first two tiers—native cleanup and compression—before touching anything that alters the servicing model. Casual users should stop after Storage Sense and CompactOS; power users with backup discipline can venture into custom ISOs; only disposable testbeds should ever see a Tiny11 Core or a manually hacked System32.

The real win isn’t just a few extra gigabytes. It’s a system that boots faster, idles with lower CPU usage, and doesn’t surprise you with update errors. Follow the stages, keep backups, and your lean Windows machine will stay fast without turning into a maintenance nightmare.