SWITCH CLEAN - CLEANUP RESEARCH AND REDESIGN PROPOSAL
Research date: November 12, 2026
Status: proposal only. No application or host changes performed.

PRODUCT PURPOSE
Clean should be a comprehensive Windows cleaning and maintenance utility, with
focused reinstall preparation as a second workflow. The current seven top-level
pages expose internal implementation rather than the two main user goals.
Cleaning should say what it achieves: storage recovery, reduced background work,
privacy, or repair. Do not advertise reclaimed bytes as a measured speed gain.

ONE SCAN, ONE REVIEW, ONE EXECUTION
Default screen: Clean Windows. One main button changes from Scan to Clean selected.
Results are grouped, expandable rows rather than separate tool buttons.
Each row shows bytes (or unknown), purpose, consequence, and why it is selected or
held. A details panel provides exact paths and affected apps. Results report actual
bytes freed separately from estimates, plus skipped files and actions needing a restart.

Second workflow: Prepare for reinstall. One guided sequence: identify this computer's
hardware; review focused drivers; create focused backup plus full recovery; optionally
review obsolete devices/packages. Restore is available within this workflow when a
backup is opened. Backup creation never implies approval for live removal.
History, scheduling and specialist repairs belong in secondary menus, not the main
navigation. Internal engines stay modular for SWITCH Toolkit integration.

COVERAGE INVENTORY AND DEFAULTS
Legend: ROUTINE = proposed low-impact default after scan; REVIEW = explicit choice;
REPAIR = use for a relevant symptom; REPORT = identify without deleting automatically.
All defaults require implementation tests; a directory name or age alone is not proof
that its contents are disposable.

1. ROUTINE: Aged user and Windows temporary files in known locations.
   Skip recent, locked, changed, linked, reparse-point and active-installation files.
   Preserve autosaves, recovered documents and unknown app data.
2. REVIEW: Recycle Bin, showing size and age before permanent removal.
   Retention-based scheduled emptying can be separately opted into.
3. ROUTINE: Windows-recognized completed setup/servicing temporary files.
   Check pending servicing and reboots; do not remove active staging content.
4. ROUTINE: Delivery Optimization cache through its supported cleanup interface.
   Cache removal can cause later downloads; don't disable update delivery/security.
5. ROUTINE WHEN RECOMMENDED: Superseded Windows components using component-store
   analysis and StartComponentCleanup. Never manually delete WinSxS; omit ResetBase.
6. REVIEW: Windows.old, upgrade staging/ESD downloads and previous installation files.
   Explain rollback loss; inspect for personal files; don't confuse these with WinRE
   or OEM recovery partitions. Clear only eligible recognized categories.
7. REVIEW: Old Windows Error Reporting archives, memory/minidumps and crash reports.
   Retain recent diagnostic evidence; identify size and age; support export first.
8. REVIEW: Old application logs, known rotated diagnostics and completed updater logs.
   Version-specific rules only. Do not sweep all *.log files or clear Security logs.
9. REVIEW: Browser HTTP caches across installed browsers/profiles, with browsers closed.
   Keep cookies, passwords, sessions, bookmarks, history, permissions, site storage
   and offline content by default. Cache deletion may slow the next page load.
10. REVIEW: Tested caches for installed desktop/Electron apps, launchers, media tools,
    editors and conferencing apps. Identify regenerable cache data specifically.
    Don't treat all AppData, LocalCache, databases or web storage as disposable.
11. REVIEW: Completed application/driver installer downloads and extracted setup files.
    Verify owner and purpose. Retain repair/update caches, installed components,
    firmware payloads needed by active jobs and offline recovery copies.
12. REVIEW/REPAIR: Thumbnail, icon, DirectX and vendor shader caches.
    Warn about rebuild work; never promise routine performance gains. Shader cache
    removal can reintroduce compilation stutter; not a recurring default.
13. REVIEW: Developer package caches (pip, npm, NuGet and similar) when tools exist.
    Use each tool's inspection/cleanup mechanism, not guessed internal paths.
    Retain environments, source trees, lock files, credentials and offline packages.
14. REVIEW: Docker build cache, individually reviewed unused images and containers.
    No blanket system prune and no automatic volume pruning. Stopped containers and
    unattached volumes can contain valuable data. Default to cache-only proposals.
15. REVIEW: WSL/VM disk-space reclamation using product-supported compaction.
    First clean safely inside the guest, then shut down/detach and verify prerequisites.
    Never delete virtual disks, checkpoints or snapshots because they are large.
16. REVIEW: OneDrive online-only conversion for already-synced files.
    Use provider-aware Free up space, not filesystem deletion; retain pinned/offline
    files and flag the resulting need for network access. Not a performance fix.
17. REPORT: Large files, old ISOs/archives, Downloads and oversized folders.
    Age/size do not establish junk. Let users inspect/open and explicitly choose.
18. REPORT: Exact duplicate personal files using content checks, not filenames.
    Exclude OS/application trees; handle hard links and cloud placeholders correctly.
    Never auto-delete backups or duplicates across recovery locations.
19. REPORT/REVIEW: Uninstalled-app remnants, dead shortcuts and orphaned startup entries.
    An absent executable or missing uninstall entry is not sufficient proof: account
    for removable disks, moved installs, launchers and per-user installations.
20. REVIEW: Installed application removal through the registered uninstaller.
    Show storage and startup footprint. Don't strip frameworks, Store infrastructure,
    WebView2, VC runtimes, .NET, shared components or arbitrary bundled applications.
21. REVIEW: Startup apps, background launchers and scheduled third-party tasks.
    Prefer reversible disable over deletion. Show publisher, target and observed
    activity. Preserve security, backup, VPN, hardware control and update services.
22. REPORT: CPU/disk/memory pressure, low free space and startup impact.
    Identify the bottleneck before proposing changes. No fabricated health score.
23. REVIEW: Windows-managed drive optimization appropriate to each volume/media type.
    Let Windows select appropriate operations; don't force old-style SSD defrag or
    disable Windows' own scheduled optimization. Honor power and busy-volume state.
24. REVIEW: Non-present device instances and unused driver packages.
    Keep existing hardware, printer, VPN, shared-service and dependency checks.
    Physical absence alone does not authorize removal; export and verify first.
25. REVIEW: Restore points/shadow-copy storage, older backup retention.
    Treat as recovery management, not junk. Show what recovery capability is lost.
    Never delete all restore points or backup history in ordinary cleaning.
26. REVIEW: Hibernation storage choices and optional OS compression assessment.
    Explain feature/performance tradeoffs. Reduced hiberfile supports Fast Startup,
    not full hibernation. Keep normal power configuration as the default.
27. REPORT/REVIEW: Optional Windows features/languages that the user no longer needs.
    Verify dependencies; use servicing APIs, not manual file deletion.
28. REPAIR: Windows Update cache reset, Microsoft Store cache reset, DNS/network reset,
    print spooler queue clearing, search-index rebuild, DISM/SFC and filesystem checks.
    Separate these from normal cleaning. They can interrupt work, discard queued
    jobs, reset state or consume substantial time; run only for a relevant symptom.
29. OPTIONAL PRIVACY: Browser history, recent-item lists, jump lists and clipboard.
    Keep separate from performance cleanup; explain lost convenience and sync effects.
    Never include saved credentials or authentication tokens in routine cleaning.

METHODS TO EXCLUDE FROM ROUTINE CLEANING
- Generic registry cleaners, registry defrag and automatic 'invalid entry' deletion.
- RAM/standby-cache emptying or periodic cache flushing sold as a speed boost.
- Regular Prefetch deletion or blanket SysMain/Search/service disabling.
- Removing/disabling the page file; preserve system-managed commit/crash-dump support.
- Disabling SAC, Defender, firewall, UAC, memory integrity, updates or mitigations.
- Direct deletion from Windows Installer, WinSxS, DriverStore or ProgramData package
  caches. Vendor-maintenance procedures are distinct, carefully reviewed operations.
- ResetBase as a default; it removes existing update-uninstall capability.
- Broad debloat scripts, indiscriminate scheduled-task deletion or permission resets.
- Free-space wiping/secure erasure as normal maintenance, especially on SSDs.
- Automatically deleting Downloads, game saves, application profiles or user backups.

PERFORMANCE INTERPRETATION
A cleaner can recover needed storage and reduce explicitly chosen startup/background
work. Removing old files is not evidence that CPU, RAM, storage hardware or games will
run faster. Useful caches often improve performance. Avoid repeated cache destruction.
Focus on measured bottlenecks, appropriate disk optimization, unnecessary autostarts
and selective app removal; keep the remaining actions labeled as space recovery.

IMPLEMENTATION REQUIREMENTS
- One unified inventory with deduplication of overlapping cleanup rules and accurate
  allocated-size accounting. Don't double-count hard links, sparse or cloud files.
- Explicit allowlists, known app versions and validated rules; never execute arbitrary
  community cleaner scripts or recursively sweep user-writable paths as administrator.
- Preview snapshots, path containment, reparse/link protections, freshness checks,
  fail-closed dependencies and least-privilege execution.
- Do not force-close applications. Skip in-use content and explain what was skipped.
- Use native APIs and bundled standard-library code where feasible; invoke installed
  optional developer tools only if present. Keep portable/native/SAC requirements.
- Back up reversible settings before disabling autostarts. Don't claim deleted caches,
  emptied Recycle Bin or removed Windows.old can all be undone.
- Scheduled runs cover only individually authorized routine categories; never silently
  add new rules, remove drivers/apps or consume recovery backups after an update.
- Schedule must show when it runs, what it touches and how to remove it. A scheduled
  portable app must remain at its configured path. No always-running cleaner service.
- Test each rule with files/apps in use, pending updates, multiple users, long paths,
  linked folders, cloud files, denied access and interrupted execution.

RESEARCH SOURCES (primary documentation/source projects, not endorsements)
Windows space cleanup:
https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/free-up-drive-space-in-windows
Windows performance and startup/background work:
https://support.microsoft.com/en-au/windows/experience/performance-optimization/tips-to-improve-pc-performance-in-windows
Component servicing and ResetBase consequences:
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/clean-up-the-winsxs-folder?view=windows-11
Windows Installer cache dependencies:
https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/missing-windows-installer-cache
Appropriate storage optimization:
https://learn.microsoft.com/en-us/powershell/module/storage/optimize-volume?view=windowsserver2025-ps
NVIDIA shader-cache purpose and stutter consequences:
https://www.nvidia.com/content/Control-Panel-Help/vLatest/en-us/mergedProjects/3D%20Settings/Manage_3D_Settings_%28reference%29.htm
Browser data categories:
https://support.microsoft.com/en-us/edge/view-and-delete-browser-history-in-microsoft-edge
Community application-cleaning scope and examples:
https://github.com/bleachbit/bleachbit/releases
https://github.com/bleachbit/bleachbit/blob/master/cleaners/windows_explorer.xml
https://github.com/MoscaDotTo/Winapp2/blob/master/README.md
Docker cleanup consequences:
https://docs.docker.com/reference/cli/docker/system/prune/
https://docs.docker.com/engine/manage-resources/pruning
Package caches:
https://pip.pypa.io/en/stable/topics/caching/
https://docs.npmjs.com/cli/v8/commands/npm-cache/
WSL and virtual disks:
https://learn.microsoft.com/en-us/windows/wsl/disk-space
https://learn.microsoft.com/en-us/powershell/module/hyper-v/optimize-vhd?view=windowsserver2025-ps
Cloud-aware space recovery:
https://support.microsoft.com/en-us/onedrive/save-disk-space-with-onedrive-files-on-demand-for-windows
Startup locations and reversible selection:
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns
Page-file function:
https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/how-to-determine-the-appropriate-page-file-size-for-64-bit-versions-of-windows
Hibernation tradeoffs:
https://learn.microsoft.com/en-us/windows/win32/power/system-power-states
Update resets are troubleshooting procedures:
https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/additional-resources-for-windows-update
Search indexing purpose:
https://support.microsoft.com/en-us/windows/experience/performance-optimization/search-indexing-in-windows

The coverage inventory above is a proposed product policy informed by these sources,
not a claim that all listed actions are universally safe or already implemented.
