Microsoft has introduced a Known Issue Rollback (KIR) aimed at users grappling with the complications stemming from the KB5043145 build of Windows 11. This non-security preview update, released in September 2024, has cast a shadow over the anticipated launch of Windows 11 24H2. While many users have navigated the update without incident, others have encountered a series of frustrating challenges.
Addressing User Concerns
Despite the widespread issues, Microsoft has remained relatively tight-lipped regarding the underlying causes of the problems. Users have reported a range of malfunctions, including:
- Frequent device reboots
- Crashes characterized by green or blue screens
- Access to the Automatic Repair tool without resolution
- Complications with the Windows Subsystem for Linux 2
- Problems with USB connections and Wi-Fi
In acknowledgment of the difficulties associated with the updates for Windows 22H2 and 23H2, Microsoft has rolled out a workaround in the form of a KIR. This innovative approach allows the tech giant to swiftly revert a specific fix back to its prior state if a critical regression is identified, without necessitating the uninstallation of the entire update.
Microsoft has indicated that users with non-managed devices, such as personal computers, may need to wait up to 24 hours for the resolution to take effect. To expedite the process, the company suggests that users restart their devices, a recommendation that echoes the classic tech troubleshooting mantra of simply turning it off and on again.
For administrators managing devices within an organization, Microsoft has also made a Group Policy available, providing additional support for those navigating these challenges.
As KB5043145 is classified as an optional non-security preview update, users are advised to exercise caution and consider postponing the installation for the time being. Reports have surfaced indicating that Microsoft may have paused the rollout, yet the company’s UK communications team appears to be as uncertain as the customers regarding the future of this patch.
