Microsoft has acknowledged that a recent Windows 11 update can break mouse cursor personalization for some users, adding another reason for administrators and power users to be cautious with late-August update rollouts. The issue is tied to Windows 11 KB5120998, released on August 27, 2026, which moved systems to builds 26200.9168 and 26100.9168. According to reporting from Windows Latest, the update brought several long-requested usability improvements, but it is also associated with cursor problems, Office app crashes on ARM-based PCs, and user reports of wallpapers resetting after reboot.

For home users, the visible symptom may simply be an annoying pointer that looks wrong or refuses to keep custom settings. For IT teams, however, the practical takeaway is broader: treat KB5120998 as a staged deployment risk, not a routine cosmetic update. Cursor behavior affects accessibility, multi-monitor workflows, remote support sessions, and user confidence after patching. If your organization supports non-English Windows installations, secondary language packs, customized pointer schemes, or accessibility-driven cursor sizing, this bug deserves attention before broad deployment.

What Microsoft has confirmed

Microsoft has reportedly narrowed the cursor issue to code components used in non-English Windows installations. In affected locales, cursor settings may fail to load and Windows falls back to default values instead. The important operational detail is that manually changing the cursor style, size, or color may not stick, because the problem prevents the settings from loading correctly in the first place.

That distinction matters for support desks. If a user reports that the cursor reverts after restart, appears oversized, switches color unexpectedly, or ignores personalization changes, repeated attempts to reapply the same setting may waste time. The better first step is to check whether KB5120998 is installed, whether the device is using a non-English Windows display language, and whether additional language packs or keyboard layouts are present.

Windows Latest also notes reports from users outside the narrowest interpretation of Microsoft’s explanation, including systems that may have secondary language or input configurations. That does not prove every language-related setup is affected, but it is enough to justify extra testing in multilingual environments.

Other issues administrators should track

The same Windows Latest report highlights two other problem areas. Microsoft has also confirmed that Microsoft Teams and the new Outlook for Windows may fail to launch or close unexpectedly on some ARM-based devices after Windows security updates released on or after August 11, 2026, including KB5121003. A fix is expected in a future update cycle, likely aligned with the September 2026 Patch Tuesday timeframe.

The third issue is less settled: wallpaper resets after restart. Windows Latest says it has seen multiple reports of desktop backgrounds disappearing, resetting, or leaving users with a black background until they manually choose a wallpaper again. As of the report, Microsoft had not yet confirmed that wallpaper behavior as a known issue. Administrators should therefore treat wallpaper complaints as credible field reports, but document them carefully rather than assuming they are officially acknowledged.

Recommended response for IT teams

Organizations that use deployment rings should keep KB5120998 in a pilot or limited rollout phase until they have tested the affected scenarios. A practical validation set should include at least one English-only device, one non-English Windows installation, one device with additional language packs or keyboard layouts, and any accessibility configuration that depends on larger or high-contrast cursors.

If users are already affected, collect a short incident record before removing anything: Windows build number, installed update history, display language, regional format, keyboard layouts, cursor scheme, pointer size, and whether wallpaper settings are also resetting. This information will help distinguish a known update regression from profile corruption, third-party customization tools, or graphics driver problems.

For managed fleets, consider pausing expansion of the update to broad production groups while allowing security policy owners to weigh the risk of delay. If the cursor problem materially affects accessibility or productivity, uninstalling the update on impacted machines may be more reasonable than repeated local troubleshooting. However, removal decisions should follow your organization’s patch governance process, especially where security fixes are bundled with quality updates.

Guidance for Windows enthusiasts

Individual Windows users should avoid drastic fixes such as reinstalling graphics drivers, deleting mouse devices, or resetting Windows unless there is evidence of a separate hardware or driver failure. First, check Windows Update history and confirm whether KB5120998 is present. Then review language and keyboard settings, especially if you use multiple input languages.

If the pointer becomes unusable or accessibility settings no longer apply, rolling back the update may be the most direct workaround until Microsoft ships a fix. Before doing so, save screenshots or notes about the symptoms, because those details can be useful when filing feedback through Feedback Hub or discussing the issue with support.

Bottom line

KB5120998 appears to be a mixed release: it introduces useful Windows 11 interface changes, but it also creates a real support concern for cursor personalization in at least some language configurations. Microsoft has acknowledged the cursor regression and a separate ARM Office app crash issue, while wallpaper resets remain unconfirmed. Until fixes arrive, the safest approach is controlled rollout, targeted testing, and clear support guidance for users who find that their cursor settings no longer behave as expected.

Source: Windows Latest source