# CrossDeviceService.exe

Windows Process: Microsoft Corporation

Catalog search terms crossdeviceservice, cross device service, cross device experience

Windows, System Component

Cross Device Experience Host service process. E dey keep Phone Link and nearby-sharing contract dem alive. CrossDeviceResume.exe na the continue-on-PC helper.

## Wetin you need know

This na the cross-device contract host, no be the Phone Link window.

CrossDeviceService.exe dey back Cross Device Experience. PhoneExperienceHost.exe na the Phone Link UI. CrossDeviceResume.exe na resume. To end the service go pause those contract dem until Windows start am again.

- **E safe?**: Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.

  **Same thing as Phone Link?**: Phone Link UI na PhoneExperienceHost

  **I suppose end am?**: Cross-device feature dem go pause

Feex tok say

If I no dey use phone or nearby sharing, I go turn those setting dem off. To end CrossDeviceService every hour no be setting.

## Wetin be CrossDeviceService.exe?

CrossDeviceService.exe na the Cross Device Experience service host inside Windows SystemApp package.

## Wetin e dey do?

E dey hold longer-running cross-device contract dem so Phone Link and related feature dem fit connect. E no dey draw the Phone Link window.

## Wetin make am dey run?

Cross-device or Phone Link feature dem dey enabled. PC wey get those off suppose show this one less often.

## Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

`Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'CrossDeviceService.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List`

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the [file-identity guide](https://feex.it/wiki/l/pcm/software/system/verify-executable-path-signature/) to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

## E dey safe?

Check dis running file

The Microsoft CrossDevice package na wetin we expect. CrossDeviceService.exe inside Temp no be am.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

`C:\Windows\SystemApps\MicrosoftWindows.CrossDevice_*\CrossDeviceService.exe`

- Contract host
- UI: PhoneExperienceHost.exe
- Resume: CrossDeviceResume.exe

## I fit end am?

E dey pause cross-device feature dem

To end am go drop connection dem until the package start am again. Turn the feature dem off inside Settings for permanent change.

## I fit comot am?

No

No delete the CrossDevice package. Disable Phone Link and nearby sharing instead.

## E suppose start with Windows?

The feature dey start am. No be chat Startup app.

## Measure resource use

| CPU and memory   | Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)               |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Disk and network | Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm) |

## File information

| Executable name            | CrossDeviceService.exe                                                             |
| -------------------------- | ---------------------------------------------------------------------------------- |
| Recorded installation path | C:\Windows\SystemApps\MicrosoftWindows.CrossDevice\_\*\CrossDeviceService.exe      |
| Publisher                  | Microsoft Corporation                                                              |
| Signature check            | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |

## Common wahala dem

### Service without phone

Nearby sharing and Microsoft account device graph fit still start am.

### Three Cross Device name dem

Service, Resume, and PhoneExperienceHost na different work.

## How to troubleshoot

Diagnose before you change anything wey fit scatter things.

### Settings > Bluetooth & devices > Mobile devices

The Phone Link switch.

### Turn nearby sharing off as second test

That contract fit keep this host awake.

## Technical details

Technical details

| Image name | CrossDeviceService.exe       |
| ---------- | ---------------------------- |
| Role       | Cross Device Experience host |

## Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

## Related

Dis entities connect to dis article. Type dey show for every link.

[CrossDeviceResume.exe: Windows Process](https://feex.it/wiki/l/pcm/process/crossdeviceresume.exe/)[PhoneExperienceHost.exe: Windows Process](https://feex.it/wiki/l/pcm/process/phoneexperiencehost.exe/)[YourPhoneAppProxy.exe: Windows Process](https://feex.it/wiki/l/pcm/process/yourphoneappproxy.exe/)[Check an executable path and digital signature: Guide](https://feex.it/wiki/l/pcm/software/system/verify-executable-path-signature/)[Read Task Manager and compare process activity: Guide](https://feex.it/wiki/l/pcm/software/system/how-to-read-task-manager/)[Windows processes: Category](https://feex.it/wiki/process/windows/)

## Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. [How we dey do research](https://feex.it/wiki/research/).

- [Microsoft Support: Phone Link ](https://support.microsoft.com/windows/phone-link)· Cross-device feature dem
- [Microsoft Learn: nearby sharing ](https://learn.microsoft.com/windows/uwp/launch-resume/nearby-sharing)· Nearby sharing contract dem
- [Foxhole process map ](https://foxhole.feex.it/)· First-party samples on top Windows PCs. No be lab benchmark.
- [Microsoft Sysinternals: Sigcheck ](https://learn.microsoft.com/en-us/sysinternals/downloads/sigcheck)· Dey explain how to check file signatures. Dis reference no establish the identity or safety of any particular running file.
- [Microsoft: Get-CimInstance ](https://learn.microsoft.com/en-us/powershell/module/cimcmdlets/get-ciminstance)· Read-only local process-query method. (pcm)
- [Microsoft: Win32_Process properties ](https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-process)· Documents process IDs, executable paths, creation dates and parent-ID reuse. (pcm)

## Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Quick facts

The short identity of dis page. Specs, sources, and the full story still dey inside the article.

- **Type**: Windows Process

  **Publisher**: Microsoft Corporation

  **Executable**: CrossDeviceService.exe

  **Typical path**: C:\Windows\SystemApps\MicrosoftWindows.CrossDevice\_\*\CrossDeviceService.exe

  **Record context**: Feex Wiki reference entry

Recorded source status: Feex Reviewed: Recorded source label: August 2026. Dis label no establish independent verification.

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/l/pcm/process/crossdeviceservice.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)