PhoneExperienceHost.exe high CPU usually means Microsoft Phone Link is stuck in a sync, notification, call, or reconnect loop—not that the genuine process is a virus. Confirm that it belongs to the Microsoft Phone Link package, then measure whether CPU, memory, or handle count keeps growing. Update both Phone Link and Link to Windows, test the feature that triggers the load, and use Repair before Reset. Disable background activity or unlink the phone only if you accept losing desktop calls, messages, photos, notifications, and other cross-device features. Treat the process as suspicious when its path or signature does not match the installed Microsoft package.
What Is PhoneExperienceHost.exe?
PhoneExperienceHost.exe is the main Windows process behind Microsoft Phone Link, formerly called Your Phone. It supports communication between the PC and a linked Android phone or iPhone, including notifications, messages, recent photos, calls, and other features that vary by device.
The packaged file normally sits in a versioned folder below C:\Program Files\WindowsApps\Microsoft.YourPhone_..._8wekyb3d8bbwe\ and has a valid Microsoft signature. The exact version string changes when the app updates. Do not compare only the filename, and do not download a replacement executable from a file-library site.
| What you see | Most useful next action |
|---|---|
| Brief CPU spike after sign-in, resume, or phone reconnect | Wait for synchronization to finish; this can be normal |
| CPU rises only while the PC is idle | Test notification and device-sync features, then update Phone Link |
| Memory rises but later stabilizes | Observe before resetting; a large working set is not automatically a leak |
| Handle count climbs continuously | Record the growth, restart Phone Link, then Repair or Reset it |
| Recurring PhoneExperienceHost.exe application errors | Update, terminate once, Repair, then Reset or relink |
| Executable runs from Temp, AppData, Downloads, or an unrelated folder | Verify the signature and scan for a lookalike plus persistence |
Measure CPU, Memory, and Handles Separately
A single Task Manager snapshot can point to the wrong repair. CPU shows current work; memory shows the process working set; handles are references to files, registry keys, events, windows, and other Windows objects. A high but stable value is different from a count that continues rising while nothing changes.
- Open Task Manager, select Details, and find
PhoneExperienceHost.exe. - Right-click a column heading, choose Select columns, and enable Handles.
- Record CPU, Memory, and Handles. Check again after five to ten minutes and after the PC enters the state that normally triggers the problem.
- Note whether the change begins after a notification burst, phone reconnect, Bluetooth call, photo refresh, message sync, screen-off idle period, or resume from sleep.
Microsoft has not published one universal handle threshold or root cause for every Phone Link build. The useful evidence is continuous growth on your system, especially when it stops after Phone Link is terminated and returns after the same feature is enabled.
An elevated PowerShell window can capture the active path, CPU time, working set, and handle count without installing another utility:
Get-Process PhoneExperienceHost -ErrorAction SilentlyContinue | Select-Object Id, CPU, WorkingSet64, Handles, Path
Get-AuthenticodeSignature (Get-Process PhoneExperienceHost).Path | Select-Object Status, SignerCertificate
If Task Manager itself wakes the PC and the CPU immediately falls, compare total CPU time before and after an idle interval or use the command above immediately after the symptom. Do not assume the drop proves malware is hiding; the exact idle-only behavior has also been reported for Phone Link bugs and notification loops.
Find the Phone Link Feature Triggering the Loop
Test one feature at a time so you know what fixed the problem. Phone Link can synchronize several independent streams, and turning everything off at once loses the useful evidence.
- Update both sides. In Phone Link, open Settings and check the app version or available update. Update Link to Windows on the phone as well, then restart both devices.
- Restart the connection. Close Phone Link from its system-tray menu, end
PhoneExperienceHost.exeonce in Task Manager, and reopen the app. Windows can restart the process when the app needs it. - Test notifications. In Phone Link, turn notification syncing off temporarily. If CPU or handles stabilize, re-enable it and limit which phone apps may send notifications to the PC.
- Test calls and Bluetooth. If the load begins during or after calls, toggle Bluetooth off and on, reconnect the phone, and test without other Bluetooth audio devices.
- Test messages, photos, and cross-device features. Pause only the feature that correlates with the rise. A large photo refresh or reconnect can cause brief work; continuous growth is the problem.
Microsoft’s current troubleshooting guidance also emphasizes matching Microsoft accounts, current app versions, network connectivity, phone permissions, and battery settings. Do not disable phone battery optimization blindly: it can improve background syncing, but it may also increase activity. Change it only when a feature fails to sync and monitor the result.
Repair, Reset, or Relink Phone Link
Use the least disruptive step that matches the symptom:
- Repair. Open Windows Settings and search for Phone Link under Installed apps or System components, depending on the Windows build. Open Advanced options and choose Repair. This attempts to fix the app without clearing its data.
- Reset. If Repair does not stop the loop, choose Reset. This clears the app data on the PC, so expect to sign in and configure the link again.
- Unlink and relink. For persistent connection loops, remove the device from Phone Link and the Microsoft account device page, sign out of Link to Windows on the phone, restart both devices, and pair them again.
- Report a repeatable leak or crash. If the latest version still adds handles continuously or crashes after the same action, use Phone Link’s Feedback & Community option. Include the app version, Windows build, trigger, and before/after counts.
Resetting or relinking is not a security requirement when the only symptom is high CPU. It is an app-state repair. Back up any information you need from the phone itself; Phone Link is a synchronized view, not the authoritative backup for messages, photos, or account data.
Can You Disable PhoneExperienceHost.exe?
You can end the process temporarily, stop Phone Link from starting automatically, disable its background permission where Windows exposes that option, or unlink the device. These choices can stop the resource use, but they also stop or delay Phone Link features.
- Disabling startup prevents Phone Link from opening automatically after sign-in.
- Restricting background activity can delay notifications, messages, calls, and reconnect behavior.
- Unlinking removes the phone-to-PC relationship until you pair it again.
- Uninstalling, where the current Windows build offers it, removes the app experience rather than repairing the underlying sync state.
Do not rename, delete, or block the executable inside WindowsApps. Package updates may restore it, and manual changes inside that protected directory can create new app errors. Use Windows app controls so the change is reversible.
Fix Recurring PhoneExperienceHost.exe Crashes
If Windows reports that PhoneExperienceHost.exe stopped working, open Reliability Monitor and look for the matching failure time. Record the Phone Link version and faulting module, then follow the same update, Repair, Reset, and relink order. A crash after an app update does not justify downloading a DLL or older executable from an unofficial site.
If several Microsoft Store or packaged apps crash—not only Phone Link—install pending Windows updates and restart before changing Phone Link again. A Phone Link-only crash is more likely to be fixed through its app controls; a system-wide packaged-app problem needs broader Windows troubleshooting.
Is PhoneExperienceHost.exe a Virus?
The Microsoft-signed Phone Link package is legitimate. A familiar process name does not authenticate every file with that name. Right-click the process in Task Manager, choose Open file location, and check Properties > Digital Signatures. Use the executable safety checklist when the path or signer is unclear.
Escalate to a security response when the file runs from Temp, AppData, Downloads, a user-created folder, or an unknown startup location; lacks a valid Microsoft signature; returns after deletion; or appears with unrelated browser changes, credential prompts, remote-access activity, or security warnings. Review suspicious startup entries rather than deleting only the visible process.
Malware can abuse data exposed through legitimate cross-device features, but that is different from Phone Link itself being malware. The separate CloudZ Phone Link abuse report explains one such threat model. High CPU by itself does not establish that scenario.
If a wrong-path copy already ran, a security tool may quarantine the visible file while a scheduled task, startup value, loader, or bundled module remains and recreates it. Run a full Gridinsoft Anti-Malware scan through the official download path, remove confirmed detections, reboot, and scan again if the process returns. A clean scan cannot restore exposed passwords or prove that no account data was accessed.
If the process path is wrong, the name imitates a Windows component, or high CPU started after an unknown installer, scan for hidden miners, services, startup entries, and bundled components.
Download Gridinsoft Anti-MalwareFAQ
Why does PhoneExperienceHost.exe use CPU only when my PC is idle?
Phone Link may enter a background notification, reconnect, or synchronization loop after the screen turns off. Test notification syncing and other Phone Link features one at a time, update both apps, and use Repair if the pattern returns.
How many handles are too many for PhoneExperienceHost.exe?
There is no official universal limit. Focus on whether the count rises continuously over several measurements, stops when Phone Link is restarted, and returns after the same feature or idle state.
Is it safe to end PhoneExperienceHost.exe?
Ending it once is a reasonable diagnostic step. Calls, messages, photos, notifications, and device syncing can pause, and Windows may start the process again when Phone Link reopens.
Will resetting Phone Link delete data from my phone?
Resetting the Windows app clears its local app state and requires setup again. It should not erase the original messages or photos stored on the phone, but Phone Link should not be treated as a backup.
Should I remove Phone Link if I do not use it?
You can disable startup, restrict background activity, unlink the phone, or uninstall the app where Windows offers that option. Use Settings rather than deleting files from WindowsApps.
References
- Microsoft. Troubleshooting the Phone Link. Microsoft Support, current living documentation. Accessed August 18, 2026.
- Microsoft. Reset your Android device and PC with the Phone Link. Microsoft Support, current living documentation. Accessed August 18, 2026.
- Microsoft Q&A community. PhoneExperienceHost.exe high CPU usage when PC idle. Microsoft Learn, opened November 12, 2022. Accessed August 18, 2026. Community symptom evidence; not an official root-cause finding.
