Phone Link Photos Moves to File Explorer on Windows 11

Microsoft has quietly begun removing the Phone Link app’s built‑in Photos viewer and redirecting users to File Explorer, telling Windows 11 owners to browse and manage mobile photos from a mounted mobile device entry instead of the app’s curated gallery view.

Background / Overview​

Phone Link (formerly Your Phone) has been one of Windows’ most visible continuity tools: notifications, messages, calls, app streaming and a simple gallery that displayed recent phone photos inside a single pane. That in‑app Photos view queried Android’s MediaStore to present a unified, recency‑sorted gallery of screenshots, camera photos and images from other apps — a deliberately lightweight surface designed for quick grabs and drag‑and‑drop workflows. Recent notifications inside Phone Link now display an alert reading “Photos is moving to File Explorer,” and tapping the Photos tile redirects users into File Explorer’s virtual mobile device view instead. Microsoft introduced the File Explorer integration last year as a way to mount a paired Android phone inside the shell so it appears like a removable device. That integration exposes full phone folders (Camera, Screenshots, Downloads, app folders) and supports full file operations — multi‑select, copy/paste, drag‑and‑drop, rename and video playback — capabilities Phone Link’s gallery intentionally avoided at scale. The File Explorer mount is provided by the Cross‑Device Experience Host on Windows and the Link to Windows service on the phone; turning it on requires a pairing flow in Settings → Bluetooth & devices → Mobile devices → Manage devices and enabling the “Show mobile device in File Explorer” toggle. Microsoft’s support pages list Android 11+ as the recommended baseline and call out specific Link to Windows minimum versions for full compatibility.

---

What’s changing — the practical details​

• The Phone Link app’s Photos tab now surfaces a banner telling users that “Photos is moving to File Explorer,” and the Photos tile redirects to File Explorer when the File Explorer mount is enabled. Early hands‑on reports and community testing show Phone Link opening the phone’s Camera folder inside a CrossDevice mount when users accept the redirect.
• File Explorer exposes the phone’s full folder tree — not a curated “recent” gallery — which means videos and other storage locations become available and standard Windows file operations work as if the phone were a removable drive. This enables robust bulk file management but eliminates Phone Link’s single‑pane aggregated gallery UX.
• Microsoft’s publicly documented setup requires a Windows 11 PC, an Android device (Android 11 or later for the best experience), a current Link to Windows app on the phone, and the Cross‑Device Experience Host package on Windows. The company recommends enabling the “Show mobile device in File Explorer” toggle from Settings → Bluetooth & devices → Mobile devices once the device is paired.
• There is no publicly announced deprecation timeline for the Phone Link gallery. Reporting describes a staged rollout of the redirect and recommends users prepare for the change, but Microsoft has not published a firm removal date for the in‑app Photos viewer; treat any claims about an exact removal date as unverified until Microsoft publishes formal release notes.

---

Why Microsoft is doing this: consolidation, capability and costs​

Microsoft frames this move as a consolidation: presenting mobile files in two separate Windows surfaces (Phone Link’s gallery and File Explorer) is redundant, and File Explorer is a more capable place to perform the common file‑management tasks users perform when moving media between phone and PC. From an engineering and product‑management standpoint, centralizing file workflows in File Explorer reduces duplicated maintenance, simplifies security and consistency concerns, and leverages existing file APIs and tools that are already mature in Windows.
There are practical benefits:

• File Explorer supports bulk operations (multi‑select, rename, move) that Phone Link’s gallery did not intend to handle.
• File Explorer exposes videos and any folder on the phone, removing artificial limits of a “recent” subset.
• A single Cross‑Device file broker (the Cross‑Device Experience Host + Link to Windows) is easier to secure, test and evolve than two different viewers that must remain consistent.

Those advantages are real for users whose workflows are file‑centric — photographers, editors, or anyone who transfers batches of media — but they come at a user‑experience cost for people who relied on Phone Link for fast, gallery‑style access.

---

UX trade‑offs: what users will gain and lose​

Gains (what File Explorer brings)​

• Full file‑management primitives: multi‑select, drag‑and‑drop between apps, copy/paste, rename and delete operations that behave like any other external storage device.
• Video support: File Explorer exposes videos stored on the phone and integrates them into Windows player and editing workflows.
• Integration with existing Windows tools: search, file tagging, indexing and third‑party gallery apps can operate on the mounted folders.
• Closer parity with wired workflows: the wireless mount behaves like MTP/USB drives for many tasks, eliminating the need for a cable in many scenarios.

Losses (what Phone Link’s gallery offered)​

• Aggregated “most recent” view: Phone Link presented screenshots, camera photos and app images in a single scrollable UI without forcing users to navigate folders — a convenience that File Explorer’s folder‑first model removes.
• Speed for quick grabs: the gallery was optimized for scanning recent content rapidly; File Explorer requires more navigation steps to find app‑specific or screenshot folders.
• Seamless Phone Link integration: past Phone Link workflows let users drag a photo from the gallery into a message or quick edit surface inside the same app; the redirect means some of those micro‑flows require an extra context switch.

The net effect depends on workflow: power users who move, rename and organize files will benefit; users who used Phone Link as a quick visual clipboard may feel the change as a regression.

---

How the File Explorer mount works (technical overview)​

• The Cross‑Device Experience Host on Windows exposes the paired phone as a virtual shell location, often visible under a CrossDevice path in the user profile folder or as a sidebar item in Explorer.
• File Explorer communicates with a local broker process that translates standard Explorer operations (list, read, write, rename) into remote calls to the Link to Windows service on the phone.
• The Link to Windows app on the phone must be granted file access permissions (storage or “all files access” depending on Android OEM). The phone and PC must be on the same network for initial pairing and many operations.

Important technical caveat: only one mobile device can be displayed in File Explorer at a time; toggling a second device to show in File Explorer will automatically disable the first. Also, File Explorer maintains a local CrossDevice cache folder under the user profile for performance; Microsoft documents how to clear that cache if you disable the feature.

---

How to switch today: step‑by‑step​

• Open Windows Settings → Bluetooth & devices → Mobile devices.
• Click Manage devices and confirm your phone is paired. If not, choose Add device and use the QR code flow.
• Toggle Show mobile device in File Explorer for the device you want to mount. File Explorer should then show the phone as a device under CrossDevice or in the sidebar.
• If you tap Phone Link’s Photos tile and see the “Photos is moving to File Explorer” banner, accept it and Phone Link will open the corresponding folder in File Explorer.

If the mount does not appear:

• Confirm the phone uses Android 11 or later and that the Link to Windows app is up to date. Microsoft’s support documentation lists minimum Link to Windows versions and Android baselines.
• Make sure both PC and phone are signed into the same Microsoft account and are on the same Wi‑Fi network.
• Disable aggressive battery optimizations on the phone (Link to Windows can be suspended by OEM power managers).
• Toggle the feature off and on, or remove and re‑pair the device if problems persist. Microsoft Q&A threads and community reports have common troubleshooting recipes.

---

Security, privacy and data‑management implications​

• Permissions: pairing asks for storage, notifications and other device permissions on the phone. Granting File Explorer access increases surface area: the PC can read and write to many phone folders. Audit permissions during pairing and only pair devices you trust.
• Local caching: File Explorer maintains a CrossDevice cache under your user profile for performance. If you enable the mount on a shared or managed PC, the CrossDevice cache can potentially leave local copies. Microsoft documents how to remove local copies by toggling the feature off and deleting the CrossDevice folder. Admins should include this in device‑handover procedures.
• Deletion semantics: deleting files from File Explorer may remove them from the phone. Microsoft notes a “Recycle bin – Connected device” on Android that can hold deleted items for up to 30 days in some configurations, but administrators and users should treat deletions as potentially permanent unless backups exist.
• Enterprise controls: for managed devices, administrators should determine whether to permit the File Explorer mount, document pairing/removal procedures, and update policies to avoid inadvertent data exposure on shared systems. The mount’s behavior (one phone visible at a time, cached files) has clear administrative implications.

---

Alternatives and workarounds if you prefer the old gallery experience​

• Keep using Phone Link while the gallery still appears on your device — some Windows installations and older Phone Link builds continue to show the in‑app gallery for now. Microsoft has not yet announced a firm removal schedule.
• Use cloud sync (OneDrive, Google Photos) to maintain a single cross‑device gallery that’s readily available in the Windows Photos app and web. This restores the “one place for everything” mental model while adding the benefits of cloud backup and indexing.
• Install a third‑party Windows gallery app that indexes the CrossDevice path and presents an aggregated, gallery‑first interface. Several gallery utilities can watch mounted drives and present a river‑style view of recent photos.
• For large‑scale library management, perform routine wired MTP transfers or use dedicated backup tools instead of relying on the wireless mount for mass operations. Wireless mounts are convenient for quick grabs and moderate transfers but wired MTP remains faster for full backups.

---

Troubleshooting: common gotchas and fixes​

• Toggle greyed out or not switching: confirm same Microsoft account on both devices, disable other paired phones or unpair extras, update Phone Link and Link to Windows, and re‑pair. Microsoft Q&A threads provide step‑by‑step checks for the most common failure modes.
• Missing screenshots or app images: look under DCIM/Camera, Pictures/Screenshots or app‑specific download folders. File Explorer exposes folder structure rather than the MediaStore‑based aggregated view Phone Link provided, so screenshots might live in separate directories.
• Local cache concerns on shared PCs: before returning a shared laptop, disable “Show mobile device in File Explorer” and delete the CrossDevice cache under C:\Users\<username>\CrossDevice to remove local copies. Microsoft documents these steps.

---

Product and community reaction — critical analysis​

This is a textbook consolidation decision: consolidate overlapping features to reduce engineering cost and focus on a single, more capable surface. The rationale is defensible: File Explorer was always the right place for bulk file operations and videos, and exposing phones as a mount helps many workflows behave like USB transfers without cables. Microsoft’s broader product trend — embedding device and AI actions into core system surfaces rather than maintaining parallel mini‑apps — aligns with this move.
But the change has trade‑offs that merit criticism:

• Phone Link’s gallery was not a niche convenience; for many users it was the fastest way to find recent screenshots and app images. Removing that single‑pane mental model forces folder navigation and can slow everyday workflows for social sharing, quick documentation, and other screenshot‑heavy tasks. This is a real usability regression for a specific but significant user cohort.
• Microsoft’s communication has so far been minimal: an in‑app banner and staged rollout messages but no public deprecation timetable. That leaves users and IT teams uncertain about how long they can rely on the old gallery or when to switch tools. Transparency on a hard removal date and enterprise controls would reduce friction.
• OEM variance and Android fragmentation mean the File Explorer mount will behave differently across phones. Microsoft’s documentation sets Android 11+ as the recommended baseline but implementation details depend on the phone’s OEM, Link to Windows version, and power‑management settings. That variability raises support complexity for help desks.

---

Practical recommendations (for everyday users and IT)​

• Update Phone Link, Link to Windows and the Cross‑Device Experience Host before switching workflows. Confirm Android version and permissions.
• If you rely on Phone Link’s gallery, set up cloud sync (OneDrive or Google Photos) now to preserve a single aggregated gallery experience on the PC. This also gives you a backup if the in‑app gallery is removed.
• For shared or corporate devices, document the CrossDevice cache removal process and decide policy for enabling the File Explorer mount. Train help‑desk staff on the one‑device limitation and pairing/clear steps.
• Test the File Explorer workflow for the most common tasks you perform (screenshot grabs, bulk transfers, video editing) and adjust habits or tooling accordingly — a small pilot will reveal whether you prefer the folder‑first approach or must preserve gallery‑first tools.

---

Conclusion​

Microsoft’s move to move photo viewing from Phone Link into File Explorer is a pragmatic engineering consolidation that prioritizes capability and maintainability over a curated convenience. For users who manage lots of media, File Explorer is the clear upgrade: more control, video access, and full file operations. For people who used Phone Link as an instant gallery and clipboard for recent captures, the change reduces immediacy and adds friction.
The transition is already visible as an in‑app banner and a redirect in Phone Link, and Microsoft’s support documentation explains the File Explorer pairing and requirements; however, there is no firm, public end‑of‑life date for the Phone Link Photos viewer yet, so users should prepare but can still choose the best interim workflow for their needs.

---

Source: Windows Report Microsoft is Moving Photos Viewing Out of Phone Link App to File Explorer

 

[ChatGPT]

Microsoft is quietly redirecting Phone Link’s built‑in photo gallery into File Explorer, replacing the app’s visual, recency‑sorted Photos tab with a banner that sends you to your phone’s storage inside File Explorer and urging users to “enjoy a better Photos experience” there.

Background​

Phone Link has been a cornerstone of Microsoft’s cross‑device strategy — a lightweight hub on Windows that brings calls, messages, notifications, app streaming and a compact photo viewer from a paired Android phone into the PC experience. Until now, Phone Link’s Photos tab gave users a single, aggregated view of recent images and screenshots without leaving the Phone Link interface.
Over the last year Microsoft also introduced direct access to a paired Android device from File Explorer, mounting the phone under a CrossDevice virtual location and exposing the phone’s folder tree (DCIM, Screenshots, Downloads, app folders) so files behave like normal removable storage. That File Explorer integration supports standard Windows file operations — multi‑select, copy/paste, drag‑and‑drop, rename and delete — and provides access to videos and deeper folders that Phone Link’s gallery did not consistently surface.
Now Microsoft is consolidating those two surfaces. Many users who open the Photos tab in Phone Link are seeing a one‑time alert telling them that “Photos is moving to File Explorer,” and in systems where the File Explorer mount is enabled, tapping the Photos tile redirects directly into the relevant folder in File Explorer. The rollout appears staged rather than instantaneous, and Microsoft has not published a formal deprecation date for the in‑app gallery.

---

Why the change matters​

This is not a mere UI tweak. It is a deliberate consolidation of two overlapping features into the operating system’s principal file manager. That decision has clear benefits, but it also trades away a particular kind of convenience.

What File Explorer brings (the upside)​

• Full folder access. File Explorer mounts let you browse your phone’s entire folder tree, not just a recent‑media snapshot. That means screenshots, app‑saved images, videos and hidden app folders become visible.
• True file operations. Multi‑select, copy/paste, drag‑and‑drop and standard context menus work naturally inside File Explorer. This is the easiest way to move dozens or hundreds of files between phone and PC.
• Video support. File Explorer exposes videos stored on the phone so you can open or transfer them without leaving the PC.
• Single management surface. Consolidating file tasks into File Explorer reduces duplicated code paths and the need to maintain two separate viewers with differing behaviors.
• Clear controls for local copies. File Explorer exposes how phone files are represented (local cache under a CrossDevice path), and there are documented steps to remove local copies if desired.

What Phone Link’s Photos tab offered (the downside)​

• Unified, quick gallery. Phone Link displayed a curated, recency‑sorted grid that pulled together camera photos, screenshots and app images into a single, gallery‑like view. That gave fast access to recent captures without traversing the phone’s directory structure.
• Simpler UI for casual use. For quick review and one‑off sharing, the gallery was faster and more approachable than switching to a folder view and locating the right subfolder.
• Less setup friction for some users. Not every user had File Explorer mobile mounting enabled; Phone Link’s gallery worked within the app once permissions were granted.

---

What Microsoft requires now (verified configuration and limits)​

To use the File Explorer integration reliably you must meet several preconditions on both PC and phone:

• Windows 11 on the PC with the relevant Cross‑Device host components and recent updates installed.
• An Android phone (recommended Android 11 or later for best compatibility).
• The Link to Windows component on the phone updated to a recent release.
• The phone and PC paired through Settings → Bluetooth & devices → Mobile devices → Manage devices.
• The Show mobile device in File Explorer toggle enabled for the paired device in Windows Settings.

There are a few operational limits to keep in mind:

• Only one mobile device can be shown in File Explorer at a time; enabling the toggle for one device will disable others.
• Phone Link continues to provide calls, messages, notifications and screen/app streaming; this change affects the Photos viewer specifically.
• Microsoft’s documentation makes clear that file operations translate to remote requests to the phone (a broker model), so actual file movement still depends on the phone’s permission model and the Link to Windows agent.

These details are implemented and documented in the Windows Settings and Cross‑Device feature set, and they reflect Microsoft’s stated design choices for centralizing file management under File Explorer.

---

Step‑by‑step: enable and use the File Explorer phone mount​

• Open Settings on your Windows 11 PC.
• Go to Bluetooth & devices → Mobile devices.
• Click Manage devices and confirm your phone is paired (or choose Add device and follow the QR code flow).
• Toggle Show mobile device in File Explorer for the phone you want to mount.
• Open File Explorer and look for your phone under the left navigation or under a CrossDevice location (the phone’s Camera folder is a common entry point).
• Use multi‑select, copy/paste or drag‑and‑drop as needed; you can also open video files directly from the mounted view.

If the phone does not appear in File Explorer, check that your phone and PC are signed in to the same Microsoft account, that the phone’s Link to Windows permissions are granted and not suspended by aggressive battery optimizations, and that both devices are on the same Wi‑Fi network. Re‑pairing the device or updating the Link to Windows and the Cross‑Device host on Windows often fixes intermittent issues.

---

Common problems and troubleshooting​

• Toggle greyed out or won’t enable:
• Confirm the phone meets the Android baseline and that Link to Windows is updated.
• Ensure only one phone is being shown in File Explorer; turn off other devices if necessary.
• Verify both devices are signed into the same Microsoft account.
• Check that the Connected Devices Platform Service is running and that firewall settings aren’t blocking Phone Link.
• Files missing or gallery not matching phone:
• Phone Link’s former gallery used MediaStore queries to present a curated recent set; File Explorer shows the actual folder tree. Expect folder‑based navigation differences.
• If the File Explorer mount shows a folder but it appears empty, check Link to Windows permissions on the phone and disable any aggressive battery manager or storage permission restrictions.
• Local copies and cleanup:
• Windows stores local cached phone files under a CrossDevice path on the PC. There are documented steps to remove local copies without deleting originals on the phone; the recommended sequence is to toggle off Show mobile device in File Explorer and then delete the cached CrossDevice folder content.

---

Practical effects for everyday users​

For power users and people who move lots of files between phone and PC, this change is a clear net positive: File Explorer handles bulk operations far better than an in‑app gallery, and the ability to access video files and deeper folders removes long‑standing limitations.
For casual users, however, there’s a behavioral shift. The Phone Link Photos tab was optimized for simple, immediate access to recently captured images. Replacing that with a folder‑centric workflow demands a little more knowledge about where different kinds of images live on the phone (Camera vs. Screenshots vs. app folders) and adds an extra click to the task flow.
File Explorer is more powerful but less tailored. That means users who relied on the quick, aggregated view will need to adapt or rely on cloud‑sync services that already provide a unified timeline (for example, OneDrive or Google Photos).

---

Enterprise and admin considerations​

IT administrators should note the following when managing fleets:

• The File Explorer integration creates a mounted view that exposes device file systems to Windows. Organizations worried about data leakage should revisit endpoint policies, conditional access, and device‑pairing rules.
• Because only one phone can be shown at a time and because CrossDevice uses local caching, admins should test whether local copies could conflict with data retention or backup policies.
• The staged rollout and lack of a publicly declared deprecation timeline mean admins should prepare for both possibilities: a permanent removal of the in‑app gallery or a long‑term redirect to File Explorer. Validate workflows that relied on Phone Link’s gallery (for example, helpdesk scripts that asked users to retrieve recent screenshots from the app).
• Troubleshooting scripts should include checks for Link to Windows versions, the Cross‑Device Experience Host, and the Show mobile device in File Explorer setting.

---

Privacy and data‑handling implications​

Consolidation into File Explorer changes the signal‑to‑noise of where mobile files live on a PC:

• Local caches: When a phone is mounted, Windows may create or cache items under a CrossDevice path. Those cached files can be removed without affecting the originals on the phone, but users should be aware of where these local copies reside and how to clear them.
• Recycle bin for connected devices: Deleted items from a mounted mobile device may be recoverable from a “Connected device” recycle bin for a limited retention window. If you are concerned about sensitive images persisting on the PC after deletion, follow the documented cleanup steps for safe removal.
• Permissions: The Link to Windows flow still requires explicit permission on the phone to share files. Make sure to confirm or revoke those permissions on the phone if you no longer want your PC accessing mobile files.
• Shared devices: On shared PCs, enable or restrict the mobile device mount appropriately; only one mobile device can appear at a time and toggling is controlled at the Windows user level.

---

Why Microsoft might have made this choice​

From an engineering and product management perspective, the consolidation makes sense:

• Avoid duplicate UX and maintenance costs. Maintaining a separate gallery, a file mount, and the synchronization layer between them multiplies complexity.
• Leverage existing file infrastructure. File Explorer already provides robust APIs and behaviors for file operations; reusing that surface avoids reinventing basic capabilities.
• Make file actions consistent. Users moving files expect Windows file semantics; File Explorer offers predictable, discoverable behaviors.

From a user experience perspective, though, Microsoft traded the convenience of an aggregated gallery for a more powerful but less curated experience. That trade‑off favors users who value complete control and heavy file operations over those who preferred the at‑a‑glance simplicity of Phone Link’s Photos grid.

---

Alternatives and workarounds​

If you prefer the old gallery behavior, consider these options:

• Keep using Phone Link while it remains available on your system. If your device has not yet received the redirect banner, you can continue to use the gallery, but treat that as a temporary state.
• Use cloud sync: OneDrive and Google Photos both provide an aggregated timeline of photos and videos and are often the closest match to the Phone Link gallery across devices.
• Third‑party gallery apps on Windows that index mounted phone folders can recreate a gallery‑style view while retaining the File Explorer mounting benefits.
• Create saved searches or library views in File Explorer that point at common folders (DCIM, Screenshots) for faster access to aggregated items.

---

What we tested and what remains unverified​

Independent reporting and user testing have confirmed the presence of the in‑app banner and the redirect behavior on a range of Insider and production builds. Microsoft’s configuration pages describe the necessary toggles and the CrossDevice mount behavior.
A few technical specifics circulating in community posts — such as precise limits on how many recent images Phone Link’s gallery historically served (commonly mentioned as around 2,000 images) — are anecdotal and not published as hard limits in official documentation. Treat such figures as user observations rather than formal constraints.
Also, while the staged rollout is visible in many reports, Microsoft has not published a formal timeline or a one‑line deprecation notice that states an exact removal date for the Phone Link Photos viewer. Until Microsoft issues an explicit deprecation timetable, assume the change is active in a rolling fashion and that it may become permanent.

---

Practical recommendations (what users should do today)​

• Update: Ensure Windows 11, the Cross‑Device Experience host and Link to Windows are up to date on both PC and phone.
• Enable File Explorer mounting: Go to Settings → Bluetooth & devices → Mobile devices → Manage devices and turn on Show mobile device in File Explorer for your preferred phone.
• Test critical workflows: If you routinely grab screenshots or camera images for company processes, run a quick test to confirm the folder path and behavior you’ll use going forward.
• Reassess backups and cleanup: If you worry about local cached copies, follow the documented cleanup steps (disable the mount and remove CrossDevice cached content) to purge local files.
• Consider cloud sync for a gallery view: If you miss the aggregated gallery, cloud services provide a stable, cross‑device timeline that is independent of Phone Link or File Explorer behavior.
• For admins: Update helpdesk documentation, add checks for the mount toggle in troubleshooting flows, and communicate the change to users who might be surprised by the new redirect.

---

Final analysis: consolidation for capability, at the cost of convenience​

This change is emblematic of a platform trade‑off: Microsoft is moving photo management to the canonical file surface where operations are richer and more consistent, but in doing so it is taking away a focused, time‑saving gallery that many users found handy for quick tasks.
For users who regularly transfer batches of images and videos, the consolidation will feel like an upgrade. For those who used Phone Link as a lightweight preview and quick sharing tool, the transition will feel like a loss of convenience — albeit one that can be mitigated through OneDrive, a Windows gallery app, or third‑party tools.
Because the change is rolling and there’s no official removal date, the practical approach is to prepare for File Explorer as the primary surface for mobile media management: enable the mount, familiarize yourself with the CrossDevice paths and file‑cleanup steps, and adjust workflows that depended on Phone Link’s single‑pane gallery. At the same time, treat community claims about specific performance limits or undocumented behaviors cautiously until Microsoft publishes formal release notes or guidance.
The consolidation simplifies Microsoft’s cross‑device architecture and empowers file management, but it also underscores a recurring reality: convenience features can vanish quietly when the platform chooses consistency and scale. Users should adapt proactively — and keep an eye on updates, because Microsoft’s staged rollout could evolve further.

---

Source: XDA Windows 11's Phone Link is about to lose a handy feature