Windows 11 users testing Microsoft’s latest optional update should pause before rolling it out broadly. Reports around KB5120998 indicate that the update can change mouse cursor personalization settings, including size, color, and custom cursor schemes. Microsoft has acknowledged that it has received reports and is investigating, according to Windows Latest’s coverage of the issue.

The update is notable because it is not a small maintenance release. KB5120998 is described as one of the larger Windows 11 updates of the year, bringing interface changes such as Start menu, taskbar, search, and File Explorer improvements. But for administrators and enthusiasts, the immediate lesson is familiar: optional Windows updates can still introduce user-facing regressions, even when they are offered to production PCs rather than Insider preview channels.

What is happening with KB5120998?

Windows Latest reports that KB5120998, released on August 27, 2026, moves Windows 11 systems to Build 26200.9278 on version 25H2 and Build 26100.9278 on version 24H2. After installation, some users have seen their cursor settings revert or change unexpectedly.

The symptoms are not identical for everyone. In some cases, the pointer disappears or becomes difficult to see. In others, users report a cursor that suddenly appears much larger or smaller than configured. Custom schemes and animations may revert to standard settings, and cursor colors can also change. For accessibility users who deliberately configure a high-contrast or enlarged pointer, that kind of reset is more than a cosmetic annoyance.

A distinctive operational takeaway is this: treat the update as a cursor personalization policy check before broad deployment. If your organization relies on managed accessibility settings, kiosk configurations, remote-support workflows, or user-specific pointer profiles, this bug deserves testing before KB5120998 reaches those machines.

Why this matters for IT teams

Mouse cursor settings sound minor until they break someone’s workflow. A pointer that is too large can obscure interface elements. A pointer that is too small or unexpectedly white on a light background can slow down users with visual accessibility needs. A missing or unreliable cursor can make a system feel unusable even when the operating system is otherwise running.

For IT departments, the larger concern is confidence in update rings. Optional Windows updates are often used by power users, pilot groups, and administrators who want early access to non-security fixes before the following Patch Tuesday. That makes them valuable, but it also means they should be treated as a controlled deployment stage rather than an automatic “safe to install everywhere” signal.

Because KB5120998 is optional, most environments can afford to wait. If you use Windows Update for Business, Intune, WSUS, or a third-party patching tool, consider holding this release in testing until Microsoft publishes a clearer root cause or mitigation. If the update has already been approved for pilot devices, ask testers specifically about cursor behavior rather than waiting for a vague “the computer looks wrong” ticket.

What affected users can try

The most practical mitigation reported so far is uninstalling KB5120998. Windows Latest says affected users have found that removing the update resolves the cursor problem, while common repair steps such as resetting cursor settings or running system repair commands may not stick.

On a typical Windows 11 PC, users can check Settings > Windows Update > Update history > Uninstall updates, then look for KB5120998 and remove it. Because this is an optional update, uninstalling it should not remove the security fixes delivered in the most recent Patch Tuesday update. That distinction is important: users should not respond to a pointer issue by broadly disabling security updates or rolling back unrelated cumulative fixes unless an administrator has validated the impact.

After uninstalling, reboot the device and confirm that pointer size, color, and scheme settings remain stable. If the cursor is managed through accessibility policies or device configuration profiles, verify that those policies still apply after the rollback.

Guidance for enthusiasts and early adopters

If you installed KB5120998 to try the latest Windows 11 interface changes and your cursor is behaving normally, you do not necessarily need to panic. But it is wise to document your current pointer settings and keep a rollback path available. Optional updates can vary by hardware, driver stack, and user configuration, so a bug may appear only on some devices.

If you have not installed the update yet, the safer move is to wait for Microsoft’s follow-up. The new Start menu and taskbar changes may be interesting, but they are unlikely to justify disruption on a primary work machine. Enthusiasts who still want to test should do so on a secondary PC or a device where a quick uninstall will not interrupt work.

Bottom line

KB5120998 is a reminder that Windows servicing is not just about whether a machine boots after an update. User experience settings, especially accessibility-related settings, are part of production readiness. Until Microsoft finishes investigating the cursor personalization bug, organizations should keep this optional update in pilot rings, watch for official release-note changes, and prepare a simple uninstall procedure for affected users.

Source: Windows Latest source