Microsoft has confirmed a fix for a long-running Windows Insider issue that shows the wrong build number in the desktop watermark. The problem resurfaced after users installed update KB5073097 in recent Canary Channel builds.
Several testers noticed that the watermark displayed an outdated or base build number instead of the actual installed build. The mismatch created confusion for developers, testers, and IT admins who rely on accurate build information for validation and bug reporting.
A known issue appeared again in build 28020.1371, where the watermark continued to show incorrect data. Some experienced users pointed out that earlier Windows 10 builds behaved the same way, especially when cumulative updates changed internal build identifiers. Even so, many Insiders expected modern preview builds to reflect precise version information.
Microsoft reviewed the feedback and confirmed that it plans to correct the watermark behavior in upcoming preview releases. They did not announce an exact rollout date, but it expects the fix to arrive in future Dev and Beta Channel builds.
The bug does not affect system stability or performance. However, it creates unnecessary friction during testing. Developers often capture screenshots, submit bug reports, and verify regression behavior using visible build numbers. Incorrect watermarks slow down this process and increase reporting errors.
See also: Windows 11 Insider Preview Build 26220.7653 Brings UI Refresh, Faster Copilot, and Stability Fixes
The confirmation also arrives during a busy update cycle. Microsoft recently shipped KB5074109 and KB5073455 alongside KB5073097. Some users reported installation failures with KB5074109, which added pressure on Insider testing reliability. Microsoft continues to collect feedback and refine update quality across preview channels.
For now, Windows Insiders should expect accurate watermark information once Microsoft deploys the fix in a future build. Testers can continue submitting feedback through the Feedback Hub if the watermark issue persists after new updates land.
