Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
Microsoft admits Cross Device Service bug is causing high CPU usage on Windows 11 PCs
The company is likely to roll out a fix to tackle this issue
3 min. read
Published onJune 17, 2024
published onJune 17, 2024
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
After multiple user complaints, Microsoft has finally acknowledged that the Cross Device Service bug is the main culprit behind the high CPU usage.
The news comes via Neowin whichreportedthat Windows Insiders and users have been investigating this issue using the Task Manager after they suspected something is wrong with their system.
Microsoft Cross Device Service blamed for high CPU usage in Windows 11 PCs
On June 5, 2024, Microsoft Community Form user,leginmat90,first reported this bug. The user posted:
Noticed this began a few days ago. Initially, it was my CPU fan running unusually high, and also noted high idle temps. The task manager then shows Cross Device Service running my CPU at 7-10% continuously. As soon as I terminate this program, my CPU returns to normal idle conditions.
How do I disable this feature?
This post has garnered forty-eight upvotes, which also means that the issue is not limited to a user. It is possible that thebug might have emerged from the recently added improvementsto Windows 11’s Cross Device Service.
If you aren’t aware, the service allows your PC to sync with your smartphone for file and media sharing. Although many associated the issue with thePhone Link feature, we can’t rule out the possibility of older changes made to Cross Device Service within a year being the real culprit.
The good news is Microsoft finally came forward to address the Cross Device Service bug. Microsoft Engineer Jennifer G replied to the post and said:Appreciate your patience, we’ve identified the cause and are working on a fix.
It is worth noting that the response on the Feedback Hub was posted a week ago, but we still await the fix. Having gone through theRecall blunderlately, we expect Microsoft to act fast to resolve any issue that comes their way.
Disabling the feature could resolve this issue
Asleginmat90noted, terminating the program brings the CPU to normal. The user even asked for help through the post to disable the feature altogether. If you are also facing a similar issue you can try disabling the feature.
We have mentioned the steps to disable Microsoft Cross Device Service as suggested by Community Forum user,ViniciusMU.
It will be interesting to see when Microsoft rolls out the fix for the reported Cross Device Service bug. Not to forget, in March, the then newly announced Cross Device Experience Hostwas reported to have multiple bugs.
Did disabling Microsoft Cross Device Service help you resolve the issue? Please share your thoughts with our readers by commenting below.
More about the topics:Windows 11
Vlad Turiceanu
Windows Editor
Passionate about technology,Windows, and everything that has a power button, he spent most of his time developing new skills and learning more about the tech world.
Coming from a solid background in PC building and software development, with a complete expertise in touch-based devices, he is constantly keeping an eye out for the latest and greatest!
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Vlad Turiceanu
Windows Editor
Coming from a solid background in PC building and software development, he’s a Windows 11 Privacy & Security expert.
