The recent preview update KB5120998, released by Microsoft on August 27, 2026, for Windows 11 versions 24H2 and 25H2, has stirred a wave of discontent among users. Following the installation of this update, reports have surfaced detailing a range of issues, including erratic behavior of the mouse pointer and the disappearance of desktop backgrounds. Notably, Microsoft has acknowledged that these problems seem to be confined to non-English versions of Windows 11, raising questions about the underlying coding practices employed by the tech giant.
The articles linked below to my German blog may be read by the blog’s built-in translation feature (see the translate feature in the upper right corner of the website).
My Review of the Issues with KB5120998
In my German blog post titled “Windows 11 24H2 – 25H2: Preview Update KB5120998,” I provided a comprehensive overview of the fixes, new features, and changes introduced in this latest update. However, the feedback from my readers has revealed a troubling array of complications. For instance, one user on BlueSky reported that the “AlwaysOn VPN” feature ceased to function post-update. Additionally, there are concerns surrounding Microsoft Defender, which erroneously indicates that it has been disabled, although this issue is not directly linked to the recent update. Such a plethora of problems is disheartening, especially considering Microsoft’s commitment to enhancing the quality of Windows 11 in the latter half of 2026.
Microsoft’s Attempts to Explain the Issues
In response to the growing concerns, Microsoft has published several support articles addressing the “Known Issues” section of the Windows 11 24H2 and 25H2 Release Health Dashboard. One article, titled “Desktop background settings are lost or reset on some devices,” explains the occurrence of a “black desktop background.” According to Microsoft, certain desktop settings fail to load correctly, resulting in a default black background when users attempt to restore their customized settings.
Another article, “Mouse customization is reset on non-English Windows devices,” reveals that the mouse pointer issues are exclusive to non-English versions of Windows 11. Users are unable to reassign their mouse cursor settings, as these customizations revert to default configurations. Microsoft attributes these glitches to code components utilized in non-English installations, indicating that the settings cannot be loaded properly, leading to a fallback to default values.
A Look Behind the Scenes
While Microsoft provides some clarity, the vagueness surrounding the specific nature of these bugs leaves much to be desired. The revelation that certain code segments fail to load, forcing Windows 11 to revert to default settings, raises concerns about the thoroughness of testing conducted in Redmond. The fact that the mouse pointer issue is limited to non-English versions suggests a potential oversight, possibly due to reliance on telemetry and AI-driven processes that may not have been rigorously vetted.
Delving deeper into the matter, I propose that the “glitches” observed may stem from what is often referred to as vibe coding—AI-generated code that lacks clarity and understanding for the developers. This notion is further supported by a comment from a blog reader, mihi, who speculated that the problems could be attributed to translation issues within the registry. The reader noted that registry keys, which previously held specific values, were altered post-update, leading to discrepancies in functionality.
Registry keys have been translated. The wallpaper, which has long been stored at:
HKEYCURRENTUSERControl PanelDesktopWallPaper
will be stored [in a German Windows 11] at the following location after the update:HKEYCURRENTUSERControl PanelDesktopHintergrundbildAlthough the default mouse pointer and its settings are still stored under:
HKEYCURRENTUSERControl PanelCursorsArrowbut they are read from this registry key:
HKEYCURRENTUSERControl PanelCursorsPfeil
The reader suggested that by manually adjusting these registry keys, users could restore their mouse pointers to normal functionality. This insight aligns with Microsoft’s acknowledgment that the mouse cursor issues are confined to non-English versions, reinforcing the idea that coding practices may have faltered in the face of AI-generated solutions. As the landscape of software development continues to evolve, the implications of relying on AI for coding and testing warrant careful consideration, particularly as we navigate the complexities of modern operating systems like Windows 11.
