When certain background tasks lead to high CPU usage on a PC, it typically means that the workload is buggy, which is what leads to its misbehavior. Often, certain Windows processes or services can be the culprit too.
This month, Windows users and insiders have been noticing something off on their systems. Digging into the issue with the help of handy ol’ Task Manager has revealed that Microsoft Cross Device Service is the potential culprit exhibiting high CPU usage.
Community Reports and Feedback
These reports were not few and far between, as multiple users have confirmed the issue. Here’s a thread on the Microsoft forum started by user leginmat90, which has been upvoted by 46 others at the time of writing. Here’s another one on the Windows Eleven forum.
The issue has also been reported to Feedback Hub by a user, and at the time of writing, it has been acknowledged by 160 others:
Cross Device Service is suddenly using an unexpected amount of CPU in the latest Windows 11 Insider builds (starting early June 2024)
Microsoft's Response
Microsoft engineer Jennifer G has responded to this issue, confirming it and adding that the company is looking into a resolution:
Appreciate your patience, we’ve identified the cause and are working on a fix
The response was posted a week ago, though we are yet to receive the fix.
The Role of Cross Device Service
The Cross Device Service, as the name suggests, is what helps a Windows PC connect to, synchronize, and share files with devices like phones. It essentially helps power Phone Link in Windows. The recent Windows 11 Beta Insider builds are testing features related to better Phone Link support, and it’s possible that the bug slipped through.
The most recent build brings improved Android file sharing, and another one from back in February updated the Cross Device Experience Host, which replaced remote capture.
As users await a fix, it's clear that the high CPU usage linked to Microsoft Cross Device Service has caught significant attention within the community. With Microsoft's acknowledgment and ongoing efforts to resolve the issue, users can hope for a smoother experience in future updates.
Comments (0)