How to Use Folder Size Shell Extension 3.2: Features & Tips

Folder Size Shell Extension 3.2 — Troubleshooting Common Issues

Folder Size Shell Extension 3.2 adds useful context-menu size information to Windows Explorer, but like any system-level utility it can run into problems. This guide lists common issues, causes, and step-by-step fixes so you can get back to seeing folder sizes reliably.

1. Extension not appearing in Explorer context menu

Possible causes:

• Shell extension not registered or failed to install.
• Disabled by Explorer settings or system policies.
• Conflicts with third-party shell extensions.

Fixes:

1. Restart Explorer
   • Press Ctrl+Shift+Esc → Processes → select Windows Explorer → Restart.
2. Re-register the extension
   • Re-run the Folder Size Shell Extension 3.2 installer as Administrator and choose Repair or Reinstall.
3. Check shell extension managers
   • Use ShellExView or Autoruns (run as Administrator) to see if the extension is present and enabled. If disabled, enable it; if conflicting extensions exist, try temporarily disabling them.
4. Check Group Policy / Registry restrictions
   • If on a managed PC, confirm with IT whether context-menu items are blocked. For local edits, inspect HKEY_CLASSES_ROOT*\shellex and similar keys carefully (backup before changes).

2. Folder sizes show incorrect or outdated values

Possible causes:

• Explorer caching or delayed updates.
• Permissions prevent scanning certain files.
• Corrupted cache or indexing issues.

Fixes:

1. Refresh view
   • Press F5 in Explorer or close/reopen the window.
2. Force recount
   • Right-click the folder and select the Folder Size option again (or use the extension’s “Recalculate” if available).
3. Run as Administrator
   • If permissions block reading some files, run Explorer elevated (or run the extension’s tool as Administrator) to see full counts.
4. Clear extension cache
   • If the extension maintains a cache, delete it via the extension settings or remove cached files stored in %LOCALAPPDATA% (path depends on install). Re-open Explorer to rebuild.
5. Check for excluded folders
   • Ensure system or protected folders aren’t excluded in the extension settings.

3. Explorer crashes or becomes unresponsive after installing

Possible causes:

• Incompatible shell extension version or 3rd-party conflicts.
• Bug in the extension interacting with certain filesystem features.

Fixes:

1. Boot into Safe Mode
   • Verify Explorer stability without non-Microsoft shell extensions. If stable, a third-party extension likely conflicts.
2. Disable other shell extensions
   • Use ShellExView to disable non-Microsoft context menu handlers in batches, rebooting Explorer between changes to isolate the culprit.
3. Uninstall or downgrade
   • Uninstall Folder Size Shell Extension 3.2, verify Explorer stability, then try an earlier stable version if available.
4. Check Windows Event Viewer
   • Look under Windows Logs → Application for error details (DLL names) to identify offending modules.

4. Performance slow when scanning large folders or network shares

Possible causes:

• Scans are I/O intensive; network latency and many small files increase time.
• Antivirus real-time scanning interferes.

Fixes:

1. Limit scope
   • Scan top-level folders rather than entire drives when possible.
2. Exclude from antivirus real-time scanning
   • Add the extension’s process or scan-target folders to antivirus exclusions (follow security policies).
3. Use background counting
   • If the extension supports background or partial scans, enable them so Explorer remains responsive.
4. Update network settings
   • For network shares, ensure stable connectivity and test with a local folder to compare speed.

5. Incorrect size on NTFS compressed or encrypted folders

Possible causes:

• Difference between on-disk size and logical size; compression/encryption change reported values.

Fixes:

1. Understand reported metric
   • Decide whether you need logical (uncompressed) size or physical (on-disk) size; check extension settings for which it reports.
2. Use alternative tools
   • For precise on-disk metrics on compressed/encrypted data, use built-in fsutil or PowerShell (Get-ChildItem with measurement) if the extension lacks the needed option.

6. Language, UI, or localization problems

Fixes:

1. Install language pack or switch UI
   • Check the extension settings for language options and install/update language files.
2. Reinstall with correct system locale
   • Re-run installer while Windows uses the intended locale, or set the app’s language in its config if available.

7. Installer fails or shows errors during install

Possible causes:

• Insufficient permissions, corrupt installer, or antivirus blocking installer actions.

Fixes:

1. Run as Administrator
   • Right-click installer → Run as administrator.
2. Redownload installer
   • Verify checksum (if provided) and get a fresh copy from the official source.
3. Temporarily disable antivirus
   • Temporarily turn off antivirus during install (re-enable afterward) if it’s blocking registration steps.
4. Check prerequisites
   • Ensure required Windows updates or frameworks are installed.

When to seek further help

• If problems persist after the above steps, collect these details before contacting support:
  • Windows version and build (Settings → About)
  • Folder Size Shell Extension version (confirm 3.2)
  • Steps to reproduce, exact error messages, and Event Viewer logs
  • Whether issue occurs on local vs. network folders

Provide that information when contacting the extension’s support forum or IT so they can reproduce and diagnose the issue.

If you want, I can write a concise troubleshooting checklist you can print and follow step-by-step.