DataExchangeHost.exe
Catalog search terms dataexchangehost, data exchange host
Data Exchange Host. E dey help clipboard and drag-and-drop between apps, including some packaged apps and the desktop.
Wetin you need know
This one dey broker data between apps. E no be RuntimeBroker.exe (capabilities) and e no be the clipboard history UI.
DataExchangeHost.exe na Windows data-exchange broker. You dey see am during share or drag operations. If you end am when drag dey go on, wetin you dey move fit lost.
- E safe?
- Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
- Wetin make am dey here?
- Share, drop, or clipboard hand-off
- I suppose end am?
- The thing wey you dey drop fit fail
Wetin be DataExchangeHost.exe?
DataExchangeHost.exe na the Windows Data Exchange Host inside System32.
Wetin e dey do?
E dey move shared payloads between callers make packaged app and desktop app fit exchange files or text. E no dey store clipboard history. That one na different feature entirely.
Wetin make am dey run?
Share charm, drag action, or interop API na wetin start am. Quiet copy fit linger small after you don drop am.
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 'DataExchangeHost.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 to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)
E dey safe?
Check dis running file
System32 DataExchangeHost na from Microsoft. The same name inside packer folder no be Microsoft.
Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)
C:\Windows\System32\DataExchangeHost.exe
- Share / drag broker
- No be RuntimeBroker.exe
- No be TextInputHost clipboard UI
I fit end am?
Fit make the drop fail
If you end am when transfer dey go on, e fit cancel the share. After the drop, you fit end any leftover copy if e hang.
I fit comot am?
No
No delete DataExchangeHost.exe. Interop between Store and desktop apps go worse.
E suppose start with Windows?
E dey open when need dey. No be Startup Apps.
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 | DataExchangeHost.exe |
|---|---|
| Recorded installation path | C:\Windows\System32\DataExchangeHost.exe |
| Publisher | Microsoft Corporation |
| Signature check | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |
Common wahala dem
E hang after huge drop
End this host if the dialog don already comot. Then try share smaller thing again.
Dem dey confuse am with clipboard history
Win+V UI na Input Experience. This host na the broker.
How to troubleshoot
Diagnose before you change anything wey fit scatter things.
Retry the share after you end host wey hang
The apps wey call am go still dey run.
No replace the broker
System file.
Technical details
Technical details
| Image name | DataExchangeHost.exe |
|---|---|
| Role | Share and drag broker |
Check the identity of running file
A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)
Sources and verification
Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.
- Microsoft Learn: sharing data · Share and exchange
- Microsoft Learn: Windows · Primary Windows documentation
- Foxhole process map · First-party samples on top Windows PCs. No be lab benchmark.
- Microsoft Sysinternals: Sigcheck · Dey explain how to check file signatures. Dis reference no establish the identity or safety of any particular running file.
- Microsoft: Get-CimInstance · Read-only local process-query method. (pcm)
- Microsoft: Win32_Process properties · 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.
Thank you. Dat one dey help us make dis page better.