dasHost.exe

Windows ProcessMicrosoft Corporation

Also called dashost, device association framework provider host, daf host

WindowsSystem Component

Device Association Framework Provider Host. It is the DAF service host that associates radios and wireless devices, not the pairing wizard window.

What you need to know

dasHost is the DAF service host.

dasHost.exe hosts Device Association Framework providers so Windows can pair Bluetooth, Wi-Fi Direct, and similar devices. DevicePairingWizard.exe is the pairing UI. Ending the host can drop an already paired radio until the Device Association Service starts it again.

Safe?: Yes, in System32
Same as DevicePairingWizard?: No. This is the DAF service host
Many copies?: One per associated device is common

Feex says

If I see Device Association Framework Provider Host pegged after I plugged in a dongle, I update that radio driver. I do not close DevicePairingWizard and call the job done.

What is dasHost.exe?

dasHost.exe is the DAF service host. Device Association Framework talks to association providers for radios and wireless devices. DevicePairingWizard.exe only draws the pair dialog. Swapping those names is wrong.

What does it do?

It keeps device association sessions alive after you click Pair. It does not print, and it does not host UMDF drivers. That last job is WUDFHost.exe.

Why is it running?

A Bluetooth mouse, a wireless display, a printer discovery, or another DAF provider is in play. Copies can sit around because each association can have its own host.

Why are there multiple copies?

Windows can start more than one dasHost.exe while more than one device is associated. That is DAF hosting, not DevicePairingWizard.exe opening twice.

Is it safe?

Usually safe

System32 dasHost.exe is the DAF service host. A dasHost.exe in a driver pack folder is not that host. The pairing wizard is a different filename.

A legitimate copy normally runs from:

C:\Windows\System32\dasHost.exe

Expected publisher: Microsoft Corporation
Related service: Device Association Service
Pairing UI: DevicePairingWizard.exe, not this file

Can I end it?

Pairing can drop

Ending dasHost.exe can disconnect the device that host was associating. The wizard window is not this process. Restart the Device Association Service if the radio goes quiet.

Can I remove it?

Do not delete dasHost.exe. You would break DAF pairing. Unpair a device in Settings, or update the radio driver. Leave System32 alone.

Should it start with Windows?

Device Association Service starts the host on demand. It is not a Startup Apps entry next to the pairing wizard.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: A bad Bluetooth or wireless-display driver can peg a copy
Memory: Usually small per associated device
Disk: Low
Network: Discovery and pairing traffic for wireless devices

File information

dasHost.exe file information
Executable name	dasHost.exe
Common legitimate path	C:\Windows\System32\dasHost.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

High CPU after hibernate

A radio that fails to resume can spin DAF. Update or remove that adapter in Device Manager before you disable the service.

UDP chatter during print discovery

A modern print dialog can keep DAF looking for network printers. That is still dasHost, not DevicePairingWizard.

Troubleshooting

Diagnose before you change anything destructive.

Device Manager on the radio, not the wizard

Bluetooth, network adapters, and wireless displays. Uninstall the stale driver, reboot, and let Windows reinstall. DevicePairingWizard.exe is only the prompt.

Restart Device Association Service after the driver change

services.msc, then pair again. Ending only the Task Manager row leaves the service and the bad driver in place.

Technical details

dasHost.exe technical details
Image name	dasHost.exe
Role	Device Association Framework service host

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: pair devices · Windows pairing stack for radios and wireless devices
Microsoft Support: Bluetooth pairing · Pairing UI is not the DAF host
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.