Microsoft’s PowerToys is preparing what may be the most practical single addition to the suite in years: a native monitor-control module (variously called
PowerDisplay or
Power Monitor) that promises per‑monitor brightness, contrast, color‑temperature and even volume controls from a system‑tray flyout — a long‑overdue fix for Windows 11’s awkward handling of external displays.
Background
PowerToys has spent the last few years acting as Microsoft’s lightweight experimental lab: features get built, tested in the open, and either stay in the suite or inform the OS itself. That history makes the new monitor tool noteworthy because it addresses an everyday pain that Windows has never solved well — controlling the backlight and related settings for external monitors from within Windows.
The module was publicly teased by Microsoft program manager Niels Laute on X, and screenshots and an early GitHub proposal have circulated since late November, showing a compact flyout with sliders for
brightness,
contrast,
color temperature, and
per‑monitor volume where applicable. The team has described the work as still being refined — the UI began life as an AI‑generated mockup and has already been iterated. The PowerToys team has suggested a goal of shipping in January, but that date is unofficial and subject to change.
Overview: what PowerDisplay (aka Power Monitor) proposes
From the screenshots and the GitHub discussion, the proposed module aims to deliver a simple, consistent control surface for multiple displays. Key elements shown or discussed include:
- Brightness sliders for each detected monitor.
- Contrast sliders and color‑temperature (white balance) adjustments.
- Volume controls for displays with built‑in speakers.
- Per‑monitor selection, potential presets and quick profiles.
- System‑tray access and keyboard hotkeys for instant changes.
If it arrives in this form, the module will replicate (within a single, Microsoft‑maintained app) the feature sets many third‑party utilities already offer, while adding the benefits of a consistent UI and first‑party distribution. Early reporting shows the project is still in development on GitHub and being actively discussed inside the PowerToys community.
Under the hood: how these monitor controls actually work
Software brightness and related controls for external monitors rely on industry standards that let a host talk to a display over the display cable. The two central technical pieces are:
- DDC/CI (Display Data Channel / Command Interface) — the channel over which a PC can send commands to a monitor and read back its status.
- MCCS / VCP (Monitor Control Command Set / Virtual Control Panel) — the defined commands (VCP codes) used to change brightness, contrast, color temperature and more.
Most third‑party utilities (Twinkle Tray, Monitorian, DisplayBuddy, Monitor Control add‑ons) work by issuing these VCP commands. A PowerToys module will almost certainly use the same plumbing, so
compatibility will depend on what each monitor exposes and whether the DDC/CI channel is preserved by the connection path.
Why this matters: the real user problem
Windows exposes easy brightness controls for built‑in laptop screens via Quick Settings and the Settings app, but external monitors are different: most vendor displays require users to navigate tiny onscreen OSD menus using physical buttons. That’s slow, inconsistent, and frustrating when you have more than one display. A single, reliable software surface solves that friction and is a genuine daily‑use productivity improvement.
Third‑party tools already show the demand: people install
Twinkle Tray,
Monitorian, or
DisplayBuddy to fix this exact annoyance. What makes a PowerToys module attractive is the combination of:
- First‑party maintenance and distribution (available via PowerToys releases, winget, or the Microsoft Store).
- Centralized management and enterprise control (PowerToys is easier to govern via ADMX/MDM than random GitHub releases).
- A consistent Windows look & feel, and the trust that comes from Microsoft stewardship.
Compatibility and limitations — the caveats users must understand
A PowerToys monitor control utility is not a magical cure: the same hardware and driver constraints that affect third‑party tools will apply.
- Not all monitors implement the same VCP codes. Some expose only brightness, others expose richer controls; some use proprietary extensions. Result: behavior will vary by model.
- Cables, adapters, and docks matter. DDC/CI commands travel over the physical link (DisplayPort, HDMI, USB‑C alt‑mode). Cheap adapters or some docks do not forward the DDC channel, making a monitor invisible to software control. DisplayLink USB graphics chains may require specific driver support.
- Graphics drivers and Windows updates can change how EDID/DDC queries behave; driver regressions can temporarily break support until updated.
- HDR and color‑critical workflows: software changes to brightness/color temperature can invalidate calibration. Professional colorists may need to re‑calibrate after software adjustments.
In short: the PowerToys module can
simplify the user experience when hardware cooperates, but it cannot force monitors or intermediary hubs to support DDC/CI. Expect a mix of “works perfectly” and “partially supported” across mixed setups.
Current status and timeline — what we can verify now
- The feature was publicly teased by Microsoft PowerToys program manager Niels Laute on X with a screenshot and the text “The PowerToys team is .” That post is part of the public discussion raising awareness of the module.
- A GitHub proposal / draft pull request exists for the module (commonly discussed as PowerDisplay or Power Monitor) and contains early UI mockups and suggested features. The PowerToys repository itself is the home for this work.
- The team commented that they “hope to ship in January,” but that remark is a plan, not a firm ship date; the module is still undergoing code review, bug‑fixing and QA. Treat the January target as provisional until a formal PowerToys release note appears.
Those three points are independently reported across multiple outlets and mirrored in the community‑hosted GitHub discussion; however, the exact release schedule and feature set remain subject to change during development.
Practical guidance: how to prepare and what to try now
If you care about software control of external monitors, there are concrete steps to take now that will make your setup ready for PowerToys’ module and give you reliable workarounds in the meantime.
- Check whether your monitors support DDC/CI: open the monitor OSD and look for a “DDC/CI”, “Enable external control”, or similar toggle. If present, enable it.
- Prefer direct connections: when possible, connect monitors directly to the GPU with DisplayPort or HDMI rather than routing through low‑end hubs or docks that may not forward DDC/CI.
- Test with existing tools: try Monitorian or Twinkle Tray to confirm whether your monitor responds to VCP commands — if these apps work, the PowerToys module likely will too.
- For DisplayLink or USB‑C dock users: check vendor docs and driver versions — DisplayLink and some docks have added brightness support in recent drivers, but compatibility varies.
- Install PowerToys via winget or the Microsoft Store to make updates simpler (PowerToys is managed through the GitHub repo and official channels). When the module ships, an update through those channels will be the easiest path.
A short, practical checklist for IT admins:
- Pilot the module on representative hardware and document which monitor models and dock chains are supported.
- Confirm whether PowerToys builds used for deployment are code‑signed and acceptable for your organization’s policy.
- Prepare fallback instructions (vendor tools, OSD navigation) for machines where DDC/CI is blocked by firmware or adapter chains.
Security, privacy and enterprise considerations
PowerToys is open source and distributed from Microsoft’s GitHub org, which reduces trust friction compared with random closed binaries. Still, enterprises should consider:
- Code signing and update channels: prefer vetted PowerToys releases and signed installers for managed deployments.
- Telemetry and privacy: verify and document what (if any) telemetry PowerToys modules send. PowerToys typically includes telemetry opt‑outs, but administrators should confirm per‑module behavior.
- Group Policy / MDM controls: PowerToys can be managed in enterprise environments; plan rollout and communication to minimize help‑desk impact from new automated features.
For citizen‑admins and enthusiasts, the advantage is clear: a Microsoft‑maintained module is easier to roll out and support than a patchwork of third‑party tools.
Critical analysis — strengths, weaknesses and realistic expectations
Strengths
- Practical, high‑value functionality: a single UI for multiple monitors answers a frequent, everyday annoyance.
- First‑party trust and distribution: PowerToys integration lowers risk compared with unknown GitHub binaries.
- Consistent UI and enterprise manageability: makes it simpler for IT teams to standardize and support.
Weaknesses & Risks
- Hardware and cabling remain the ultimate limiter: if your dock or cable doesn’t pass DDC/CI, no software layer can fix that. Expect edge cases.
- Driver and firmware variability: graphics drivers and monitor firmware updates can break VCP access unpredictably; expect occasional regressions.
- Not a replacement for vendor firmware tools: advanced vendor functions (factory presets, firmware updates, hardware calibration) will still require vendor software or onboard OSD.
Longer‑term outlook
- PowerToys has a track record of incubating features that later influence Windows’ own settings. FancyZones inspired snapping improvements, and Light Switch delivered a feature Windows hadn’t prioritized natively. If PowerDisplay proves broadly useful, expect Microsoft to keep evolving it and possibly bring selected capabilities into the OS experience over time — though that is speculative and will depend on adoption and engineering priorities.
What to watch for next
- A GitHub pull request merge and a PowerToys release note announcing PowerDisplay / Power Monitor will be the definitive sign it’s ready for general use. Until then, references to a January ship target should be treated as optimistic.
- Community reports during the preview phase will quickly surface which monitor models and docks do or do not work; that early compatibility matrix will be essential for enterprise pilots.
- Watch for explicit notes about how the module handles HDR displays, local dimming, and color profiles — these are the sticky technical areas where user expectations and professional workflows can conflict.
Immediate recommendations for readers
- If you need multi‑monitor brightness control today, install a trusted third‑party utility (Twinkle Tray, Monitorian, DisplayBuddy) and use it as a compatibility test; if those tools control your displays, PowerToys is likely to work as well when it ships.
- Prefer direct GPU connections and good quality DisplayPort / HDMI cables during your power‑user setup phase; docks and cheap adapters are the most common reason such tools fail.
- Track the PowerToys GitHub (the PowerToys repo) and the project’s release notes for the official announcement; that will include the final feature list, release date, and any enterprise guidance.
Conclusion
PowerToys’ new monitor module addresses a mundane but persistent Windows problem in a way that makes practical sense: software brightness and color controls belong in the operating system’s toolbox, and doing this inside PowerToys is exactly the right experimental path. The technical approach — using DDC/CI and VCP codes — is the same plumbing third‑party tools have relied on for years, which means the module will inherit the same hardware‑compatibility limits while delivering a cleaner, first‑party experience if your monitors and cables cooperate. Expect an initial preview and community testing cycle before widespread availability; the January target is plausible but not guaranteed. In the meantime, prepare your setup by verifying DDC/CI support, testing with existing utilities, and favoring direct connections over dock chains that may block the DDC channel. When PowerDisplay ships, it will likely become the simplest, most trustworthy option for everyday multi‑monitor brightness and basic color adjustments on Windows 11 — a small change with outsized daily benefits.
Source: Windows Central
https://www.windowscentral.com/soft...he-better-brightness-controls-are-on-the-way/