Lightweight File Type Registry Viewer: Install, Configure, and Customize

Troubleshooting with File Type Registry Viewer: Tips & Tricks

What it is

File Type Registry Viewer displays file-association data from the system registry (extensions, ProgIDs, verbs like open/edit, default icons, and associated applications), helping diagnose why files open with a particular program or show incorrect icons.

When to use it

• Wrong program opens a file type
• Missing or incorrect file type icons
• “Open with” menu shows obsolete entries
• Double-click does nothing or prompts repeatedly
• You need to clean up orphaned ProgIDs or shell verbs

Quick checklist (order to follow)

1. Confirm extension → ProgID mapping — verify the extension key (e.g., .txt) points to the expected ProgID.
2. Check ProgID shell verbs — inspect shell\open\command and other verbs to ensure paths and arguments are correct.
3. Verify DefaultIcon — ensure DefaultIcon string points to a valid file and resource index.
4. Look for UserChoice overrides — on modern Windows check UserChoice under HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts<.ext>\UserChoice which can override defaults.
5. Search for duplicate or conflicting ProgIDs — remove or repair old entries added by uninstalled apps.
6. Validate file paths and quotes — commands must correctly quote paths with spaces; check for missing/extraneous parameters.
7. Check 32-bit vs 64-bit registry hives — on 64-bit systems examine both registry views if behavior differs between ⁄₆₄-bit apps.
8. Backup before editing — export keys or create a system restore point.

Step-by-step fixes

1. Fix wrong default program:
   • Find .ext → ProgID.
   • Confirm ProgID\shell\open\command points to intended executable.
   • If UserChoice exists, remove it (only after confirming) to let system use ProgID defaults; then re-register default program via Settings > Apps > Default apps.

2. Restore missing icon:

   • Open ProgID\DefaultIcon and set to “C:\Path\to\app.exe,0” (adjust index).
   • Rebuild icon cache if changes don’t appear (log off or use taskkill /IM explorer.exe & start explorer).

3. Remove stale “Open with” entries:

   • Under HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts<.ext>\OpenWithList and OpenWithProgids remove obsolete entries.
   • Restart Explorer.

4. Repair broken verb that gives errors:

   • Correct command string; include “%1” where file path should be passed.
   • Avoid extra parameters that some apps don’t accept.

5. Resolve double-registration/priority conflicts:

   • Ensure only the desired app registers for the verb and clean up other app ProgIDs.
   • Use Default Programs UI or re-run the application’s installer repair if unsure.

Diagnostic tips

• Use the Viewer’s search to find all references to a ProgID or executable.
• Compare HKCR (merged view) vs HKCU/HKLM to see per-user vs system-wide settings.
• Temporarily set a different app as default to test whether the registry change takes effect.
• Record original values before changes.

Safety and best practices

• Export any key you change.
• Prefer using the app’s installer/uninstaller or built-in Default Apps settings for common tasks.
• Test changes on a non-production machine when possible.
• Don’t delete CLSID or COM-related keys unless you understand dependencies.

When to escalate

• Registry entries appear correct but system still misbehaves — consider file-system corruption or shell extension conflicts.
• Errors from signed system components or when multiple users are affected — escalate to system admin/support.

If you want, I can convert this into a printable checklist or provide exact example registry key paths and sample command strings for a specific extension (tell me which extension).