Windows 11 Release Preview Brings Extreme Refresh Rate to Multi Monitor Setups

Microsoft’s latest Release Preview drop for Windows 11—delivered as KB5079387 to Insiders—makes a clear push into high-refresh display support and a handful of quality-of-life graphics features that gamers, creators, and multi-monitor users have been asking for. Early reports and preview notes indicate Microsoft is widening the OS-level refresh-rate envelope (what Neowin called “extreme display refresh rate” support) while rolling out the companion display and graphics improvements that power smoother scrolling, lower latency and better HDR workflows. These changes are arriving via Release Preview channel builds (26100.8106 and 26200.8106), and while the headline is compelling, the actual impact depends heavily on hardware, drivers, and the rollout cadence from manufacturers and OEMs.

Background / Overview​

Dynamic refresh technologies have been evolving rapidly across OS, GPU driver, and display firmware layers. Microsoft introduced Dynamic Refresh Rate (DRR) in Windows 11 to let systems automatically scale between lower refresh rates for power savings and higher refresh rates for responsiveness (inking, scrolling, low-latency input). Over time Microsoft has extended DRR and Variable Refresh Rate (VRR) behaviors to support more scenarios, including external displays and mixed-monitor setups. These preview-era updates also included the building blocks for better HDR calibration and a graphics-focused “Optimizations g input latency while enabling Auto HDR and VRR.
Historically, Windows’ refresh-rate logic has been a point of friction: OS-level policies, GPU drivers, EDID information from displays, and cable/connector bandwidth all interplay. Microsoft’s updates aim to make the OS a more active partner—choosing refresh rates dynamically and coordinating behavior across multiple monitors—rather than leaving everything to driver heuristics. Independent reporting and Insider blog notes confirm the company has been iterating on this capability across preview builds.

---

What KB5079387 reportedly adds​

• Release channel: KB5079387 is being delivered to Windows 11 Insiders via the Release Preview Channel as cumulative package for builds 26100.8106 (24H2) and 26200.8106 (25H2). This was surfaced in Insider rollout announcements and community posts tied to the March 2026 update wave.
• Display improvements: previehe update extends Windows’ support for “extreme” refresh rates—meaning the OS will better recognize and use very high panel refresh options on supported hardware, and improve DRR behavior across internal and external displays. The new capabilities are paired with improvements to how Windows manages multiple high-refresh displays to preserve power and GPU zero‑RPM modes where possible.
• Graphics and gaming: the update surface includes the previously previewed Optimizations for windowed games feature (improves latency, unlocks Auto HDR and VRR for more titles), smoother scrolling integration in more UIs and apps, and the Windows HDR Calibration app becoming accessible from Settings. These were originally rolled out to Insiders in earlier preview builds and are being expanded.
• Rollout nuance: KB5079387 appears to be part of the broader March 2026 update cycle (which included several cumulative packages such as KB5079473), but KB5079387 specifically targets Release Preview channel Insiders and acts as an enabling update for staged feature rollouts rather than an immediate, universal feature flip. Administrators should watch release notes and channel targeting carefully.

Note: some press coverage referenced a Neowin write-up that flagged “extreme display refresh rate support” specifically under KB5079387. At the time of writing, Microsoft’s cumulative KB rollups for March cover many items; the new behavior is best treated as a staged, hardware-dependent enhancement rather than a universal OS switch. Community signals confirm the rollout is selective and tied to specific device/driver combinations. ([reddeddit.com/r/windowsinsiders/comments/1rrxdnp/releasing_windows_11_builds_261008106_and/)

---

How “extreme refresh rate” support actually works (and what it means)​

What Microsoft changed at the OS level​

Windows already supports a gamut of refresh rates via the display pipeline, but improvements in KB5079387 and earlier previews tighten the way Windows chooses and switches refresh rates:

• More aggressive DRR boosting for cursor, touch and pen — when you interact, the OS will boost to the panel’s high refresh rate more frequently to make input feel snappier. This was first observed in Insider builds and expanded in these Release Preview drops.
• Better multi-monitor coordination — Windows will attempt to keep GPUs in low-power modes (zero RPM fan idle) where possible, switching refresh behavior only when content or input requires it. That prevents a second high-refresh monitor from forcing elevated power state on the primary GPU unnecessarily.
• Expanded external display DRR testing — Microsoft is allowing DRR-style behaviors to be trialed on external monitors via Insider/preview channels to surface driver and firmware compatibility issues before a broader rollout.

What “extreme” means (hardware and bandwidth limits)​

“Extreme refresh rate” in media shorthand usually refers to panels that operate well above mainstream refresh rates (144Hz, 165Hz), typically 240Hz, 360Hz or beyond. Important constraints:

• Connector bandwidth: achieving extreme refresh at high resolution depends on DisplayPort (1.4 with DSC or 2.0) or HDMI 2.1 class bandwidth, and on the monitor and GPU supporting required reduced-blanking or compression. Windows changes alone won’t conjure bandwidth that the cable or GPU can’t deliver.
• EDID and driver support: the monitor must expose supported modes correctly via EDID and GPU drivers must advertise and allow these modes. OEM/driver updates are often necessary after OS changes.
• GPU and OS coordination: the OS, GPU driver, and monitor firmware must all agree on refresh-change policies to avoid flicker, signal negotiation loops, or modes where Windows reports a rate but the panel actually runs at half-rate (a community problem reported in some prevrts show edge cases where the system reports 120Hz but effectively runs at 60Hz or 120Hz when it should be 240Hz; this is typically driver/EDID negotiation friction, not a simple OS bug.

Because of these dependencies, users should treat the OS-level change as an enabling improvement rather than a guarantee that every panel will suddenly support, for example, 360Hz at 4K.

---

Gaming and latency: what to expect​

KB5079387’s graphics-related enhancements extend features Microsoft has iterated in Insider builds:

• Optimizations for windowed games: designed to improve latency when playing windowed or borderless games and to make Auto HDR/VRR available with fewer compatibility constraints. Turning this on via Settings > System > Display > Graphics may reduce input lag and unlock HDR/VRR for games that previously required full-screen exclusive modes.
• Auto HDR adoption: expanding Auto HDR’s availability when the OS supports more flexible refresh policies makes HDR conversion more consistent across titles and displays.
• Smoother scrolling and UI inking: Microsoft has been expanding boosted refresh behavior for scroll and pen interactions beyond Office to Edge (canary flags) and Settings, giving the UI a perceptibly smoother feel when hardware supports it.

These features matter for competitive gamers chasing lower latency and creators who rely on consistent HDR or color-managed workflows. However, performance gains are contingent on drivers and GPU firmware updates—not only on the KB package itself.

---

Known issues and community warnings​

Preview channels reveal both progress and problems. Community threads and Microsoft Q&A highlight recurring themes:

• Refresh-rate negotiation problems: users on Insider and preview builds have reported displays dropping to lower-than-expected refresh rates (e.g., reporting 120Hz but effectively running half that) or failing to display full-screen correctly at very high rates. These are typically caused by driver/display firmware negotiation issues or how Windows’ display policy interacts with specific hardware. Microsoft has acknowledged DRR/refresh rate work but issues persist in preview.
• DRR compatibility regressions: some users reported that after previous 24H2 updates, Dynamic Refresh Rate became “not supported” on systems where it had worked before—again underlining the fragile interdependence of OS, driver and firmware.
• Staged rollout and device gating: Microsoft is enabling features in a staged manner, which means not all devices in the Release Preview channel receive the same behavior simultaneously. Expect feature-gating and phased enablement as Microsoft collects telemetry and manufacturer feedback.

Because of these issues, enthusiasts should avoid assuming immediate, perfect behavior on their systems; instead, follow a cautious rollout plan and be prepaand monitor firmware.

---

How to prepare and validate on your PC (practical steps)​

If you want to test KB5079387 features (or generally validate high-refresh behavior on Windows 11), follow these steps:

• Verify your Windows build: open Settings > System > About and confirm you’re on the Release Preview build that corresponds to KB5079387 (26100.8106 or 26200.8106 for Insiders). If you’re not an Insider, wait for your production channel rollout.
• Update GPU drivers: get the latest WHQL/optional drivers from NVIDIA, AMD, or Intel that explicitly list support for the new Windows build, or check the GPU vendor’s release notes for DRR/VRR improvements.
• Update monitor firmware: check your monitor manufacturer for firmware updates that expand or fix EDID and refresh-mode negotiation, especially for 240Hz+ or novel DisplayPort/HDMI modes.
• Use the right cable and port: ensure you’re using certified DisplayPort 1.4/2.0 or HDMI 2.1 cables capable of the required bandwidth and plug into GPU ports that expose full lanes; docking stations and adapters often bottleneck refresh rates.
• Check advanced display settings: Settings > System > Display > Advanced display will list available refresh rates. Look for “Dynamic” options or the target refresh rate and test via the monitor’s OSD to confirm actual panel refresh.
• Test with controlled content: run benchmark or test utilities that can display explicit refresh rates and frame pacing (FPSTest, custom frame generators, or the monitor’s service menus) to confirm end-to-end behavior.
• Roll back if necessary: create a restore point and keep a copy of prior GPU drivers so you can revert igresses.

---

For IT admins: rollout guidance and risk mitigation​

• Pilot first: test KB5079387 and accompanying driver updates on a small representative set of machines (including mobile devices, desktops with multiple displays, and AV/meeting-room PCs).
• Lock drivers in managed environments: for stable endpoints, push vendor-validated drivers via your standard deployment pipeline rather than letting Windows Update pick optionaollout.
• Staged feature enablement: use Windows Update rings and Group Policy to stagger the update. If you rely on specialized display hardware (digital signage, control rooms), validate those systems separately; OS-level changes to refresh negotiation can break appliance-like setups.
• Rollback plan: have a documented rollback plan (restore points, driver packages, and update block policies) in case refresh negotiation causes outages or degraded user experience.
• Monitor telemetry and user reports: watch for reports of flicker, dropped signals, or unexpected refresh-rate changes and correlate them with driver/firmware versions.

---

Strengths, opportunities, and risks — critical analysis​

Strengths​

• User experience lift: enabling the OS to proactively manage extreme refresh behaviors can make scrolling, inking, and input feel materially better without every app doing heavy lifting. This is especially true for hybrid devices where power saving is important.
• Better multi-monitor handling: improving how Windows coordinates refresh across displays is a real win for multi-monitor productivity setups and gamers using mixed-refresh displays.
• Game-focused optimizations: bringing low-latency windowed game optimizations, Auto HDR and VRR closer together simplifies modern gaming setups and reduces friction for titles that don’t run well in exclusive fullscreen mode.

Risks and caveats​

• Hardware/driver fragmentation: the broader the OS-level policy, the more visible the gaps caused by out-of-date drivers and incomplete EDID support. Users with older GPUs or monitors stand to see regressions.
• Rollout complexity: staged enablement and channel targeting mean public messaging can be confusing: some users will get the feature immediately, others will not; some will get buggy behavior. Administrators must test rather than assume.
• Power vs. performance trade-offs: aggressive refresh-rate boosting increases responsiveness but can also increase power draw and reduce battery life on laptops. For users sensitive to battery life, default or “balanced” settings may still be preferable.
• Telemetry dependency: Microsoft’s phased approach depends on feedback and telemetry; while this is sensible, it also means the feature’s availability and behavior could change quickly based on anonymized data the user cannot inspect.

---

Verdict and practical recommendations​

KB5079387 represents a careful, iterative step forward: Microsoft is lifting OS-level behavior to better support very high refresh-rate displays and modern gaming scenarios. For early adopters and gamers with cutting-edge hardware, this is promising—provided you pair the OS update with up-to-date GPU drivers and monitor firmware. For IT admins and conservative users, the right approach is staged testing, driver control, and clear rollback plans.

• Enthusiasts: test on a secondary machine, update drivers and monitor firmware, and validate end-to-end using test utilities before trusting your primary workstation or gaming rig.
• Creators and professionals: wait for vendor-certified drivers for mission-critical systems if you rely on color-managed HDR workflows or have multi-monitor arrangements in production.
• Administrators: pilot, stage, and document rollback procedures. Use driver whitelisting or deployment groups to avoid surprise regressions that can impact meetings, streaming, or digital signage.

---

Final thoughts​

The promise of OS-driven support for “extreme” refresh rates is significant: smoother interaction, better game latency, and smarter power use across mixed-display setups. But as the preview rollout demonstrates, the reality will always be a three-way negotiation—Windows, the GPU driver, and the display’s firmware. Users who understand that dependency chain and prepare accordingly will see the biggest gains; everyone else should treat KB5079387 as a feature preview to be adopted with care.

---

---

Source: Neowin Windows 11 gets extreme display refresh rate support and new features in KB5079387

 

[ChatGPT]

Microsoft’s newest Release Preview drop for Windows 11 — packaged as KB5079387 and delivered as Builds 26100.8106 and 26200.8106 to Insiders — signals a deliberate push to improve the operating system’s handling of high‑refresh displays and the broader graphics stack, while rolling out several usability and accessibility enhancements that matter to gamers, creators, and power users alike. The release introduces what Microsoft and early reports call “extreme display refresh rate” support (monitors reporting refresh rates above 1000 Hz), wider Dynamic Refresh Rate (DRR) coverage, improved HDR and DisplayID handling, and several quality‑of‑life updates such as a Smart App Control toggle, Settings refinements, Narrator improvements, and voice/pen experience updates. This update is being staged and its availability will vary by device and market as Microsoft ramps the rollout.

Background / Overview​

Windows 11’s refresh‑rate story has evolved over several releases. The operating system introduced Dynamic Refresh Rate (DRR) as a way to balance smooth interactivity (with higher refresh rates) and power savings (with lower rates) on compatible laptops and tablets. Historically DRR has been most visible on internal laptop panels (commonly 60 Hz ↔ 120 Hz). Over time Microsoft has expanded DRR and related graphics optimizations to improve inking, scrolling, and general UI responsiveness. The DirectX and Windows teams documented DRR’s goals and supported scenarios when the feature first shipped, highlighting smoother inking, scrolling, and lower latency for specific app classes. Those original design goals are now being widened to embrace external and higher‑end displays.
The KB5079387 update — targeted at Insiders in the Release Preview channel — consolidates multiple efforts into a single, staged rollout: extreme refresh‑rate reporting, DRR and VRR improvements, Auto HDR and windowed‑game optimizations, improved HDR reliability for certain DisplayID implementations, and a string of settings and accessibility refinements. Because this is a Release Preview packaging, Microsoft is using a gradual rollout model to surface features to subsets of Insiders before wide availability; expect phased enablement and device‑dependent availability.

---

What KB5079387 actually changes​

Extreme display refresh rate support (what this means)​

• What Microsoft changed: Monitors can now report refresh rates higher than 1000 Hz to Windows. The OS will accept and enumerate very high refresh rates when the monitor advertises them via DisplayID/EDID, and the display stack has been adjusted to handle larger numeric values. This is the “extreme display refresh rate” capability many outlets highlighted.
• Why it matters: Device makers experimenting with ultrahigh refresh panels or specialized capture/measurement hardware will no longer be artificially limited by OS clamps that assumed lower ceilings. For gamers, esports hardware vendors, and certain pro AV use cases, operating‑system recognition of extreme rates is a prerequisite for proper toolchains and driver behavior.
• Practical reality check: There are verys that actually operate above several hundred hertz today; the OS change enables support for those that exist or may arrive, but it does not create new hardware. Treat the OS capability as necessary but not sufficient for practical ultra‑high‑refresh experiences.

Expanded Dynamic Refresh Rate (DRR) and Variable Refresh handling​

• Expanded targets: Microsoft is widening DRR’s scope beyond internal laptop panels and the small set of apps where it previously demonstrated the largest gains, making DRR behaviors (like boosting to a higher rate when moving the cursor or scrolling) available in more contexts. The update also continues work to avoid conflicts between DRR and games that use VRR.
• User experience changes: On supported systems, the OS may now increase refresh for pointer movement, pen and touch, and smooth scrolling in more built‑in apps (Settings, some Office scenarios) and compatible browsers when flagged. Microsoft’s policy remains: DRR should not interfere with VRR when a game explicitly requests full control.

Gaming and windowed‑game optimizations​

• Optimizations for windowed games: KB5079387 introduces or flips on a feature set aimed at lowering latency for windowed games and enabling Auto HDR/VRR in those contexts. This is positioned as a way to narrow input‑lag gaps and unlock Auto HDR/VRR for more titles without full‑screen exclusivity. Microsoft has been experimenting with these measures for a while; this update reflects work to surface them to Release Preview Insiders.
• What to expect: Improved input responsiveness in windowed and borderless window modes on supported hardware; Auto HDR where applicable; the OS-level plumbing to reduce bottlenecks that used to require exclusive full‑screen modes.

HDR, DisplayID and USB4 power improvements​

• HDR reliability: KB5079387 includes fixes for HDR reliability, especially for displays with non‑compliant DisplayID 2.0 blocks. This should reduce glitches and color problems on some HDR panels.
• DisplayID sizing: Work was done to improve the accuracy of monitor size reporting (via WMI monitor APIs) for displays using DisplayID; this helps color management, scaling, and calibration tools get better information from monitors.
• USB4 power management: When using a native USB4 monitor connection, the USB controller can now drop to a lower power state while the PC sleeps, improving battery life on portable systems docked to USB4 displays.

Settings, Smart App Control, voice and accessibility improvements​

• Smart App Control (SAC): The update makes Smart App Control togglable without a clean reinstall — a meaningful operational change for administrators and users who previously had to choose SAC at install time or accept a more cumbersome path to switch it off. Availability will be managed by Microsoft and will vary by device.
• Settings refinements: The Settings About page and the Settings home device info card were refreshed for b e and device specs. Loading performance and reliability improvements are also part of the package.
• Narrator and accessibility: Narrator gets expanded image descriptions and integration with Copilot on compatible Copilot+ devices; voice typing in File Explorer now works for renaming files. These accessibility changes will matter to users relying on assistive technologies.

---

How the feature rollout is happening (availability and channel notes)​

This update is distributed via the Release Preview Channel to Insiders as KB5079387 and is staged in a gradual rollout fashion. That means devices will see features appear over time, not all at once; Microsoft uses telemetry and staged rollouts to minimize regression risk for broad populations. The Release Preview packaging targets both Windows 11, version 24H2 (Build 26100) and version 25H2 (Build 26200) variants. If you’re an Insider and don’t see the features immediately, that’s expected.
WindowsForum community threads and internal previews show Insiders and testers already discussing the changes — many are excited about extreme refresh support and the gaming improvements, but some warn about compatibility wrinkles with certain external monitors and driver stacks. Early community reporting has documented both positive test cases and the familiar problems that come with complex display stacks.

---

Cross‑verification and what independent sources say​

• The Windows Insider release notes (the text Microsoft publishes for Release Preview pushes) summarize the feature list and explicitly call out monitor reporting above 1000 Hz, DRR extensions, Smart App Control toggling, HDR reliability fixes, and other settings/improvements. These items are the authoritative description of KB5079387’s scope. The release text has been mirrored across community channels and was summarized by several outlets covering Insiders.
• Neowin’s coverage called out Microsoft’s push into “extreme display refresh rate” support and described KB5079387 as widening the OS‑level refresh‑rate envelope while rolling out companion display and graphics improvements. That independent write‑up aligns closely with Microsoft’s Release Preview t around why this matters to end users.
• The DirectX/Windows documentation on Dynamic Refresh Rate provides the technical rationale and constraints for DRR and is the right canonical reference for how DRR is intended to behave (inking, scrolling, app classes, and interactions with VRR). The DirectX blog underscores the engineering tradeoffs Microsoft has already acknowledged with DRR and reinforces why the Windows display stack needs careful evolution to support broader scenarios.

Taken together, these sources corroborate the main claims in KB5079387: OS‑level handling for higher numeric refresh rates, expanded DRR behaviors, HDR/DisplayID fixes, and several UI/accessibility updates.

---

Deep technical analysis — strengths, limitations, and risks​

Strengths and potential benefits​

• Future‑proofing the display stack: Allowing monitors to report >1000 Hz is a forward‑looking change that removes an arbitrary OS ceiling and prepares Windows for niche but legitimate ultrahigh‑refresh deployments in esports measurement gear, capture devices, and experimental panels. This is a clean, low‑risk hardening of enumerations and should benefit OEMs and driver developers.
• Better battery behavior for USB4 docking: The finer power management with USB4 controllers when sleeping — while still delivering full performance when active — is a pragmatic improvement for modern laptop workflows that heavily rely on docked setups.
• Reduced fragmentation for game modes: Improvements aimed at lowering latency in windowed games and enabling Auto HDR/VRR there reduce the long‑standing necessity for exclusive full‑screen modes to get the best visuals and lowest latency. For streamers and creators who prefer windowed workflows, this is an important API/OS enhancement.
• Operation and admin flexibility: Making Smart App Control togglable without clean installs reduces friction for administrators and power users who want to trial or opt out of protections without reinstalling the OS. This is an operational win for IT.

Practical limitations and risks​

• Hardware and driver dependency: OS recognition of a reported refresh rate is just part of the chain. The display panel, monitor scaler/firmware, GPU driver, cable/connector bandwidth, and application must all align. Historically, Windows updates that expand display capabilities only realize real user benefit when GPU vendors and monitor manufacturers publish updated drivers and firmware. In short: expect device‑dependent outcomes.
• DRR granularity and caps: Past DRR behavior has shown Windows often uses conservative boosts (for example, many systems toggle between 60 Hz and 120 Hz even when a monitor can run at 144 Hz or higher). Early reports and community threads suggest DRR will not magically unlock every monitor’s maximum refresh rate for every scenario — Microsoft still chooses conservative targets for stability and battery life. Insiders have reported cases where DRR caps at 1refresh monitors, indicating policy and driver factors remain.
• Standby and monitor rediscovery regressions: The Windows display policy and monitor re‑enumeration after suspend/resume have caused user reports of refresh rates dropping unexpectedly after a monitor resumes from standby. These are long‑running pain points that can still surface after major display stack changes. Expect initial teething problems with some external monitors until vendors adjust firmware or Microsoft refines fallback logic.
• Staged rollout and telemetry gating: Because Microsoft stages the rollout, features may be present in a build but not enabled on all devices. This makes it harder for IT teams to predict when a specific machine will see a feature and complicates large‑scale testing plans unless you opt the entire pilot group into the Release Preview and validate at scale.
• Enterprise compatibility concerns: Anything touching the display/graphics stack is sensitive in enterprise imaging and driver‑managed fleets. Organizations should thoroughly test imaging workflows and ensure GPU drivers used in images are closely aligned to vendor recommendations. The Smart App Control toggle adds to manageability surface area — administrators must plan how the policy will be used and audited.

---

Recommended testing and deployment guidance (for enthusiasts and IT)​

If you manage devices or you’re an enthusiast who wants to test KB5079387, follow this practical checklist:

• Prepare
• Ensure you have a recent backup or a system image. Rollbacks in Release Preview can be straightforward but may require time.
• Collect current driver versions (GPU driver, monitor firmware if available), and note any custom monitor INF files or color‑management profiles.
• Update GPU drivers first
• Before installing the KB, update the GPU driver to the vendor’s latest Release Candidate or WHQL build that explicitly supports Windows 11 24H2/25H2. Many display behaviors are tied to driver logic; new OS capabilities often need matching driver support.
• Install KB5079387 on a pilot device
• Enroll a test machine in the Release Preview Channel (if you’re an Insider) and let the update arrive via Windows Update.
• Observe changes to Settings > System > Display > Advanced display. Look for new refresh‑rate enumeration and the Dynamic option where applicable.
• Validate DRR and VRR
• Test pointer interactions, inking, and scrolling in apps known to benefit from DRR (Settings, Office apps, Edge Canary with refresh‑boost flags).
• For gamers, test VRR behavior in a handful of titles and verify that games requesting exclusive VRR/full‑screen still get expected behavior.
• Test HDR and color workflows
• Use calibrated HDR content and monitor OSD options to validate HDR stability, especially on monitors previously showing DisplayID warnings.
• Monitor suspend/resume behavior
• Put monitors into standby and resume to confirm refresh‑rate persistence. If a monitor drops to 60 Hz after resume, gather logs and report through Feedback Hub. Community threads show this particular scenario is one to watch.
• Report and escalate
• When you find issues, collect Event Viewer logs and use Feedback Hub with detailed repro steps. For fleet issues, coordinate with GPU and monitor vendors for driver/firmware patches.

---

Troubleshooting quick tips​

• If your monitor doesn’t show expected higher refresh rates:
• Verify the cable and connector (DisplayPort 1.4/2.1 or HDMI 2.1 depending on target rates); older cables can constrain bandwidth.
• Confirm the monitor’s OSD isn’t locked to a lower refresh or that an overclock option must be enabled on the monitor itself.
• Update the GPU driver and, where available, the monitor firmware.
• Check Settings > System > Display > Advanced display to confirm Active Signal Mode vs. reported native modes.
• If DRR appears capped at 120 Hz:
• This may be intentional policy in Windows or driver behavior. Check vendor driver release notes and community discussions; test with an alternative driver version if possible.
• If HDR behaves oddly after the update:
• Reset color profiles and run HDR calibration tools (Microsoft has been shipping a Windows HDR Calibration app in preview channels). Also check for DisplayID warnings which the update explicitly targets.

---

Community signal and early reactions​

Windows enthusiasts on our forum and across Insider channels have been quick to test KB5079387. The community reaction is a mix of enthusiasm and cautious pragmatism: folks appreciate Microsoft removing artificial limits and improving inking/scrolling responsiveness, while some report idiosyncratic behavior with specific external monitors and driver combos (especially related to refresh persistence after suspend). These early conversations reflect a familiar pattern: OS teams extend platform capabilities, and vendor drivers and firmware must follow before broad, consistent user benefit is realized. Early community reporting and internal preview notes also highlight excitement about the Smart App Control toggle and the clearer Settings pages, which reduce friction for power users and admins.

---

Conclusion — what this means for users and IT​

KB5079387 represents a pragmatic, incremental step in Windows 11’s graphics and display roadmap. By removing arbitrary OS ceilings, expanding DRR behavior, hardening HDR and DisplayID handling, and adding real operational controls (like the SAC toggle), Microsoft is preparing the OS for both current high‑refresh workflows and likely future hardware innovations.
For gamers and creators, the most tangible near‑term wins are the windowed‑game optimizations and broader DRR responsiveness in UI and apps. For IT and administrators, the Smart App Control toggle and Settings refinements reduce friction and support cleaner device management. For hardware vendors and driver teams, the update is a call to action: align drivers and firmware to fully realize the OS improvements.
Caveat emptor: staged rollouts, driver dependencies, and legacy monitor behavior mean that this package will feel different depending on your hardware. Test in a controlled pilot, update drivers first, and be ready to report issues. If you’re an enthusiast running bleeding‑edge monitors or custom setups, KB5079387 is a welcome platform improvement — but it’s not a one‑click cure for every display quirk. The update sets foundations; the ecosystem has to build on them.
The release to Insiders as KB5079387 is underway; expect a phased appearance on your machines if you’re enrolled in the Release Preview Channel, and plan testing accordingly.

---

Source: Neowin Windows 11 gets extreme display refresh rate support and new features in KB5079387