Microsoft’s PowerToys is preparing a practical fix for one of Windows 11’s most persistent everyday annoyances: a new utility — shown in early teasers as PowerDisplay (also discussed as Power Monitor) — that promises per‑monitor brightness, contrast, color temperature and even speaker volume controls from a single taskbar flyout, bringing first‑party convenience to multi‑monitor management.
Background
PowerToys has long functioned as Microsoft’s public sandbox for small, high‑utility tools that close gaps in Windows’ default feature set. Over the past few years the project has graduated from a hobbyist collection into an actively maintained, open‑source toolkit distributed via GitHub and the Microsoft Store, and it has repeatedly produced features that users ask Microsoft to adopt system‑wide. FancyZones (advanced window tiling), PowerToys Run (a fast launcher), and the newer Light Switch theme automation are examples of utilities that began in PowerToys and became essential to power users.
The current PowerToys work‑in‑progress addresses a narrow but ubiquitous pain point: laptop displays have convenient brightness controls baked into Quick Settings, while external monitors typically force users into tiny, awkward on‑screen display (OSD) menus operated with physical buttons. Third‑party apps have filled the gap for years, but a Microsoft‑maintained, well‑integrated solution would remove friction for a much broader audience. Several outlets have reported the teaser and early development conversation, and the PowerToys team’s public posts have made the concept visible to the community.
What PowerDisplay proposes
From publicly shared screenshots and discussion traces, the proposed PowerToys module aims to deliver:
- Per‑monitor brightness sliders for every detected display.
- Contrast adjustments and color temperature (warm ↔ cool) controls where supported.
- Per‑monitor volume sliders for monitors with built‑in speakers or audio passthrough.
- A compact system‑tray flyout / taskbar context menu to surface all controls without opening Settings or pressing OSD buttons.
- Potential for presets/profiles, hotkeys, and automation in later updates.
This feature set mirrors established third‑party tools (Twinkle Tray, Monitorian, DisplayBuddy, ClickMonitorDDC), but packaged within PowerToys’ consistent UI and Microsoft’s distribution channels—an appealing proposition for users and administrators alike.
How it works: the technical plumbing
Under the hood, software control of external monitor settings depends on long‑standing standards:
- DDC/CI (Display Data Channel / Command Interface): a bidirectional channel that lets a host query a monitor and send commands over the display link.
- MCCS / VCP (Monitor Control Command Set / Virtual Control Panel): an industry set of VCP codes that map to functions like brightness (commonly VCP 0x10), contrast (0x12), color temperature and volume.
Most third‑party tools and the proposed PowerToys module will use the same DDC/CI + VCP approach, meaning that compatibility hinges on what the monitor and the connection path expose and forward. If DDC/CI is preserved end‑to‑end (direct DisplayPort/HDMI/USB‑C alt‑mode), the software can typically adjust supported settings; if a hub, adapter or DisplayLink chain strips or blocks DDC/CI, controls will not reach the panel. These constraints are an industry reality, not a PowerToys limitation.
Verification and timeline — what’s confirmed and what’s tentative
Multiple independent outlets have reported the same sequence of events: a PowerToys program manager publicly teased the utility, screenshots and a GitHub discussion surfaced, and the PowerToys team is iterating on UI and code. Reputable technology sites, including PCWorld and Windows Central, have covered the announcement and referenced a social media tease by Niels Laute, a PowerToys program manager. Key claims and their verification status:
- The feature name: early reports use PowerDisplay and Power Monitor interchangeably; naming is still informal and may change before release.
- Public tease: a screenshot and short message from a PowerToys program manager were shared publicly and widely reposted. This social post is the origin of reporting.
- GitHub activity: PowerToys’ issue tracker and pull request logs show long‑standing interest in monitor controls and several recent issues requesting brightness/DDC/CI support, but a fully merged “PowerDisplay” pull request was not visible publicly at the time of reporting. That means the project is active in discussion and early code review, but a final, merged release branch had not yet been confirmed in the public release history. Treat claims that “the code is available for early testing” as plausible but not fully verifiable until a named PR or preview build appears in the official releases.
- Estimated release window: several reports and the team’s public comments indicate a January 2026 target in the PowerToys cadence (community discussion has referenced a prospective 0.98 milestone). This is an optimistic target and remains subject to code review, QA and bug triage; it should be considered provisional until a GitHub release or PowerToys changelog entry confirms a version and date.
Strengths: why this matters to users and IT teams
PowerDisplay is small in scope but high in daily value. The likely strengths include:
- High-frequency value: brightness/contrast adjustments are used multiple times per day; software sliders reduce friction and save time.
- Unified experience: a single, first‑party UI removes the need to poke through inconsistent vendor apps or OSD menus.
- Enterprise friendliness: PowerToys is open source, distributed through trusted channels (Microsoft Store, GitHub, winget) and can be managed via enterprise deployment tools, reducing friction for IT departments compared with random third‑party binaries.
- Incubation path: PowerToys has historically acted as a test bed; a successful module could influence future Windows Settings or Quick Settings integration.
These are practical wins for remote workers, creators, traders, and anyone routinely switching light conditions or swapping monitors. The convenience compounds: a two‑click brightness change repeated dozens of times per week quickly becomes a measurable productivity improvement.
Limits and risks: what PowerDisplay cannot change
It is critical to set realistic expectations. The software cannot bypass hardware or connection limits:
- Hardware VCP support: some monitors expose only brightness, while others expose richer VCP codes. If a monitor doesn’t implement a given VCP code (for contrast, color temperature or volume), the software slider will be unavailable or nonfunctional for that panel.
- Connection path fragility: many docks, inexpensive USB‑C adapters and some DisplayLink solutions do not forward DDC/CI reliably. Users plugged into such intermediary hardware may find controls missing or intermittent. Direct GPU connections (DisplayPort/HDMI/USB‑C alt‑mode) remain the most reliable.
- Color‑critical workflows: software changes to brightness/color temperature can invalidate color‑calibration profiles. Photographers, video editors and designers should re‑calibrate with a hardware colorimeter after major adjustments or maintain a separate calibrated workflow for color‑critical tasks.
- Driver and firmware regressions: changes in GPU drivers, monitor firmware or Windows updates can change EDID/DDC/CI behavior and break compatibility until fixes are issued; PowerToys cannot control these external variables.
- Security considerations: giving software control over external hardware increases the attack surface slightly. While DDC/CI control typically requires local privileges, administrators should confirm how the module handles permissions, whether it exposes programmatic APIs, and how it respects enterprise policies. Until documentation is published, treat this area cautiously.
In short: PowerDisplay can vastly improve convenience where the hardware chain cooperates, but it cannot magically enable controls over monitors or pathways that do not expose or forward the needed protocols.
How PowerDisplay compares to existing third‑party tools
Third‑party apps have long filled this gap and are useful diagnostics to test your setup:
- Twinkle Tray and Monitorian are popular Windows utilities that talk DDC/CI + VCP and support per‑monitor brightness and some advanced VCPs.
- DisplayBuddy targets macOS/Windows workflows for connected USB-C monitors and professional monitors that expose extensive VCP sets.
- ClickMonitorDDC and other utilities provide scripting and fine control for tinkerers.
PowerDisplay’s advantages over these tools are simple:
first‑party distribution, consistent UI, and integration into the PowerToys suite—which means easier discovery, consistent updating, and potentially enterprise‑sanctioned deployment. For many users, a single trusted app maintained by Microsoft will be preferable to piecing together separate third‑party binaries. That said, power users who need vendor‑specific advanced features or per‑pixel color matching may still rely on specialized manufacturer tools and hardware calibration devices.
Practical guidance: how to prepare and what to test now
If you rely on multiple displays and want to be ready for PowerDisplay or any similar tool:
- Test current DDC/CI compatibility:
- Install a reliable third‑party utility (Twinkle Tray or Monitorian) and confirm whether it can detect and adjust each monitor’s brightness. If those apps can control your screens, PowerDisplay is likely to work similarly when released.
- Prefer direct connections where possible:
- Use direct DisplayPort or HDMI connections from the GPU to the monitor when you need full DDC/CI support. Avoid low‑cost USB‑C hubs or DisplayLink chains if they don’t explicitly promise DDC/CI forwarding.
- Keep drivers and firmware current:
- Monitor vendor firmware and GPU driver updates can fix or break DDC/CI behavior. Track vendor release notes for any mention of display control forwarding.
- For professionals: maintain calibration workflows:
- After using software adjustments, re‑run hardware color calibrations to preserve color accuracy for production work.
- Track official channels:
- Watch PowerToys’ repositories and release notes for a public preview or Dev channel build rather than relying on speculative timelines. The current PowerToys release at the time of reporting was 0.95.x; community discussion referenced a possible 0.98 milestone for January, but that remains provisional.
Enterprise and admin considerations
PowerDisplay, if delivered via PowerToys, brings clear benefits for IT management:
- Distribution: PowerToys is available via Microsoft Store, winget and GitHub, making it easier to distribute using existing deployment pipelines.
- Policy control: a Microsoft‑maintained module could expose Group Policy or Intune controls to enable/disable the utility for managed systems, reducing the temptation for users to install unvetted third‑party brightness tools.
- Supportability: a single, documented Microsoft tool simplifies troubleshooting steps for helpdesk staff compared with multiple vendor utilities and inconsistent OSD menus.
Administrators should still treat DDC/CI forwarding as an environmental variable: many user support cases will continue to be caused by docks/adapters rather than the PowerToys module itself. Prepare standard troubleshooting steps: check direct connection, test with a known‑good DDC/CI tool, and verify firmware/driver versions before escalating.
Risks to watch and red flags
The following items merit scrutiny as PowerDisplay moves through previews:
- Claim verification: several news stories referenced GitHub drafts or early code, but a fully merged, discoverable PR or an official preview build is the confirmatory milestone to watch for. Until then, treat references to “code available for early testing” as partly verified—the project’s public issue discussions indicate active work but not a final merged module.
- Device enumeration UI: early screenshots from teases used autogenerated iconography and placeholder labels; users with multiple identical monitors raised concerns about how the UI will distinguish units. Expect further UX refinement before general availability.
- Interaction with HDR and adaptive sync: how PowerDisplay handles HDR, per‑monitor HDR toggles, local dimming, and dynamic refresh rates is unproven. These advanced features are prone to incompatibility with simple VCP adjustments; watch for documentation on HDR workflows and any caveats for high‑dynamic‑range content.
If any of these areas remain ambiguous in previews, treat the module as excellent for general convenience but not yet suitable as a replacement for professional color‑managed workflows.
Conclusion
PowerDisplay (Power Monitor) is a deceptively simple idea with outsized practical benefit: a single, first‑party control surface for per‑monitor brightness, contrast, color temperature and volume would remove a daily annoyance for millions of multi‑monitor Windows users. The concept is well‑aligned with PowerToys’ mission to prototype high‑leverage usability improvements in the open, and multiple independent outlets and the PowerToys team’s public messaging confirm the work is underway. That said, success depends on immutable hardware and connection realities: DDC/CI exposure, VCP support by vendors, and dock/adapter behavior. Until a named GitHub pull request is merged or an official PowerToys preview build is published, timeline claims (including the January 2026 target) should be treated as provisional. Users who want to evaluate compatibility today can test with existing third‑party tools; if those tools work for your monitors, PowerDisplay is likely to work likewise when it ships. PowerToys has repeatedly demonstrated that modest, well‑targeted features can deliver outsized day‑to‑day value. If PowerDisplay ships with reliable device detection, clear permissions, and sensible handling of edge cases, it will quickly become one of the suite’s most practically useful additions for anyone who lives with two or more screens.
Source: livemint.com
Microsoft PowerToys to bring enhanced control for multi-monitor users | Mint