Technical Report: Multiple Reports of Progressive IPS Display Failures Potentially Associated with Windows 11 25H2 and 26H2

Microsoft does not currently list progressive lines, coloured bands, or refresh-rate-dependent distortion as a known Windows 11 25H2 or 26H2 issue, so the supported route is to submit instrumented Feedback Hub reports from affected devices and escalate the resulting feedback links through Microsoft Support. ^1^ ^2^

A Q&A post cannot itself register an engineering incident or confirm a common cause. The absence of a release-health entry does not invalidate the reports; it means that an OS-wide regression matching these symptoms has not yet been publicly acknowledged.

Submit an engineering-actionable report

Perform this on at least one affected computer while the fault is visible:

1. Press Win+F to open Feedback Hub, then sign in.
2. Search for an existing report matching the symptom and build.
   • If an accurate report exists, upvote it and add the affected hardware/build details.
   • If not, select Give feedback → Report a problem.
3. Use Display and graphics as the category—not Install and update, even if the problem began after an update. Correct categorization determines which diagnostics are collected and where the report is routed. ^3^
4. Select Recreate my problem/Record steps, start capture, reproduce the distortion by changing only the relevant refresh rate or VRR state, then stop capture.
5. Attach:
   • A photograph or video showing the physical panel.
   • A Windows screenshot taken while the problem is visible.
   • Exact Windows edition, version, OS build and installed KB.
   • GPU models and driver versions, including both adapters on hybrid-GPU laptops.
   • Monitor/laptop model and firmware version.
   • Connection path: direct HDMI/DisplayPort/USB-C, or dock/adapter.
   • Resolution, refresh rate, HDR and VRR state.
   • First occurrence date and whether it followed a Windows, driver, or firmware update.
   • Whether the artifact appears in BIOS/UEFI, the monitor’s own on-screen menu, Safe Mode, and a screen recording.
   • Minimal reproduction steps and frequency.

Feedback Hub supports screenshots, files, and recorded reproduction steps; these provide diagnostics that photographs and links to unrelated reports cannot provide. ^4^

Submit separate reports from materially different hardware configurations. Include the same distinctive title prefix, such as:

[IPS progressive lines investigation] Refresh-rate-dependent distortion – Windows 11 25H2 build xxxxx.xxxx

After submission, copy each Feedback Hub share link. Cross-reference the related links in every report so Microsoft can assess them as a possible cluster.

Establish whether Windows is in the failing path

Since cables, alternate computers, and graphics-driver reinstalls have already been tested in some reports, do not repeat those as blanket recommendations. Record these higher-value distinctions instead:

• Visible in BIOS/UEFI or the monitor’s own menu: Windows and its graphics stack are not rendering that image. Treat that individual device as a panel, timing-controller, firmware, or other hardware-path case.
• Absent before Windows loads but present after sign-in: Windows, the display driver, an application, or an active display feature remains in scope.
• Present in a Windows screenshot or screen recording viewed on another unaffected device: the artifact was generated before physical panel output, supporting a rendering/graphics-stack path.
• Visible only in a camera photograph, not in the screenshot/recording: the physical output link, monitor electronics, or panel remains more likely.
• Task Manager flickers or distorts with the rest of the desktop: Microsoft’s documented diagnostic points toward the display driver. If Task Manager remains unaffected, an incompatible application is more likely. ^5^

Do not describe lower refresh rates “confirming” a Windows defect. A symptom changing with refresh rate identifies a timing-sensitive condition but does not by itself distinguish the OS, driver, signalling path, monitor firmware, or panel electronics.

Escalate beyond Feedback Hub

For each affected home PC:

1. Open the Windows Get Help app.
2. Request Microsoft Support for Windows → Display and graphics.
3. Provide the Feedback Hub links and ask that the case be associated with a potential Windows graphics regression.
4. Supply a compact comparison table covering device model, panel, GPU, driver, OS build/KB, connection, refresh rate, HDR/VRR, first occurrence, and BIOS/screenshot results.

For organization-managed systems, open a business support case and provide the same package. Microsoft’s release-health pages identify Feedback Hub for update reports, Get Help/Microsoft Support for direct assistance, and business support for organizations. ^2^

Monitor both release-health pages after filing. The currently documented display-related 25H2/26H2 item concerns black screens or desktop-loading failures primarily on Azure Virtual Desktop hosts; its KIR and update resolution do not apply to progressive physical-panel lines or coloured bands. ^1^

References

1. Windows 11, version 25H2 known issues and notifications
2. Windows 11, version 26H2 known issues and notifications
3. Understand feedback categories and diagnostics
4. Deeper look at feedback
5. [Windows 11](https://support.microsoft.com/windows/hardware/display-graphics/troubleshoot-screen-flickering-in-windows)