When you purchase through links on our site, we may earn an affiliate commission.Heres how it works.
While the problem could prove irritating, it was blown out of proportion by some outlets.
A previous article with a clickbait title by TechRadar incorrectly framed this bug as something out of the ordinary.
That, of course, was never the case.
Microsoft acknowledged the bug, shared a mitigation swiftly, and worked on a permanent fix for the issue.
That solution is now here.
Microsoft now marks the bug as “Resolved” on itswebsite.
This fix is part of the KB5027303 update that brings systems to Windows 11 Build 22621.1928.
It’s also available through theMicrosoft Update Catalog.
Alternatively, you’re able to wait until the update ships next month.
Preview updates can have bugs, so it’s probably best to wait a couple of weeks.
While the bug was fixable, it did take Microsoft roughly six months to figure out a permanent solution.
Reports of the issue first appeared in January 2023.
Iaddressed the false reportswhen they first emerged, so I won’t rehash the situation in full.
