The Files community has shipped a focused, practical update that sharpens the app’s right‑click experience, extends cloud detection, and adds a handful of polish settings users have asked for — all part of the steady cadence of improvements that has made Files the most compelling third‑party File Explorer alternative on Windows 11. The v4.0.28 release makes
Properties a first‑class action in more places, lets you hide or show several context‑menu items, adds support for the Microsoft Store build of Dropbox, and exposes extra customization for URL and shortcut icons, plus a toggle for smooth scrolling — small changes that add up to a noticeably more consistent and configurable file‑management experience. (
files.community)
Background
Files started life as an open‑source reimagining of File Explorer: modern UI, tabbed browsing, dual‑pane and column navigation modes, integrated archive support, file tagging, and numerous refinements that power users and enthusiasts have been requesting for years. The project is maintained on GitHub and shipped through both the Microsoft Store and direct downloads; its release cadence is brisk and transparent, with detailed change notes posted by the developers for each build. (
github.com)
Over the last two years Files moved from a feature‑packed hobby project to a polished, stable product that many users rely on as their daily file manager. That growth has been fueled by a responsive contributor base, an active issue tracker, and a release process that mixes stable channel updates with preview builds for early testing. Files’ feature set positions it as a true alternative to Windows File Explorer rather than just a novelty; this makes even small quality‑of‑life updates — like the context‑menu improvements in v4.0.28 — meaningful to a significant number of users. (
github.com)
What v4.0.28 actually changes
Context menus: consistency and control
The headline change in v4.0.28 is the
refinement of right‑click context menus across the app. Specifically:
- Properties is promoted to a primary action in both the Sidebar and Home Page context menus, making it easier to reach file metadata and properties without hunting through nested menus. (files.community)
- New settings allow you to hide “Pin to Start” and “Pin to Sidebar” from context menus. This is exposed under Settings → General → Context Menu Options and is a direct nod to users who want minimalism or who prefer to avoid accidental pinning. (files.community)
- The update also includes visual refreshes to toolbar and context‑menu icons and addresses subtle sizing/behavior issues that historically caused the context menu to resize or flicker while shell extensions loaded. (files.community)
These changes are targeted: they do not overhaul the whole context‑menu model but instead make high‑value actions easier to access while giving users control over clutter. For users who rely on Discoverability (e.g., occasional users or those migrating from File Explorer), the primary‑action promotion reduces friction; for power users, the ability to selectively hide entries prevents accidental activations.
Cloud and integration improvements
Files now recognizes the
Microsoft Store version of Dropbox, not just the traditional Win32 installer variant. That matters because cloud clients installed via the Store can expose different mount points and APIs; previously Files’ detection logic missed the Store build for some configurations. Broader cloud detection improves reliability for users with mixed‑source installations of Dropbox or other cloud clients. (
files.community)
Customization and usability
- You can now customize icons for URL and shortcut file types on the Properties customization page, which helps users visually distinguish frequently used link and shortcut files at a glance. (files.community)
- A new toggle lets users disable smooth scrolling from Settings → General → Scrolling. This is a small but thoughtful addition for users who prefer the snappier, non‑interpolated feel of traditional scrolling or who need consistent scrolling behavior across multiple displays and input devices. (files.community)
Bug fixes and quality work
The changelog lists a number of targeted fixes: restoration of the Open With menu for script files, scroll‑wheel tab switching reliability, SEER behavior, tag search quirks, and inconsistencies in how hidden item file types were displayed. Together, these fixes smooth out everyday annoyances. (
files.community)
Why these changes matter (and how they fit into a bigger picture)
Context menus are a high‑impact surface
The right‑click context menu is the single most frequently used surface in any file manager. Microsoft’s own recent work on File Explorer context menus demonstrates how much attention this area warrants: Windows 11 has progressively reorganized the menu to surface top commands and to group app‑specific verbs in predictable ways, and Microsoft has been experimenting with caching and background preloading to address cold starts and menu loading issues. Files’ v4.0.28 moves in the same direction — prioritizing commonly used actions and reducing top‑level clutter — but with an
open‑source twist: user‑toggleable options and more granular control.
By making
Properties a primary action in more places, Files reduces clicks for a routine task. By offering toggles to remove “Pin” actions, it respects diverse user workflows: some users want the full ability to pin; others prefer a minimal, accidental‑proof menu.
Cloud detection is increasingly important
Cloud drives are not monolithic. The way a service is installed — as an unpackaged Win32 client, MSIX, or a Microsoft Store app — affects how drive roots are exposed, how shell extensions are registered, and how the OS surfaces provider verbs. Files’ recognition of the Dropbox Microsoft Store variant is a practical, compatibility‑first improvement that reduces confusion for users who install cloud software through the Store. Given the increasing fragmentation of distribution methods, this kind of detection work matters. (
files.community)
Small customization options yield big UX wins
Icon customization for URL and shortcut files is a niche feature, but it improves
scannability and supports personalization and accessibility. The smooth‑scroll toggle is likewise small, but it addresses a perennial complaint for mixed‑input and multi‑monitor setups where interpolation can be jarring or cause motion sickness.
Strengths: what Files gets right with v4.0.28
- User‑centric, incremental improvements. The changes are precisely the sort of incremental polish that makes daily use smoother: fewer clicks, more predictable menus, fewer accidental actions. The developers are focusing on tangible pain points rather than splashy but unproven features. (files.community)
- Transparent release notes and preview channel. Files publishes clear changelogs and runs preview builds so early adopters can test performance improvements before they land in stable channels. That’s a mature approach for an open‑source project and reduces upgrade risk for power users. (files.community)
- Better cloud parity. Recognizing Store‑packaged cloud clients is a pragmatic compatibility improvement that prevents missed mounts and perplexing “where’s my Drive?” support tickets. (files.community)
- Granular customization. Options to toggle context‑menu items and to change icons reflect an understanding that one size does not fit all. These are features that power users prize. (files.community)
Risks and trade‑offs: what to watch for
- Shell extensions and third‑party integration. Context‑menu behavior depends heavily on third‑party shell extensions and how the OS exposes verbs. Files’ adjustments to context‑menu loading and to when shell extensions appear reduce flicker and resizing, but they might expose compatibility edge cases with poorly written extensions. Users who depend on niche shell extensions should test their workflows in the updated build. (files.community)
- Discoverability vs. minimalism. Hiding “Pin to Start” or “Pin to Sidebar” is welcome to many, but hiding too many items risks burying functionality newcomers expect. Files’ approach — giving users the choice — is sound, but default settings matter. The project will need to monitor telemetry and feedback to avoid creating a confusing out‑of‑the‑box experience for less technical users. (files.community)
- Fragmentation of user experience. Power users love Files because it diverges from File Explorer in helpful ways, but divergence increases fragmentation across Windows environments. IT administrators who standardize on File Explorer behaviors may find Files’ customizations a management concern in enterprise deployments; conversely, Files’ configurability may be an asset for tailored environments. (github.com)
- Security surface area. Any time an app parses or exposes file metadata, or interacts more deeply with shell extensions and cloud providers, there’s an increased security auditing requirement. The Files community has been active in addressing bugs, but larger enterprises should exercise standard vetting for open‑source software used on managed machines. (github.com)
Verification and cross‑checking: what I confirmed and where
I verified the release details directly from the Files project announcement for v4.0.28; the blog post lays out the core changes, the settings locations, and the short list of fixes. (
files.community)
I cross‑checked the release listing and contributor notes against the project’s GitHub releases page to confirm the version tag, release date, and the fact that v4.0.28 is the latest stable release at the time of writing. (
github.com)
Third‑party coverage from independent outlets summarized the same highlights — context menu adjustments and Dropbox Store detection — which corroborates that these are the primary, user‑facing changes in the update. These independent writeups confirm the scope and intent of the release.
Finally, to put the context‑menu changes in perspective I reviewed notes and community threads about Microsoft’s own context‑menu work in File Explorer and the broader UX rationale for promoting common verbs and grouping app‑specific entries. Files’ changes track well with the broader industry trend toward surfacing commonly used actions and grouping provider/extension verbs to reduce clutter.
If any claim in this article cannot be independently verified — for example, the exact internal heuristics the Files app uses to detect certain Dropbox builds on every possible machine configuration — I flag it as such and recommend users test in their own environment before assuming parity.
Practical guidance: how to adopt v4.0.28 safely
- Check your distribution channel. If you use the Microsoft Store version of Files, the update should show automatically; stable channel users will see an in‑app update icon. Preview users can test newer changes earlier. (github.com)
- Before switching defaults, test shell‑extension behavior. If you rely on third‑party context‑menu extensions, right‑click several representative file types after updating to ensure those extensions load reliably. If you notice missing entries, file a bug with the Files project and, in the interim, re‑enable the classic or stable behavior if needed. (files.community)
- Customize context menus intentionally. To hide Pin to Start or Pin to Sidebar, open Settings → General → Context Menu Options and toggle as desired. Take a few minutes to see how that impacts your daily flow. (files.community)
- Test cloud drive detection. If you use Dropbox from the Microsoft Store, confirm that your mount points and cloud‑file verbs appear in the sidebar and context menus. If Files still misses the drive, collect environment details and report them to the project so they can refine detection heuristics. (files.community)
- Back up settings before major changes. Files stores preferences in a location that can be exported; take a snapshot of your config so you can restore if a setting tweak behaves unexpectedly. The project’s documentation and preview releases make this straightforward. (github.com)
What power users and admins should care about
- Power users will appreciate the tiny productivity wins: a consistent Properties location, cleaner menus, and icon customization for quicker visual parsing of folders full of shortcuts and links. These are the kinds of small refinements that compound over hundreds of daily interactions.
- System administrators should evaluate Files’ update path and how it fits into managed environments. The app can be distributed via the Store or via direct installers; organizations that standardize user environments should consider testing Files in a controlled pilot before wider rollout. (github.com)
- Enterprises with strict security controls should treat Files like any third‑party client: vet it for compliance, validate behavior with managed shell extensions, and ensure that remote support teams are comfortable with the app’s settings and troubleshooting workflows. (github.com)
The roadmap and what to expect next
The Files team signaled that
thumbnail performance improvements are in active development and that work will land in the preview channel first. This kind of performance engineering — focused on faster thumbnail loading — has the potential to materially improve perceived responsiveness in media‑heavy folders. The developers are taking a measured approach: iterating in preview, testing, and then promoting to stable once they’re confident. That incremental methodology reduces rollout risk and encourages community testing. (
files.community)
Longer term, expect continuing convergence on the UX patterns Microsoft is promoting for File Explorer: clearer top‑level verbs, grouped provider actions, and better handling of provider extensions and shell verbs. Files has the flexibility to experiment more rapidly than a large vendor might, and that agility makes it an interesting bellwether for what power users might want from a modern file manager. (
files.community)
Final assessment
Files v4.0.28 is a good example of focused, user‑led product evolution. The changes are pragmatic: promote common actions, reduce accidental clicks, and improve compatibility with modern cloud distributions. For people who have already made Files their default, the update will feel like a steady refinement that removes small friction points. For evaluators still on the fence, the release strengthens the case that Files is now a mature, production‑ready alternative to Windows File Explorer — particularly for users who value customization, rapid iteration, and a modern UI.
That said, the usual caveats apply: test shell‑extension behavior, validate cloud detection in your environment, and back up settings before sweeping changes. The Files community’s transparent release notes and preview channel make those tests straightforward, and the project’s active development signals continued improvements ahead — notably thumbnail performance optimizations that should make media browsing snappier. (
files.community)
Files continues to demonstrate that practical polish and community‑driven responsiveness can keep a third‑party file manager competitive with built‑in system tools — and v4.0.28 is another step along that road.
Source: Neowin
Popular Windows 11 file manager Files gets improved context menus and more