
Most large files should be in profile hierarchy though.
Also quick to uninstall large, unused software packages.Īnd check root of C:\ for virtuals and similar uses.
Just the 5-minute emergency procedure I use myself (trivial options).Īnd obviously empty the recycle bin :-).
iTunes?, ISOs?, Installers (in Downloads). Zap Re-downloadable Files? (many huge files can easily be re-acquired). In short: Move only files you know are safe to move!. Avoid source code folders and virtual disks (move whole folder only)!. Careful with: Outlook PST files! Database files!. Typically ISOs, Virtuals, Movie files, etc. Mongers Sweep: In Windows Explorer, select "Users folder" (C:\Users), press F3 and select "Size: Gigantic" (or very large). Move the content of your Downloads and Largest Media folders on there. Storage: Insert a USB drive (low-profile if you want it connected permanently) or SD-card. Microsoft's piece on space reclamation: Free up drive space in Windows 10Įxpress: Urgent 5-Minute Space Reclamation Original and messy answer: Trifles & Tricks: Obvious ways to free Below are some suggested procedures you can use to regainīelow are the essential / most effective options summarized from this The real issue is disc space - SSD drives are still too small for comfort. See bottom section: "Administrative Installation". Must be done per package, and you need a stable, always on network share (or a stable local path / drive). Administrative installs can drastically reduce the size of the local cache folder. Essentially a file extraction of installation source that you put on a network share. Reduce the size of the %SystemRoot%\Installer folder for future deployments. Using administrative installations (please skim linked answer) is a general purpose measure to Same goes for WinSxS, Driver Store & GAC.
An unserviceable system almost always results. The directory %SystemRoot%\Installer and its contents must never be meddled with.