microsoft / microsoft/PowerToys

Power Display: detect external monitors by connection type and allow WMI/DDC override

Open
#49,893 1 comment 0 reactions 1 assignee View on GitHub

@moooyo is already working on this.

Since Aug 18, 2026.

Needs-Triage Product-PowerDisplay
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

### Description of the new feature / enhancement

Power Display should not classify a monitor as built-in solely because it exposes a WmiMonitorBrightness instance. It should also consider the display output technology reported by QueryDisplayConfig (HDMI, external DisplayPort, DVI, etc.).

Please also add a per-monitor override that lets the user choose the communication method:

- Automatic
- WMI
- DDC/CI

Expected behavior: an HDMI/DisplayPort monitor that happens to expose WMI brightness should remain an external display and should be eligible for DDC/CI discovery. Profiles should keep matching the same physical monitor if the automatic communication method changes.

### Scenario when this would be used?

I use two desktop monitors. My DEXP DF24H1 is connected through HDMI and Windows identifies it correctly by EDID, but it also exposes WmiMonitorBrightness. Power Display 0.100.2 therefore labels it as Built-in display 2 and excludes it from DDC/CI discovery.

This matters because the monitor loses its correct name and DDC/CI-only controls, and profiles created for the external-monitor representation may no longer match after the monitor is reclassified as WMI. Monitorian can still control its brightness, confirming that the display itself and the brightness channel are working.

### Supporting information

Observed on PowerToys 0.100.2:

- Monitor: DEXP DF24H1
- EDID hardware ID: SKG2413
- Connection reported by Windows: VideoOutputTechnology = 5 (HDMI)
- PnP status: OK
- Power Display log: EdidId=SKG2413 / DEXP DF24H1 -> WMI (internal)
- Classification summary: 1 WMI, 1 DDC/CI
- Enabling Max compatibility mode does not change the classification, because the DEXP is excluded from the DDC/CI target set before probing.
- Sending the current brightness value through WMI succeeds, so this is a classification issue rather than a failed monitor or cable.

Screenshot of the Power Display flyout showing the HDMI DEXP monitor as Built-in display 2:

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.