# DeviceProperties.exe

Windows Process: Microsoft Corporation

Also called deviceproperties, device properties, hardware properties

Windows, System Component

Device properties sheet from Device Manager. It is the Details / Driver UI for one device. WUDFHost.exe is the UMDF driver host, not this window.

## What you need to know

Device properties UI, not the driver host WUDFHost.

DeviceProperties.exe is the property sheet Device Manager opens. WUDFHost.exe loads user-mode drivers. Ending the sheet does not unload a UMDF stack.

- **Safe?**: Yes, when you opened properties

  **Is it the driver host?**: No. WUDFHost.exe hosts UMDF drivers

  **Should I end it?**: The properties window closes

Feex says

If I opened a device and this name is the window, I read the Driver tab. I do not end WUDFHost to close properties.

## What is DeviceProperties.exe?

DeviceProperties.exe is device properties UI, not the driver host WUDFHost.exe. Device Manager starts this sheet for one hardware instance.

## What does it do?

It shows General, Driver, Details, and Events. It does not run WinUSB. WUDFHost.exe does that for UMDF devices. dasHost.exe is still DAF pairing.

## Why is it running?

You double-clicked a device, or an installer opened hardware properties. The process should exit when you close the sheet.

## Is it safe?

Usually safe

System32 DeviceProperties.exe is Microsoft. A DeviceProperties.exe in a driver pack folder is not this sheet.

A legitimate copy normally runs from:

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

- Device Manager property sheet
- UMDF host: WUDFHost.exe
- Not dasHost.exe

## Can I end it?

Closes the sheet

Ending DeviceProperties.exe closes the window. The device and WUDFHost.exe stay. A driver change you already clicked Apply may still be pending a reboot.

## Can I remove it?

No

Do not delete DeviceProperties.exe. Uninstall a device from Device Manager if you want that hardware gone. Leave WUDFHost.exe in place.

## Should it start with Windows?

On demand from Device Manager. It is not a Startup Apps row.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Low

  **Memory**: Small

  **Disk**: None

  **Network**: None for a local sheet

## File information

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

## Common problems

### People end WUDFHost because properties looks stuck

The sheet is this process. Ending the UMDF host can drop the gadget.

### Properties blank after a bad driver

Uninstall the device and rescan. Do not replace DeviceProperties.exe.

## Troubleshooting

Diagnose before you change anything destructive.

### Close the sheet, then reopen from Device Manager

If the window is this exe, WUDFHost.exe is not the UI.

### Update or roll back from the Driver tab

That tab is why this process exists. A forum zip is not the first step.

## Technical details

Technical details

| Image name | DeviceProperties.exe         |
| ---------- | ---------------------------- |
| Role       | Device Manager properties UI |

## Related

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

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

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft Learn: Device Manager ](https://learn.microsoft.com/windows-hardware/drivers/install/using-device-manager)· Properties sheet for a device
- [Microsoft Support: update drivers ](https://support.microsoft.com/windows/update-drivers-manually-in-windows)· Driver tab on the properties UI
- [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**: DeviceProperties.exe

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

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

  **Related process**: [WUDFHost.exe](https://feex.it/wiki/process/wudfhost.exe)

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/deviceproperties.exe/)

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