Windows 11 users have been dealing with a silent system drain since at least 2023: the Cross Device Service, a core component of Microsoft’s Phone Link functionality, is gobbling up staggering amounts of memory. On affected machines, the background process can swell to 15 GB, 20 GB, or even 30 GB of RAM, leaving systems sluggish and unresponsive. Despite hundreds of complaints on forums, Reddit, and the Feedback Hub, Microsoft has yet to issue a definitive fix.

What’s actually happening

The culprit is a system service called CrossDeviceService, which appears in Task Manager as crossdeviceservice.exe. This service handles the communication pipeline between your Windows 11 PC and your Android phone (or iPhone, with some limitations) through the built‑in Phone Link app. It synchronizes notifications, messages, photos, and even enables you to make and receive calls from your desktop.

But under certain conditions, the service begins to leak memory—rapidly. Users report that after a fresh boot, the service sits at a modest 100–200 MB. Within hours or days, however, its RAM footprint balloons. Threads on the Microsoft Community and Reddit describe systems where crossdeviceservice.exe consumes 15 GB, 20 GB, and sometimes as much as 30 GB of memory. The leak does not depend on heavy phone‑to‑PC activity; it can happen even when the Phone Link app is idle or minimized.

The problem first gained widespread attention in early 2023, coinciding with the rollout of Windows 11 22H2 “Moment” updates. Reports have continued to surface with Windows 11 23H2, and early adopters of Windows 11 24H2 are also complaining of similar behavior. There is no evidence that a specific cumulative update or KB patch introduced the bug—it appears to be an inherent flaw in the service’s memory management that may have been latent from its inception.

Microsoft has not officially acknowledged the issue in any release notes or advisory. Searches of the Windows Health Dashboard show no mention of a memory leak tied to Cross Device Service. The company’s typical response on community forums is to suggest standard troubleshooting—uninstalling and reinstalling Phone Link, running the System File Checker, or performing a clean boot—but these rarely resolve the underlying leak.

What it means for your daily workflow

For the average home user, the symptom is unmistakable: a PC that gradually gets slower until everything lags. Opening apps takes longer, switching between windows stutters, and even the cursor may hesitate. Often, users only discover the source when they open Task Manager and sort processes by memory usage—only to find crossdeviceservice.exe sitting at the top, dwarfing everything else.

The impact is especially harsh on laptops with 8 GB or 16 GB of RAM. At 30 GB, the service can completely choke a 16 GB machine, forcing Windows to aggressively page memory to disk, which drags everything to a crawl. Even on 32 GB systems, a 20 GB leak will cause noticeable slowdowns and elevate fan noise as the CPU works harder to juggle memory.

For power users and IT administrators, the leak represents more than a nuisance. It undermines the very concept of a modern “connected” Windows experience that Microsoft has been pushing. A service intended to make you more productive—by letting you handle calls and texts from your keyboard—instead becomes the reason you have to restart your PC every day. In enterprise environments where devices are locked down, diagnosing and shutting down the service can be tricky, and the performance degradation might be misdiagnosed as endpoint malware or a failing hard drive.

Developers and those running virtual machines or memory‑intensive applications (video editors, 3D modelers, data analysts) face outright workflow interruptions. A VM that suddenly runs out of allocated RAM because the host has been secretly drained by crossdeviceservice.exe can lose work or corrupt data.

Phone Link is not a new application. It debuted as “Your Phone” in Windows 10 back in 2018, offering basic photo and SMS sync. Over the years, Microsoft has layered on features: notification mirroring, the ability to run Android apps on the PC, and, more recently, Bluetooth‑based calling for iPhones. With Windows 11, Microsoft integrated the functionality more deeply, rebranding it as Phone Link and introducing a new background infrastructure to power all the inter‑device communication.

The Cross Device Service (crossdeviceservice.exe) is the engine behind that integration. It maintains persistent connections via Wi‑Fi or Bluetooth, listens for incoming notifications, and brokers data between the phone and the Windows shell. It was introduced as part of the Windows 11 22H2 feature update, and its importance grew with each subsequent “Moment” release that added more cross‑device capabilities.

Regrettably, memory leaks in system‑level Windows services are not unprecedented. Windows Search indexer has been known to misbehave, as have certain Defender components and even the audio service. What sets the Cross Device Service leak apart is its sheer scale—few system processes have ever been documented to quietly steal 30 GB of RAM. Moreover, because the service is tied to an app that many users rarely configure or even open, the leak can go undetected for days until performance tanks.

Microsoft’s silence on the matter is puzzling. The company has been actively promoting the “Windows‑Android ecosystem” and counts Phone Link as a key differentiator from macOS. Allowing such a glaring flaw to persist for over two years undermines the reliability users expect from a first‑party service. It’s possible that the bug is not universal—it may be triggered only when certain phone models or specific Bluetooth/Wi‑Fi configurations are involved—but that hasn’t stopped the steady stream of complaints.

What you can do right now

Until Microsoft delivers an official patch, the only reliable remedy is to disable or aggressively manage the Cross Device Service. Here are your options, from simplest to most drastic.

Option 1: Stop the service when you notice the leak

Open Task Manager (Ctrl+Shift+Esc), switch to the Details tab, find crossdeviceservice.exe, right‑click it, and choose “End task.” The service will restart automatically at the next reboot, but this buys you a few hours or days of normal‑speed computing.

Option 2: Use PowerShell to stop and disable the service

Run the following commands in an elevated PowerShell window:

Get-Service CrossDeviceService | Stop-Service -Force
Set-Service CrossDeviceService -StartupType Disabled

This stops the service immediately and prevents it from starting again when you restart your PC. Note that doing this will break all Phone Link functionality—your notifications, messages, and calls will no longer sync.

Option 3: Disable via the Services console

  1. Press Win+R, type services.msc, and hit Enter.
  2. Scroll down to “Cross Device Service.”
  3. Right‑click it, select “Properties,” and change the “Startup type” to “Disabled.”
  4. Click “Stop” if the service is running, then “OK.”

Option 4: Tweak the registry

For group policy or scripting, you can also set

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CrossDeviceService\Start

to 4 (Disabled). Be careful when editing the registry; make a backup first.

If you never use Phone Link, you can remove it via Settings → Apps → Installed apps, though note that the background service might still linger. For a complete removal, third‑party tools like O&O App Buster can strip out the underlying service, but only do so if you’re comfortable with advanced system tweaks.

Option 6: Use a script to periodically check and kill the service

For those who want to keep Phone Link but hate the unpredictable slowdowns, a scheduled task or a small PowerShell script can monitor crossdeviceservice.exe working set and kill it once it exceeds a threshold (e.g., 2 GB). An example script:

$proc = Get-Process crossdeviceservice -ErrorAction SilentlyContinue
if ($proc -and $proc.WorkingSet64 -gt 2GB) {
    $proc.Kill()
    Write-EventLog -LogName Application -Source "PSMonitor" -EventID 1001 -EntryType Warning -Message "CrossDeviceService exceeded 2 GB RAM. Killed."
}

Schedule it to run every 30 minutes via Task Scheduler.

Option 7: Provide feedback to Microsoft

Open the Feedback Hub app, search for “Cross Device Service memory,” and upvote existing reports. The more telemetry Microsoft receives, the faster it may prioritize a fix.

What to watch for next

Microsoft’s development cadence for Windows 11 is relentless, with new builds shipping almost every week in the Insider channels. There is a chance that a refactored Cross Device Service is already baking in the Dev or Canary channels, using a more robust inter‑process communication model. Users running the latest 24H2 preview builds have reported mixed results: some say the leak is gone, others claim it’s merely reduced. Without public confirmation, though, it’s impossible to know if a fix is imminent.

With Windows 12 rumors swirling and Microsoft’s continued push for AI‑powered “Copilot+” PCs, the expectation is that cross‑device integration will only deepen. That makes it all the more critical for Microsoft to nip this reliability issue in the bud. For now, if your system starts feeling inexplicably slow, open Task Manager—it might just be Phone Link silently feasting on your memory.