Microsoft is investigating reports that the optional Windows 11 update KB5120998, released August 27, 2026, is breaking mouse cursor personalization and causing desktop wallpapers to turn black. While the update introduces highly requested taskbar and search customizations, affected users must currently uninstall the update to restore system stability.
For users who prioritize the latest features, the August 27 update was a significant milestone. It officially moved several customization tools from the Windows Insider program to the general public, including the ability to resize and move the taskbar and various improvements to Windows Search. However, these additions arrived alongside a set of bugs that disrupt the basic user interface.
KB5120998 Cursor and Wallpaper Glitches
The most disruptive issue involves the mouse cursor. Users have reported that the cursor either disappears entirely or manifests in erratic sizes—appearing either enormously large or annoyingly small. In other instances, the cursor simply reverts to default settings, ignoring any personalized color or size preferences the user had previously set.
“Microsoft has received reports indicating that mouse cursor personalization settings are being changed or reverted to certain standard settings. This occurs following installation of Windows updates released August 27 2026 (KB5120998) and later.”
Microsoft, via Lifehacker
Beyond the cursor, the update has triggered a persistent wallpaper bug. Even when a user manually changes the wallpaper, the screen often reverts to black immediately upon the next system restart.
Because these issues affect the primary ways users interact with their machines, the current recommendation is to roll back the update.
How to Roll Back the August 27 Update
Since KB5120998 was an optional update, removing it does not strip the system of critical security patches.
- Open Settings
- Navigate to Windows Update
- Select Update History
- Click Uninstall updates
- Locate KB5120998 and select Uninstall
Reports indicate that this process successfully returns the cursor to normal and resolves the black wallpaper glitch. Until Microsoft releases a formal patch, this manual rollback is the only verified solution.
Broader Update Instability and Cloud-Initiated Recovery
The cursor issues are part of a wider pattern of instability in recent Windows 11 releases. For example, a separate update, KB5121003, has been linked to crashes in multiplayer games such as The Finals, Marvel Tōkon: Fighting Souls, and Arc Raiders. In the case of Arc Raiders, the developer Embark identified the crash as being related to a change in the inpoutx64.sys file.
To combat this cycle of “broken” updates, Microsoft is deploying a new system called Cloud-Initiated Driver Recovery (CIDR). This feature allows Microsoft to remotely roll back a faulty driver to a known-good version without requiring any action from the user or the original equipment manufacturer (OEM). The process is triggered via the Hardware Dev Center (HDC) Driver Shiproom and delivered through the existing Windows Update pipeline.
While CIDR is a significant shift toward automated maintenance, it only applies to drivers distributed via Windows Update. It does not solve the broader OS-level bugs found in updates like KB5120998, which require a full update uninstall rather than a simple driver rollback.
The Tradeoff Between Features and Stability
The current situation highlights a recurring tension in Windows 11’s deployment strategy. By releasing highly anticipated features—like taskbar resizing—through optional updates, Microsoft provides a pathway for enthusiasts to get new tools early. However, the fact that these “optional” updates can break fundamental UI elements like the mouse cursor suggests a gap in the testing phase for diverse hardware configurations.
The introduction of CIDR suggests Microsoft is aware that manual troubleshooting is a primary pain point for users. By moving toward a cloud-managed recovery model, the company is attempting to reduce the blue screen spiral
and the reliance on users to manually navigate the Device Manager to fix driver-related failures.
Until the automated recovery systems are fully integrated and a patch for KB5120998 is released, the safest path for users is to avoid optional updates until they have been vetted by the community. For those already affected, the uninstall process remains the only way to regain a functional cursor and a visible desktop.
