# DevicePairingWizard.exe

Windows Process: Microsoft Corporation

Catalog search terms devicepairingwizard, pairing wizard, add bluetooth device

Windows, System Component

Bluetooth and device pairing wizard UI. Na the pair dialog. dasHost.exe na the Device Association Framework service host.

## Wetin you need know

This na the pairing wizard UI, no be dasHost.

DevicePairingWizard.exe dey draw Add a device / pair prompts. dasHost.exe dey keep Device Association Framework sessions active after you click Pair. If you end the wizard, e go cancel the dialog, no be the DAF host.

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

  **E same thing with dasHost?**: No. dasHost na the DAF service host

  **I suppose end am?**: The pair dialog go close

Feex tok say

If the pair box dey screen, na DevicePairingWizard be that. I no dey end dasHost make I take close the wizard, and I no dey talk say work don finish if na only the UI die.

## Wetin be DevicePairingWizard.exe?

DevicePairingWizard.exe na the pairing wizard UI, no be dasHost.exe. Settings fit open this dialog. The DAF service host get different filename.

## Wetin e dey do?

E dey list devices and collect the PIN. dasHost.exe dey follow association providers talk after you confirm. WUDFHost.exe still be another process if UMDF driver load.

## Wetin make am dey run?

You click Add device, or Bluetooth pair start, or wireless display ask to pair. The wizard suppose close when the dialog comot.

## 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 'DevicePairingWizard.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

System32 DevicePairingWizard.exe na the wizard. Any pairing exe inside driver pack no be am. dasHost.exe still remain the service host.

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

`C:\Windows\System32\DevicePairingWizard.exe`

- Pairing UI only
- DAF host: dasHost.exe
- Settings fit open this dialog

## I fit end am?

E dey cancel the dialog

If you end DevicePairingWizard.exe, e go close the pair UI. dasHost.exe fit still hold association. Unpair inside Settings if you no mean to finish am.

## I fit comot am?

No

No delete DevicePairingWizard.exe. You go lose the supported pair dialog. Unpair devices inside Settings. Leave dasHost.exe as e dey.

## E suppose start with Windows?

On demand when you pair am. No be Startup Apps row beside dasHost.

## 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            | DevicePairingWizard.exe                                                            |
| -------------------------- | ---------------------------------------------------------------------------------- |
| Recorded installation path | C:\Windows\System32\DevicePairingWizard.exe                                        |
| Publisher                  | Microsoft Corporation                                                              |
| Signature check            | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |

## Common wahala dem

### Wizard don close, device still dey try connect

Na dasHost be dat, no be dis UI. Restart Device Association Service afta bad radio driver.

### People dey end dasHost make dem fit dismiss di box

Na dis process be di box. To kill DAF fit drop devices wey you don pair already.

## How to troubleshoot

Diagnose before you change anything wey fit scatter things.

### Finish or cancel di dialog, den check Bluetooth for Settings

Di wizard na just di prompt. dasHost.exe na di host wey dey remain.

### Update di radio for Device Manager

List wey hang na often di adapter, no be say System32 wizard dey miss.

## Technical details

Technical details

| Image name | DevicePairingWizard.exe  |
| ---------- | ------------------------ |
| Role       | Device pairing wizard UI |

## 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.

[dasHost.exe: Windows Process](https://feex.it/wiki/l/pcm/process/dashost.exe/)[SystemSettings.exe: Windows Process](https://feex.it/wiki/l/pcm/process/systemsettings.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: pair a Bluetooth device ](https://support.microsoft.com/windows/pair-a-bluetooth-device-in-windows)· Pairing UI
- [Microsoft Learn: pair devices ](https://learn.microsoft.com/windows/uwp/devices-sensors/pair-devices)· Pairing stack versus DAF host
- [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**: DevicePairingWizard.exe

  **Typical path**: C:\Windows\System32\DevicePairingWizard.exe

  **Record context**: Feex Wiki reference entry

  **Related process**: [dasHost.exe](https://feex.it/wiki/l/pcm/process/dashost.exe/)

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/devicepairingwizard.exe/)

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