Skip go content

dasHost.exe

Windows ProcessMicrosoft Corporation

Catalog search terms dashost, device association framework provider host, daf host

WindowsSystem Component

Device Association Framework Provider Host. Na the DAF service host wey dey link radios and wireless devices, no be the pairing wizard window.

Wetin you need know

dasHost na the DAF service host.

dasHost.exe dey host Device Association Framework providers so that Windows fit pair Bluetooth, Wi-Fi Direct, and other similar devices. DevicePairingWizard.exe na the pairing UI. If you end the host, e fit disconnect radio wey don pair already until Device Association Service start am again.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
E same thing with DevicePairingWizard?
No. This na the DAF service host
Plenty copies?
One per associated device dey common
Feex tok say
If I see say Device Association Framework Provider Host jump high after I plug dongle, I dey update that radio driver. I no dey close DevicePairingWizard come talk say the work don finish.

Wetin be dasHost.exe?

dasHost.exe na the DAF service host. Device Association Framework dey follow association providers for radios and wireless devices talk. DevicePairingWizard.exe only dey draw the pair dialog. To swap those names no correct.

Wetin e dey do?

E dey keep device association sessions active after you click Pair. E no dey print, and e no dey host UMDF drivers. That last job na WUDFHost.exe dey do am.

Wetin make am dey run?

Bluetooth mouse, wireless display, printer discovery, or another DAF provider dey work. Copies fit sitdown for there because each association fit get im own host.

Wetin make many copies dey?

Windows fit start pass one dasHost.exe when pass one device dey associated. Na DAF hosting be that, no be DevicePairingWizard.exe wey open twice.

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 'dasHost.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 dasHost.exe na the DAF service host. Any dasHost.exe inside driver pack folder no be that host. The pairing wizard na different filename entirely.

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

C:\Windows\System32\dasHost.exe

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

I fit end am?

Pairing fit disconnect

If you end dasHost.exe e fit disconnect the device wey that host dey associate. The wizard window no be this process. Restart Device Association Service if the radio stop to work.

I fit comot am?

No

No delete dasHost.exe. You go scatter DAF pairing. Unpair device inside Settings, or update the radio driver. Leave System32 alone.

E suppose start with Windows?

Device Association Service dey start the host when need dey. E no be Startup Apps entry wey dey beside the pairing wizard.

Measure resource use

Measure the current process rather than assume a universal baseline
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

dasHost.exe file information
Executable name dasHost.exe
Recorded installation path C:\Windows\System32\dasHost.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

High CPU after hibernate

Radio wey fail to resume fit make DAF dey spin. Update or comot that adapter inside Device Manager before you disable the service.

UDP chatter during print discovery

Modern print dialog fit make DAF continue to look for network printers. That one still na dasHost, no be DevicePairingWizard.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Check Device Manager on top the radio, no be the wizard

Bluetooth, network adapters, and wireless displays. Uninstall the old driver, reboot, make Windows reinstall am. DevicePairingWizard.exe na just the prompt.

Restart Device Association Service after you change driver

Open services.msc, then pair again. If you only end the Task Manager row, e go leave the service and the bad driver as dem dey.

Technical details

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

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.

Dis article make sense to you?

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

Dis article make sense to you?