Where Is Quick Access in Windows 11: The Real Mechanics Behind the Folder

Quick Access in Windows 11 lives inside File Explorer: open any folder window, and the Quick Access view appears in the navigation pane's top section and as the default landing page, listing pinned folders above recently used files. If you pinned a folder and cannot find it, the pin is stored per-user in File Explorer's settings database, not as a shortcut on disk.

The name itself is the first trap. In Windows 11's 22H2 update and later builds, Microsoft split the old combined Quick Access view into two separate navigation entries: Home and Gallery. The pinning behavior survived, but the label that millions of users search for did not survive in the same place. That single rename explains most of the confusion behind this query. What follows is the mechanism-level account of where the feature actually lives, why pins vanish, and how to recover or deliberately move it.

Where the Quick Access view actually renders

File Explorer's navigation pane is not a folder tree in the traditional sense. It is a composite view assembled at runtime from several data sources: the known-folder registry entries, the shell namespace, and a per-user settings file that records which folders the user has pinned. Quick Access is one of those assembled views, which is why it has no physical path you can type into the address bar.

Pinned Quick Access folders are recorded in a file named f01b4d95cf55d32a.automaticDestinations-ms inside the user's AppData folder under Roaming\Microsoft\Windows\Recent\AutomaticDestinations. That file is a jump list database, the same binary format Windows uses for taskbar jump lists. It stores the pinned entries as shell item identifiers rather than plain text paths. In plain language: the pin is a bookmark written in a Windows-specific shorthand, not a shortcut file.

This has a direct consequence. You cannot copy Quick Access pins to another user profile by copying a folder. You cannot back them up by dragging anything to a USB drive. And when the underlying target moves or its drive letter changes, the stored identifier no longer resolves, so the pin appears to break rather than update. The entry may remain visible but open nothing, or it may silently drop from the list.

Quantified context: how much Quick Access holds and when it forgets

Quick Access is bounded in ways most explainers never state. The recent-files list is capped by a setting in Folder Options with a default of 20 items, adjustable only through registry values since Windows 11 removed the visible spinner from the General tab in some builds. The pinned list has no documented hard cap, but performance degrades as the settings database grows; power users who pin hundreds of network shares report slower navigation pane rendering because every pin is resolved at view load.

The "Show recently used files" and "Show recently used folders" toggles live under Folder Options, View tab, in the Privacy section. Turning either off clears the corresponding list and stops new entries from accumulating. The clearing is immediate and not undoable through the interface.

There is a retention detail worth flagging. If you disable "Show recently used files in Quick Access," Windows stops populating the list but does not necessarily erase existing entries on every build; behavior has varied across feature updates. The reliable way to purge is the Clear button next to that checkbox, which wipes both lists.

Timeline: what happened to the label, build by build

The confusion is a version problem, and the timeline makes it legible.

Read the table as a translation guide. A user following a Windows 10 tutorial will look for a node called Quick Access, not find it, and conclude the feature was removed. It was not removed. It was renamed and its pin storage mechanism carried forward unchanged. The folder that opens by default when you press Windows key + E is Home, which contains the pinned section at its top.

Edge cases that break pins

Several conditions cause pins to disappear or fail, and each has a distinct mechanism.

A moved or renamed target breaks the shell identifier even though the file system path changed only slightly. Renaming a parent folder cascades to every pinned child beneath it. Remapping a network drive to a different letter breaks every pin that pointed at the old letter, because the stored identifier encodes the drive context.

A corrupted jump list database can wipe the entire pin set at once. This typically follows an unclean shutdown or a profile migration tool that copies AppData without preserving file locks. The symptom is a Home view with no pins at all despite no user action.

Profile-level policy can hide the section. In managed environments, a Group Policy setting under User Configuration, Administrative Templates, Windows Components, File Explorer controls whether recent files appear in Quick Access. When the policy is enforced, the toggles in Folder Options gray out, and users cannot re-enable the list. This is a common source of "my pins keep resetting" reports in corporate laptops.

Warning: do not delete the AutomaticDestinations folder contents manually to "reset" Quick Access; you will also destroy taskbar jump lists, recent-document history, and pinned Start items that share the database. Warning: one-third-party "cleaner" tools flag the jump list database as junk and purge it, silently removing every Quick Access pin. Warning: syncing a roaming profile across machines with different drive mappings produces pins that resolve on one device and fail on another. Warning: if Folder Options toggles are grayed out, a policy is in force; changing them in the registry will be overwritten at next policy refresh.

Misconceptions about the feature

The most persistent misconception is that Quick Access is a folder you can navigate to. It is a view. There is no C:\Users\Name\Quick Access directory, and typing that path fails. The pins point elsewhere; the view is a launcher.

A second misconception holds that pinning a folder copies or moves it. Pinning creates a reference only. Deleting the pinned folder leaves a dead entry; deleting the pin never touches the target. Users who "clean up" pins expecting to free disk space accomplish nothing, because the pins occupy kilobytes at most.

A third misconception treats the recent-files list as a privacy-neutral convenience. It is a behavioral record. On a shared machine, the Home view can expose document names a user opened but did not intend to share. The correct mitigation is the Folder Options toggle, not deleting files from the list one at a time.

The counterintuitive detail professionals rely on: pinning a folder to Quick Access also pins it to File Explorer's jump list on the taskbar icon, but only if the taskbar jump list setting is enabled. Disabling jump lists in taskbar settings severs that second surface while leaving the navigation pane pin intact. Two surfaces, one pin record, independent display switches.

Comparison: where to put a frequently used folder

The table's practical reading: pins are the fastest to create and the least portable. If the goal is durability across machines, a shortcut or symbolic link in a synced folder outperforms a pin despite requiring more setup.

Practical actions: restore, relocate, and control Quick Access

Restoring a missing pinned section takes three checks in order. First, open File Explorer, click View, then Show, and confirm Navigation pane is enabled; a collapsed pane hides the section entirely. Second, open the Options dialog from the three-dot menu, go to the View tab, and confirm both "Show recently used files" and "Show recently used folders" are checked. Third, expand the navigation pane's Home node; if pins exist but the node is collapsed, the section is present but out of sight.

To re-pin a folder, right-click it in the navigation pane or the file list and choose Pin to Quick Access. The command appears in the context menu under Show more options on builds where the compact menu is enabled. The pin takes effect immediately and appears at the top of the pinned group. To unpin, right-click the pinned entry and choose Unpin from Quick Access. There is no confirmation dialog, and no undo.

To control the recent list, open Folder Options, View tab, and use the two Privacy checkboxes. Unchecking stops accumulation; the Clear button beside them purges existing entries. On managed machines where the checkboxes are grayed, the setting is policy-controlled and local changes will not persist.

To recover pins after a profile migration, do not copy the AutomaticDestinations folder while Explorer is running. Sign out first, copy the file, sign back in. Copying while the shell holds the file open produces a stale or locked database and the pins will not appear.

Threshold guidance for when to abandon pins: if a folder lives on a network share that remaps its drive letter more than occasionally, or if the user works across two machines with different drive layouts, pins will break repeatedly. Below that threshold, pins are the lowest-friction option. Above it, a symbolic link in a synced folder pays for its setup cost within a few migrations.

Limitations and what the interface does not tell you

The behavior described here is stable across Windows 11 builds through 24H2, but Microsoft has changed the navigation pane twice in three years and has signaled continued consolidation of OneDrive and recommendation surfaces into Home. Any statement about the exact label is therefore version-bounded; the underlying pin mechanism has been stable since Windows 10 and is the safer thing to reason about.

Two limits deserve explicit statement. First, the jump list database format is undocumented. Recovery from corruption is best handled by letting Windows rebuild it after a sign-out, not by manual editing. Second, policy precedence overrides user preference silently in managed environments, and the interface offers no banner explaining why a toggle refuses to stay set. Diagnosing that requires checking applied Group Policy, which is outside the scope of the File Explorer interface itself.

This article is general educational information about Windows interface behavior, not a support contract or a guarantee of outcomes on any specific build or managed device. Configuration options and defaults can change with feature updates and organizational policy. For a device under IT management, consult your local administrator before changing File Explorer settings.