Files’ new v4.0.28 update quietly fixes one of the small, daily frictions that make File Explorer alternatives compelling: the right‑click context menu in the app is now more consistent, faster to use, and — crucially — configurable, putting a routine action (Properties) front and center and letting users remove noisy pinning commands from the top level.
Background / Overview
Windows’ built‑in File Explorer has been a battleground for UX debates ever since Windows 11 rearranged core surfaces and introduced a sleeker, touch‑oriented context menu that buried many long‑used commands behind a “Show more options” step. That change created a generation of power users who either tolerated extra clicks or adopted third‑party alternatives that restored discoverability and efficiency. The open‑source Files app has become one of the most prominent alternatives, offering tabs, column and dual‑pane views, file previews, and a deliberately customizable interface that targets the exact pain points power users complain about.
Files’ v4.0.28 arrives in that context: an incremental but meaningful polish release that addresses context‑menu ergonomics, third‑party cloud detection quirks, icon customization for shortcut types, and a handful of stability fixes. The update is explicitly framed as a quality‑of‑life release, while the project continues to work on heavier performance items such as thumbnail loading.
What changed in Files v4.0.28
The changelog for v4.0.28 is compact and pragmatic: it does not add blockbuster features, but it tightens the experience in ways that matter in day‑to‑day file management. Key items in the release include:
- Context menu rework: The Properties action is now promoted to a primary menu item in both the Sidebar and Home page context menus, bringing parity across places where users expect to inspect metadata.
- Context menu toggles: Users can disable Pin to Start and Pin to Sidebar menu items via Settings → General → Context Menu Options, removing accidental pinning and reducing top‑level clutter.
- Microsoft Store Dropbox support: Files now recognizes cloud drives provided by the Microsoft Store build of Dropbox in addition to the traditional Win32/non‑Store client, closing a compatibility blind spot.
- Icon customization for URLs and shortcuts: The Properties customization page now allows icon changes for URL (.url) and shortcut (.lnk) file types, a small but welcome personalization affordance.
- Smooth‑scroll toggle: Smooth scrolling can be disabled from Settings → General → Scrolling, giving users a way to prefer discrete wheel behavior if they find the animation intrusive.
- Bug fixes: Addressed missing “Open With” for script files, fixed tab switching via mouse wheel, corrected SEER behavior, prevented default app toggles from flipping unintentionally when mixing stable and preview builds, fixed tag searches with spaces, and more.
Those changes are corroborated by independent coverage and by community changelogs; the Files team published the release announcement, and third‑party aggregators have summarized the same items.
Why the context‑menu change matters
The context menu is a high‑impact surface
Right‑click menus are the most frequently used command surface in a file manager. They are the handshake between user intent and the system’s services: rename, properties, pinning, sharing, and extension verbs from third‑party apps all live there. When Microsoft simplified the default Windows 11 menu, it improved visual clarity for touch users but increased friction for desktop power users who suddenly needed an extra click for routine tasks. Files’ choice to
promote Properties to a top action directly addresses that micro‑friction.
Consistency reduces mental load
Making a routine action like
Properties behave the same across the sidebar and the home page is a small design move with outsized returns: users build muscle memory faster, keyboard and screen‑reader interactions become more predictable, and documentation or help resources can point to a single location. The addition of opt‑outs for common pinning verbs gives users control over accidental UI noise — a practical feature that acknowledges different workflows (some users want fast pinning; others find pin clutter damaging).
Power‑users win; admins should be aware
For power users, this is pure productivity: fewer clicks, clearer affordances, and a less cluttered menu. For IT administrators, the change is neutral to positive, but it raises two considerations: first, third‑party file managers can alter expected behaviors in managed environments; second, users who set Files as the default may need guidance if enterprise‑standard tooling depends on shell integration. The Files changelog actually notes a bug fix around switching defaults between Stable and Preview channels, which shows the team is aware of this exact interaction.
Cloud drives, packaging, and detection quirks
One underappreciated source of friction in the Windows ecosystem is how differently cloud storage vendors ship their clients. A provider can offer a traditional Win32 installer, an MSIX/AppX package, or a Microsoft Store wrapper — each exposes different shell hooks and mount points. Files’ explicit support for the Microsoft Store build of Dropbox reduces a common confusion: the app previously only recognized the non‑Store Dropbox client. That improvement is practical for users who prefer installing from the Store for security, update behavior, or enterprise policy reasons.
Files’ documentation describes how the app detects and surfaces cloud drives: the integration is client‑side and depends on the cloud provider’s local client to register drive roots or shell providers. That means Files can’t conjure native support for every cloud service automatically — it relies on how vendors expose their storage to the OS — but the team is actively expanding detection compatibility.
Personalization and accessibility: small features with real value
The ability to change icons for URL and shortcut files is a niche feature, but it has visibility value: shortcuts and links can be visually distinguished, making galleries and shared folders easier to parse visually. Similarly, adding a
smooth‑scroll toggle is a nod to accessibility and preferences: not all users benefit from animation smoothing, and allowing a toggle respects diverse input devices and motion‑sensitivity needs. These smaller preferences often have outsized importance for users who spend hours in a file manager daily.
The stability work: fixes that stop recurring annoyances
Files’ release notes show targeted fixes for real‑world pain points:
- Restores “Open With” for script files — a common developer annoyance when the OS already treats text/exec file types specially.
- Fixes scroll‑wheel tab switching and SEER reopen behavior — two interactions that, when broken, quickly erode confidence in an app’s reliability.
- Corrects default app toggles between Stable and Preview channels — a practical reliability issue for users who test Preview builds and then revert to Stable releases.
These are the kinds of iterative quality improvements that separate hobby projects from maintenance‑grade alternatives. The Files team also called out ongoing work to make thumbnails load faster — a heavier, measurable performance problem that remains on their roadmap.
How this fits into Microsoft’s broader File Explorer story
Microsoft has been iterating on File Explorer and other core surfaces with mixed results: recent File Explorer experiments — such as a “Recommended files” feed that surfaced large thumbnails in Home — were paused after rollout issues and community backlash. That pause and a broader revaluation of AI‑heavy integrations underline a larger point: users want practical, predictable improvements before novel, disruptive features. Files’ incremental, user‑control‑first changes stand in contrast to some of Microsoft’s more aggressive experiments.
There’s also a wider lifecycle context: Windows 10 reached end of support on October 14, 2025, which accelerated migration discussions and placed new emphasis on Windows 11’s user experience as upgrade incentives. For many users, file management is a daily pain point, and third‑party tools are filling gaps while Microsoft rebalances product direction.
Security and compatibility considerations
Third‑party file managers inevitably invite questions about security, shell integration, and enterprise compatibility. Here are the practical risk and mitigation points users and admins should weigh:
- Shell extension exposure: Files relies on Windows APIs and, for some features, shell extensions registered by cloud clients. If you install untrusted shell extensions, you increase attack surface. Always prefer official clients and verify publisher signatures.
- Default app behavior: Files is a popular default replacement. The release notes explicitly mention a bug where defaults flipped when mixing channels — a reminder that default handler registration must be managed carefully in environments where policy and automation expect the Microsoft Explorer behavior.
- Permission model: Any app that previews or manipulates files needs the usual file system permissions; for networked or cloud files, sandboxing and client behavior matter. Files appears to surface cloud drives that the local cloud client exposes; it does not itself replace cloud providers’ authentication models.
- Enterprise governance: IT teams should test third‑party file managers before mass rollout. Policy tools and imaging processes should explicitly account for alternative default handlers and verify whether enterprise tools (backup, DLP, EDR) are fully compatible. Files’ active maintenance and release notes suggest a mature project, but that is not a substitute for organizational validation.
Practical guidance for users and IT professionals
If you’re considering trying Files or upgrading to v4.0.28, here’s a pragmatic checklist:
- Back up your settings and note any shell integrations you depend on (sync clients, archivers, version control hooks).
- Test the app in your normal workflows: open, rename, search, context‑menu actions, and any enterprise tools that integrate with the file system.
- If you use the Microsoft Store version of Dropbox, confirm Files now detects the cloud root as expected — this was a stated fix in v4.0.28.
- If you administer systems, test default app registration and group‑policy interactions in a controlled environment before rolling Files out broadly. Files’ team has already fixed at least one default‑switching bug, but behavior can vary across builds and channels.
The limits of small updates: why incremental UX matters, but is not enough
Files v4.0.28 shows a product focused on polishing everyday flows rather than reshaping the file management paradigm. That is a strength — it addresses the cold‑start, repetitive tasks that accumulate into real productivity losses. But there are limits:
- Fixing context menu discoverability does not solve broader problems such as fragmented cloud provider APIs, search relevance across local and cloud files, or the performance characteristics of thumbnail generation on large datasets. The Files team has acknowledged those performance targets and placed them on the roadmap.
- The broader Windows ecosystem continues to change: Microsoft’s experimentation with recommended feeds, Copilot integrations, and storage provider APIs influences what users will expect from a file manager in 12–24 months. Third‑party apps can be nimble, but they cannot change platform‑level indexing or access patterns without platform cooperation.
In short: v4.0.28 is a meaningful incremental win, but it is not a catch‑all replacement for platform investments in file discovery and cloud parity.
Community and maintenance dynamics
Files is an open‑source community project with both a Microsoft Store presence and a GitHub sponsor model. That model has advantages: rapid response to user feedback, transparent changelogs, and optional paid distribution that supports development while leaving the core project open. The project’s responsiveness — quick fixes and a detailed changelog — is a positive signal for long‑term users who need a reliable maintenance cadence.
However, community projects also have structural risks: volunteer bandwidth, contributor churn, and dependency management for platform APIs can all affect long‑term viability. Users and organizations should weigh these factors when making a default‑app decision: pick a tool that balances feature needs with a sustainable maintenance model and clear update practices.
Verdict: meaningful polish, practical control
Files v4.0.28 is not a headline‑grabbing release, and that’s the point. It makes targeted changes that reduce micro‑friction and give users control over one of the most used UI surfaces in any file manager: the right‑click context menu. By promoting
Properties, exposing toggles to hide pinning commands, and improving cloud detection for Store‑packaged Dropbox clients, Files addresses concrete annoyances that push users toward third‑party alternatives in the first place.
From a broader perspective, Files’ steady, community‑driven approach contrasts with Microsoft’s mixed record of large‑scale UX experiments and pulled rollouts. Users who prioritize predictable, tweakable file management will find v4.0.28 a welcome step; enterprises and admins should still validate integrations and default‑handler behaviors before wide deployment.
What to watch next
- Thumbnails and performance: Files has said thumbnail performance improvements are in active development. When implemented, faster thumbnail generation will be one of the most tangible upgrades for users with large photo or media libraries.
- Storage provider parity: Microsoft paused the recommended files rollout and related StorageProvider API expansion; how Microsoft chooses to support third‑party cloud providers in File Explorer will affect the value proposition of Files and alternatives. Better platform parity reduces the need for third‑party workarounds.
- Policy and enterprise readiness: watch how Files’ default‑handler behavior matures across channels. The team already fixed a bug where switching between Stable and Preview could flip defaults — a promising sign, but admins should continue to test.
Conclusion
Files v4.0.28 is a textbook example of how thoughtful, incremental improvements can materially improve day‑to‑day productivity. By focusing on context‑menu consistency, giving users the power to remove accidental pinning verbs, and closing compatibility gaps with the Microsoft Store version of Dropbox, the update reduces friction precisely where it accumulates: in repeated, small interactions. For users frustrated by Windows 11’s file‑management changes, Files remains a practical, well‑maintained alternative; for IT professionals, this release is a reminder that third‑party tools can fill real gaps — but that due diligence is still required before widescale adoption.
Source: Windows Central
This third‑party Windows 11 app fixes one of its most annoying UX problems