SWITCH CLEAN 0.10.1 - NATIVE PORTABLE RELEASE START Extract the entire ZIP, then double-click SWITCH Clean.exe. Keep the entire folder together. No installer, separately installed Python, pip, browser or server is required. The SWITCH theme and broom remain; Windows light/dark, high contrast, DPI scaling, resizing and native keyboard navigation are supported. TWO WORKFLOWS Clean Windows: Scan -> review the category list -> Clean selected. Routine suggestions cover aged temporary files, Windows Update, Delivery Optimization and completed setup files when their measured total is worthwhile. Other categories are optional and unchecked. Select a row to inspect paths and consequences. Category and Find filters narrow the list; hidden selections remain selected. More contains rescan, selection helpers, results, reports and Windows storage/startup/installed-app review tools. Prepare for reinstall: Scan -> review focused selection -> choose a destination -> Create both backups. All installed OEM driver packages enter the full recovery archive; only checked packages enter the focused backup. Use a drive that survives the reinstall. Review uncertain dependencies and companion software. An approved machine-bound local selection is retained when still valid. The dropdown also contains optional unused-package review, disconnected-device review, and selective restore. Creating backups never removes drivers or devices. Package removal remains a separate, explicitly confirmed, backed-up operation. IMPLEMENTED CLEANUP Rows depend on installed applications, Windows handlers and access permissions. - User and Windows temporary files aged 7+ days. Recognized documents, archives, autosaves and recovery formats are preserved. Age alone does not prove all temporary data is disposable; inspect the selection. - Windows-owned cleanup of completed setup files, superseded updates, Delivery Optimization cache, previous Windows installs, installation downloads, discarded upgrade files, setup/upgrade logs, recovered fragments, and thumbnails. A new otherwise-unused cleanmgr profile selects only requested handlers, and its flags are removed afterward. Existing cleanup profiles are preserved. Administrator scans query Windows for estimates across fixed local drives. Unknown estimates are labelled Not measured. Estimates are not guaranteed savings. - Old installations/downloads are optional recovery choices. Deletion can lose rollback, reinstall downloads or personal files in Windows.old. Inspect/copy anything needed first. No manual WinSxS, Installer or DriverStore deletion. - DISM component-store analysis, then cleanup only if Windows recommends it. No ResetBase or automatic reboot. Pending restarts and unknown servicing state block cleanup. Active servicing is allowed to finish naturally; waiting is cancellable and bound by preview expiry. - Recycle Bin with Windows confirmation and a post-operation count check. - Windows-managed optimization of fixed volumes, selecting appropriate operations including SSD retrim where supported. Volume refusals are retained in reports. - Recognized HTTP/code caches across Edge, Chrome, Brave, Vivaldi and Firefox profiles. Close browsers, including background processes. Cookies, passwords, sessions, history, bookmarks, site storage and offline content are preserved. - Recognized VS Code, Slack and Discord caches, with the app closed. Settings, extensions, messages, credentials and workspaces are retained. - Archived Windows Error Reporting data, application dumps and Windows minidumps aged 30+ days; pending reports and recent diagnostics retained. VS Code .log files aged 30+ days. Preserve diagnostics needed for open support cases. - Optional DirectX/NVIDIA/AMD shader caches aged 7+ days. Rebuilding can cause stutter and slower launches; this is not a routine performance boost. PROTECTIONS AND RESULTS Only unchanged files from the preview are deleted. Locked, changed, inaccessible, hard-linked, sparse, compressed, cloud/reparse files and junction targets are skipped. Ancestors are locked against rename during deletion. New files are not added to an existing plan. Relevant app processes and servicing state are rechecked. No app is force-closed. File ages and paths are allowlisted; no broad AppData sweep. Temporary cleanup also preserves whole scanner refresh folders referenced by current scanner-amd64/arm64.json pointers, scanner metadata/download archives, NVIDIA bridge, Razer and THX paths. Pointers are re-read at execution while holding SWITCH's existing refresh.lock (safely created if missing during confirmed cleanup). Missing/unsafe pointers, a busy scanner or an unusable lock preserves the entire scanner cache. Unknown scanner-cache layouts are retained. Plans expire after 30 minutes and are single-use. Reports are established before mutation and updated throughout execution. Results distinguish file bytes actually deleted, skips, Windows command outcomes and restart requirements. File sizes are logical bytes, not guaranteed physical storage savings. Windows-managed deletion amounts are not independently measured; a successful process can clean nothing. Reclaimed storage is not a measured CPU, RAM or gaming performance improvement. Clean Windows starts with Scan as administrator. It requests normal Windows UAC using the unchanged publisher-signed Python host, then scans automatically in the new native window. More > Scan without administrator keeps a limited read-only preview available. System cleanup still requires administrator rights. SAC is separate from UAC; neither security mechanism is suppressed. DRIVERS AND RESTORE Non-present means Windows reports an instance absent, not idle or disabled. All classes can be reviewed; presence is rechecked. Package cleanup separately holds present/internal hardware, printer classes including Print to PDF, VPN/virtual adapters, shared services/filters/components, incoming dependencies, unknown associations and incomplete inventories. Candidates are rechecked twice; export and hash verification precede deletion. No /force, device-uninstall flag or reboot. Razer/THX and other shared filter/component packages remain subject to these guards. Restore loads a SWITCH Clean manifest, verifies its files and lets you choose packages. Reverification and a private copy precede Windows import. Windows driver ranking applies; no forced downgrade. Hashes detect changed files, not malicious replacement of both a manifest and its files. Keep archives in trusted storage. REVIEW TOOLS / LIMITS More opens Windows Storage, Startup Apps and Installed Apps for explicit review. It does not automatically remove personal files, apps or startup entries. This release does not implement custom scheduling, duplicate-file deletion, arbitrary app-remnant deletion, Docker/WSL pruning, VM compaction, OneDrive eviction, privacy-history wiping, registry cleaning, RAM boosting or blanket service tweaks. Existing Windows scheduled maintenance stays unchanged. The research document separately identifies future coverage; it is not an implemented-feature checklist. PORTABILITY AND SMART APP CONTROL SWITCH Clean.exe is a byte-for-byte copy of the bundled Python Software Foundation signed pythonw.exe. The executable's publisher signature is unchanged. We do not sign our own executable, install dependencies, disable SAC, add exclusions, remove download markings or ask for Run anyway. Python and runtime libraries are bundled. The broom is applied to the window and shortcut without modifying the signed EXE. See VM-VALIDATION.txt for this build's observed results. Microsoft reputation and policy can change; one enforced VM cannot guarantee every future runtime, policy or downloaded distribution will run. Normal administrator UAC can still appear. TOOLKIT INTEGRATION The native UI calls core.Engine.scan(workflow='cleanup'|'prepare'|'all') and execute. The CLI scan and doctor commands are read-only. See INTEGRATION.txt. The machine- local focused-selection.local.json stays private and is excluded from the ZIP. Reports/archives remain until you remove them. Keep the complete portable folder. 0.8.0 ADMINISTRATOR CLEANUP WORKFLOW Windows-owned estimates use read-only IEmptyVolumeCache GetSpaceUsed calls in separate bundled Python processes. No purge or automatic-cleanup flag is used while scanning. Windows component-store analysis uses AnalyzeComponentStore only. Windows Update Cleanup and component cleanup overlap; the UI shows a single Windows Update choice when that handler is available. The component analysis is included in its details instead of offering two equivalent cleanup selections. Selected Windows handlers run together in a new, otherwise-unused documented cleanmgr profile (1..9999). The exact selection is checked before starting and the temporary flags are removed afterward. No driver-package handler is allowed. After you confirm cleanup, busy Windows servicing is allowed to finish naturally. Cancel pending work stops a wait or later actions. It does not terminate active Windows cleanup, DISM or optimization; the current operation finishes and is verified. No services are stopped and no pending restart is bypassed. Previews expire after 30 minutes; an expired wait requires a new scan and review. Results show each selected Windows category's before and remaining estimates. A successful command may leave a nonzero estimate. The app reports it, without claiming it was deleted, repeatedly cleaning, forcing deletion or using ResetBase. File bytes deleted are separate from Windows estimates. Driver INF names/hashes, SAC state and restart indicators are checked at the cleanup boundaries. Drive free space is recorded separately because other applications can change it concurrently. Verification failures are disclosed; unavailable estimates are never reported as zero. 0.9.0 CLEANUP RECOMMENDATIONS The existing scan screen now explains Suggested, Small amount, Keep, Review needed, and Leave for Windows. The summary explicitly says when nothing is worth cleaning in routine categories. No extra buttons or automatic cleanup were added. Routine suggestions require at least 100 MiB combined across eligible routine categories, with each included category at least 1 MiB. These are SWITCH Clean convenience thresholds, not a Windows requirement or a performance claim. Small amounts remain available for manual review. Browsers (including Brave), app caches, shader caches, recovery files and diagnostics are never routinely preselected. Unknown sizes, scan warnings and blocked checks are not treated as an all-clear. After successful Windows Update cleanup, verified remaining per-volume estimates are saved in cleanup-history.local.json beside the app. A fresh scan that matches that remainder recommends leaving it for Windows maintenance. It does not offer the unchanged estimate as suggested savings. A changed estimate, Windows build, installation, volume identity/set, or history older than 30 days requires fresh assessment. Corrupt history asks for review; it never authorizes cleanup. History affects recommendations only; manual selections still use every existing confirmation, servicing, backup and driver protection. No repeated cleanup starts. Keep cleanup-history.local.json when moving your local app to a newer release. It is excluded from the distributable ZIP, as is the focused driver selection. History contains a hashed system/build/volume scope, estimates and timestamps; it does not contain raw machine IDs, browsing data or a driver inventory. 0.9.1 MISSING SCANNER LOCK A missing scanner refresh.lock no longer prevents every obsolete scanner-cache cleanup. Recovery occurs only during confirmed cleanup of selected scanner staging files, after existing scanner pointers and ancestor directories pass validation. Scans, unrelated temp cleanup and empty selections never create the lock. Clean opens existing locks without changing their contents. Only a genuinely missing file permits CREATE_NEW; a concurrent creator's file is reopened unchanged. The handle is validated against links/unsafe types, byte zero is locked, and a new file receives the Toolkit-compatible byte '0'. The same handle and ancestor locks remain held while pointers are re-read and approved files are processed. Current scanner folders, metadata and downloads remain protected. Lock or initialization failure preserves scanner-cache files; other approved temp files may still clean. Results disclose lock recovery or preservation. No scanner refresh/download starts, no app or service is stopped, and no cleanup is triggered just by opening the app. 0.10.0 SAVED SCANS AND LIST ORDER Completed Clean Windows scans in the native app are automatically saved to scans/ beside the portable app. More > Open saved scan... reopens a chosen JSON file. Older 0.9.x cleanup CLI exports and the saved administrator scan reports can also be opened. Driver inventories and cleanup execution reports are not scan files. Reopened results show their original date, version, scope and recommendations. Every selection is cleared, the view is read-only, and the primary action becomes Scan again. No saved file candidates or executable plan are restored. A successful fresh scan and a new review/confirmation are required before cleanup. Availability and estimates in a saved scan describe its original time, not current conditions. Selectable items appear before unavailable or empty rows, retaining their order within each group. Labels still distinguish Suggested, Optional, Keep and Leave for Windows: being selectable does not mean an item should be cleaned. The same ordering is used for driver-package review without changing any protection. Saved scans keep the original availability order but cannot be selected. No new main-screen buttons were added. If the portable folder is read-only, scan results remain visible and the app reports that saving failed. Scans can contain local paths; keep them private. The scans/ folder, reports and local preferences are excluded from the distributable ZIP. Keep your local scans when moving releases. 0.10.1 VISIBLE ADMINISTRATOR SCANS Scan as administrator and More > Run as administrator now request a normal visible window. The previous launch used SW_HIDE, which overrode the new app window's first ShowWindow call. The signed windowed Python runtime remains console-free. Normal Windows UAC and Smart App Control still apply. No security setting changes. Cleanup rules, saved scan behavior, selectable-first ordering and protections are unchanged. Opening or elevating the app never authorizes cleanup. 0.10.1 VALIDATION The administrator window was observed during analysis and after completion in both the disposable Windows VM and the host scan, with Smart App Control Enforced. The host scan ended with 0 selected and no cleanup. See VM-VALIDATION.txt and HOST-VALIDATION.txt; machine-readable evidence is in validation/.