Decades‑Old File Explorer Bug: Folder View Settings Still Reset Automatically

Jorge Dias 0 Reputation points
2026-05-18T08:06:42.0233333+00:00

I have been using Microsoft operating systems for more than 30 years — from MS‑DOS to every version of Windows since 1995. After three decades, File Explorer still cannot reliably remember custom column settings in Details View. This is not a minor UI issue; it is a long‑standing architectural flaw that affects productivity and user trust.

Every version of Windows — 95, 98, NT, 2000, XP, Vista, 7, 10, 11 — suffers from the same problem: File Explorer forgets user‑defined columns and silently replaces them with automatic templates.

The root causes are well‑known:

• ShellBags / BagMRU registry system

Folder view settings are stored in HKCU\Software\Microsoft\Windows\Shell\BagMRU and …\Bags, a system created in the 1990s. It has a hard‑coded limit of 5,000 folders. After that, Windows overwrites older settings, causing column resets.

• Automatic Folder Type Discovery (“folder sniffing”)

File Explorer constantly reassigns folder templates based on content, overriding explicit user choices. Adding a single image or media file can reset carefully configured columns.

• Namespace duplication

The same physical folder is treated as multiple locations depending on the navigation path (This PC, Quick Access, Libraries, User Profile, UNC paths, symlinks). Each path generates a separate ShellBag entry, causing inconsistent or lost view settings.

• Outdated COM‑based architecture

File Explorer still relies on legacy COM objects, GUID‑based folder types, and per‑folder Bag IDs. This system has never been modernized.

• Official “fixes” do not work

“Apply to Folders”, “Reset Folders”, “Optimize this folder for…”, registry resets, and BagMRU size increases do not solve the underlying architectural limitations.

• Third‑party tools succeed where Microsoft does not

Utilities like WinSetView can enforce global templates and disable folder sniffing entirely. If independent developers can solve this, Microsoft should be able to as well.

This is a 30‑year‑old problem affecting millions of users.

There are thousands of complaints across Reddit, Microsoft Answers, TechNet, StackOverflow, and every major tech community. If this issue were truly resolved, these discussions would not exist.

As a long‑time Windows user and paying Microsoft 365 customer, I expect Microsoft to finally address this fundamental flaw. File Explorer must reliably and permanently remember user‑defined column settings without resets, overrides, or arbitrary limits.

Windows for home | Previous Windows versions | Files, folders, and storage

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-05-18T08:07:09.36+00:00

    Windows uses a per-folder view storage mechanism (ShellBags / BagMRU) and folder type “sniffing” that can lead to view resets and inconsistent behavior, especially over time and across many folders. This behavior has existed for multiple Windows versions and is acknowledged in at least one documented case.

    From the available documentation:

    1. Folder type “sniffing” can cause repeated view changes On Windows 8.1 / Windows RT 8.1 / Windows Server 2012 R2, Microsoft documents a specific issue where Explorer’s sniffing logic sends explorer.exe into a refresh loop and causes folder type changes based on file types in the folder. This is directly related to the automatic folder type discovery that can override user expectations. Microsoft’s resolution for that scenario is to install the December 2014 update rollup for those platforms, which adjusts this behavior.
    2. Folder view customizations can be lost or incorrect Microsoft’s File and Folder Troubleshooter explicitly lists “View settings or customizations for one or more folders may be lost or incorrect” as a known problem it can diagnose and repair. This confirms that loss of folder view settings is a recognized issue class. The same troubleshooter also addresses related Explorer issues such as:
      • Inability to empty Recycle Bin or delete files
      • Errors when renaming/moving files
      • Problems selecting multiple items
      • Random icon changes
    3. Icons and folder customizations are handled via legacy mechanisms The “Icons are changed unexpectedly in Windows” article describes how the MATS package manipulates the Max Cached Icons registry value and deletes IconCache.db to repair icon and folder customization problems. This shows that parts of the shell customization system still rely on legacy caches and registry values.
    4. Modern settings surface for File Explorer “classic” exists but is still state-based Windows 10/11 expose File Explorer Classic state via Windows.Data.FileExplorerClassic settings (ShellStateSetting, CabinetStateSettings, AdvancedSettings). These control behaviors like showing all objects, extensions, full path title, saving local view, and new window mode. They are still stateful settings layered on top of the existing shell model, not a replacement for the underlying architecture.
    5. Officially documented mitigations Based on the documentation in scope, the following are the supported mitigations and repair options:
      1. Install platform updates that address folder type refresh issues
        • On Windows 8.1 / Windows RT 8.1 / Windows Server 2012 R2, install the December 2014 update rollup to fix the specific folder-type refresh loop caused by sniffing logic.
      2. Use the File and Folder Troubleshooter on Windows 10
        • Download and run the File and Folder Troubleshooter (aka.ms/winfilefolder).
        • It can automatically diagnose and repair:
          • Lost/incorrect folder view settings
          • Problems with deleting, copying, moving, or renaming files
          • Issues selecting multiple items in Explorer
        • Note: The troubleshooter is based on the Microsoft Support Diagnostic Tool (MSDT), which is deprecated and will be removed from future Windows versions.
      3. Use icon/folder customization repair via MATS (older Windows versions)
        • The MATS package checks and sets Max Cached Icons to 2048 and verifies that IconCache.db is deleted, which can help with icon and some folder customization issues.
      4. Use Automatic/Startup Repair if File Explorer is unstable
        • On Windows 10, Automatic Repair can be run from Advanced startup (Settings → Update & Security → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → Startup Repair). It attempts to fix registry corruption that may affect Explorer behavior.
    6. Scope of official fixes vs. architectural change The documentation in scope confirms:
      • Microsoft has acknowledged specific bugs related to folder type sniffing and view changes and provided hotfixes/rollups for those versions.
      • Microsoft provides troubleshooters and repair tools that can correct corrupted view settings, icon caches, and some shell state problems.
      • The File Explorer Classic state model is still present in Windows 10/11.
      However, the provided documentation does not describe a complete architectural replacement for ShellBags/BagMRU, nor does it claim that all long-term folder view persistence issues are fully resolved across all Windows versions. It focuses on targeted fixes and repair tools rather than a redesign of the underlying system.

    Within the documented guidance, the practical steps available are:

    1. Ensure all relevant cumulative/rollup updates are installed (especially on Windows 8.1 / Server 2012 R2 for the folder-type refresh issue).
    2. On Windows 10, run the File and Folder Troubleshooter to repair lost/incorrect folder view settings.
    3. On older versions, use the MATS-based fix for icon and folder customization issues where applicable.
    4. If Explorer instability or corruption is suspected, use Automatic Repair from Advanced startup on Windows 10.

    For broader, systemic changes to how File Explorer stores and respects folder view settings (for example, eliminating ShellBag limits, disabling sniffing globally, or unifying views across all namespace paths), no such architectural overhaul is described in the available documentation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.