# DevicePairingWizard.exe

Windows Process: Microsoft Corporation

Also called devicepairingwizard, pairing wizard, add bluetooth device

Windows, System Component

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

## What you need to know

This is the pairing wizard UI, not dasHost.

DevicePairingWizard.exe draws Add a device / pair prompts. dasHost.exe keeps Device Association Framework sessions alive after you click Pair. Ending the wizard cancels the dialog, not the DAF host.

- **Safe?**: Yes, while you pair

  **Same as dasHost?**: No. dasHost is the DAF service host

  **Should I end it?**: The pair dialog closes

Feex says

If the pair box is on screen, that is DevicePairingWizard. I do not end dasHost to close the wizard, and I do not call the job done if only the UI died.

## What is DevicePairingWizard.exe?

DevicePairingWizard.exe is the pairing wizard UI, not dasHost.exe. Settings can open this dialog. The DAF service host is a different filename.

## What does it do?

It lists devices and collects the PIN. dasHost.exe talks to association providers after you confirm. WUDFHost.exe is still another process if a UMDF driver loads.

## Why is it running?

You clicked Add device, a Bluetooth pair started, or a wireless display asked to pair. The wizard should exit when the dialog closes.

## Is it safe?

Usually safe

System32 DevicePairingWizard.exe is the wizard. A pairing exe in a driver pack is not. dasHost.exe is still the service host.

A legitimate copy normally runs from:

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

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

## Can I end it?

Cancels the dialog

Ending DevicePairingWizard.exe closes the pair UI. dasHost.exe can still hold an association. Unpair in Settings if you did not mean to finish.

## Can I remove it?

No

Do not delete DevicePairingWizard.exe. You would lose the supported pair dialog. Unpair devices in Settings. Leave dasHost.exe in place.

## Should it start with Windows?

On demand when you pair. It is not a Startup Apps row next to dasHost.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Low while the list refreshes

  **Memory**: Small

  **Disk**: None

  **Network**: Discovery for wireless devices

## File information

| Executable name        | DevicePairingWizard.exe                     |
| ---------------------- | ------------------------------------------- |
| Common legitimate path | C:\Windows\System32\DevicePairingWizard.exe |
| Publisher              | Microsoft Corporation                       |
| Signature expectation  | Signed by Microsoft Windows                 |

## Common problems

### Wizard closed, device still tries to associate

That is dasHost, not this UI. Restart Device Association Service after a bad radio driver.

### People end dasHost to dismiss the box

The box is this process. Killing DAF can drop devices you already paired.

## Troubleshooting

Diagnose before you change anything destructive.

### Finish or cancel the dialog, then check Bluetooth in Settings

The wizard is only the prompt. dasHost.exe is the host that remains.

### Update the radio in Device Manager

A stuck list is often the adapter, not a missing System32 wizard.

## Technical details

Technical details

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

## Related

These entities connect to this article. Type is shown on every link.

[dasHost.exe: Windows Process](https://feex.it/wiki/process/dashost.exe)[SystemSettings.exe: Windows Process](https://feex.it/wiki/process/systemsettings.exe)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we 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 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.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Windows Process

  **Publisher**: Microsoft Corporation

  **Executable**: DevicePairingWizard.exe

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

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

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

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/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)