Repository navigation
Registry Cleaner
Clean Registry is WMT's deep registry scanner. It checks selected areas of the registry for references to missing files, stale COM registrations, invalid paths, orphaned uninstall entries, and similar problems. It is a review-first tool: findings are shown with risk and confidence, and protected entries are never changed automatically.

Select Registry Scan Targets. Checked categories are remembered and reused for later scans.
Registry cleaning is optional maintenance, not a required repair. Windows does not need a registry cleaner to run well, and deleting the wrong key can break an application, a shell extension, or a Windows component.
Before scanning:
- Create a restore point. WMT also attempts one before applying fixes, but an existing point is more reliable.
- Close applications and save your work.
- Read the Risk, Confidence, and Why Flagged columns before selecting anything.
- Prefer fixing a small number of high-confidence items over selecting everything.
- Keep the generated
.regbackup until you are sure the system is healthy.
- Go to Cleanup > Clean Registry.
- Check the categories you want to scan. Your selection is saved in
settings.jsonunderRegistryScan. - Click Start Deep Scan.
- Wait for the scan to finish. A progress window shows the current category and offers Cancel.
- Review the findings in the Deep Registry Cleaner window.
- Select only the items you understand, then click Fix Selected Issues... and confirm.
The scan is read-only. Nothing changes until you apply fixes.
The target picker offers 53 categories:
| Area | Categories |
|---|---|
| Shared components | Missing Shared DLLs, ActiveX & COM Issues, Type Libraries (TLB), Orphaned CLSID Servers, Orphaned AppID Entries, Orphaned COM+ / DCOM Apps |
| File associations and apps | Unused File Extensions (System), Unused File Extensions (User), Applications (Registered), Application Paths, App Paths (Executables), File Associations, Invalid Default Icons, App Execution Aliases |
| Installer and uninstall data | Installer Folders, Obsolete Software (Uninstall), Uninstall Metadata Values |
| Startup and policies | Run At Startup, RunOnce & Policy Startup, Image File Execution Options, Scheduled Task Cache, Scheduled Task Actions |
| Shell and Explorer | Shell Extensions, Explorer Namespace Entries, Context Menu Handlers, URL Protocol Handlers, Per-User Shell Commands, MUI Cache (MRU Lists), User MRU Caches, Notification Area Icons, Font Entries |
| System services and drivers | Windows Services, Event Log Message DLLs, Invalid Print Monitor DLLs, Invalid LSA Package DLLs, Invalid Network Provider DLLs, Invalid Keyboard Layout DLLs |
| Devices and hardware | Ghosted USB Devices, Invalid Drive Letter Paths, Broken Sound Scheme Files, Invalid Mic Permissions, Invalid Window Placements |
| Compatibility and recovery | Compatibility Store (Flags), AppCompat Layers, Obsolete App Module Caches, Invalid App Recovery Entries, Broken Autoplay Handlers, Invalid Pending Renames |
| Security and network | Firewall Rules, Invalid Defender Exclusions, Environment PATH Entries |
| User profile | Empty User Software Keys, Stale BAM/DAM Entries |
Not every category is appropriate for every system. Categories that touch services, firewall rules, Defender exclusions, or scheduled tasks can remove configuration you still need. Enable them only when you have a specific problem to solve.
The results window is titled Deep Registry Cleaner.
| Column | Meaning |
|---|---|
| Select | Checkbox used to include the row in the fix operation |
| Problem | Short description of the detected issue |
| Action | Planned fix, such as delete a value or key |
| Risk | Low, medium, or high impact estimate |
| Confidence | How certain WMT is that the entry is genuinely stale |
| Default | Whether the row is checked by default |
| Type | Registry value type or entry type |
| Value | Value name |
| Data (Path/Value) | Current value data |
| Display Key | Friendly registry path |
| Exact Registry Path | Full path used for the fix |
| Why Flagged | Explanation of the detection rule |
- Missing-file COM server entries are selected by default unless WMT classifies them as protected or as merged Microsoft COM registrations.
- Review-only rows are never fixed automatically and stay unselected.
- Press Enter to toggle the check state of the highlighted rows.
- Right-click a row to open its key in Registry Editor or copy details to the clipboard.
- The Show Protected Entries checkbox reveals rows that WMT will not modify.
A Show Protected Entries checkbox sits with these buttons and controls whether protected rows appear in the list.
| Button | Purpose |
|---|---|
| Copy Selected Details | Copies the selected findings as text |
| Copy All Details | Copies every finding as text |
| Fix Selected Issues... | Applies the checked fixes after confirmation |
| Close | Closes the window without changing anything |
Copying details is the safest way to ask for help before applying a fix. The copied text includes registry paths and value data.
When you confirm Fix Selected Issues..., WMT:
- Attempts to create a System Restore point named WMT DeepClean.
- Creates a backup file under
data\RegistryBackups:-
DeepClean_Backup_YYYYMMDD_HHmmss.regcontains the successfully changed entries. -
DeepClean_Skipped_YYYYMMDD_HHmmss.logrecords items that were skipped or failed.
-
- Applies only the checked, non-protected fixes.
- Reports how many entries were fixed and how many were skipped.
Important details:
- A
.regbackup is written only if at least one selected item is successfully changed. - The backup is written incrementally from changed entries, so it reflects what was actually modified.
- If the restore point cannot be created (for example, System Protection is off), WMT logs the failure and continues. The
.regbackup is still the primary rollback path. - Protected and review-only rows are never modified, even if they are somehow checked.
- Some fixes require administrator rights and registry ownership privileges; WMT enables
SeTakeOwnershipPrivilegeandSeRestorePrivilegefor the operation.
The target picker also contains backup controls:
| Button | Action |
|---|---|
| Export HKLM | Exports the entire HKLM hive to data\RegistryBackups\HKLM_Backup_YYYYMMDD_HHmmss.reg
|
| Import Backup | Imports a .reg file after a warning confirmation |
Export HKLM is a full-hive export and can take a while and produce a large file. Use it before major registry work, not for routine cleaning.
Import Backup opens a file picker starting in data\RegistryBackups. Importing a .reg file merges it into the current registry and can overwrite existing values. It does not delete keys that are absent from the file. Read the confirmation, and only import a backup you created or trust.
To undo a cleanup manually, double-click the .reg backup and confirm the merge, or use Import Backup. A System Restore point restores a broader system state but also rolls back other changes made after the point.
- The scanner looks for specific, known patterns. It does not prove that every flagged entry is unused.
- Software that is installed but currently offline, on a disconnected drive, or in a nonstandard location can look broken.
- Entries owned by Windows TrustedInstaller may be reported but not fixable without taking ownership.
- The scanner does not compact the registry hive, defragment it, or improve performance by itself.
- Registry cleaning is not a substitute for reinstalling a broken application or repairing Windows with System Health.