In preparation for the monthly Patch Tuesday updates, Microsoft traditionally offers preview versions of their operating systems to allow interested users to test upcoming features and changes. Recently, a preview update for Windows 11 version 22H2, named KB5028254, was released. While it aimed to provide users with an early glimpse of new features, it inadvertently caused problems in the OS. Microsoft has promptly addressed these issues, providing guidance to users affected by the update.
Start Menu Issue and Third-Party App Customization:
Following the installation of the KB5028254 update, several Windows 11 users reported a broken Start menu. Upon investigation, Microsoft determined that this problem only affected users who had installed third-party apps to customize their Windows installation. Specifically, users of ExplorerPatcher, available on GitHub, were impacted, but other third-party apps may also have been affected. ExplorerPatcher is designed to enhance the Windows working environment.
Microsoft's Approach and Workaround:
Since the issue solely pertains to users employing "unsupported" methods to customize their OS, Microsoft has taken a hands-off approach. The company has stated that it will not provide a workaround for this particular problem. Instead, it advises users to either uninstall third-party apps before downloading KB5028254 or contact the developer responsible for the app to implement a fix. The Start menu issue currently affects users of Windows 11 version 22H2 who have installed the preview update, but it could potentially impact more customers as the update becomes widely available next month.
Additional Codec Bug:
Apart from the Start menu issue, Microsoft also highlighted another bug in the recent preview update, KB5027303. This bug specifically affects apps, including webcams and cameras, using the WVC1 codec (VC-1) for video playback or recording. Unfortunately, there is no immediate fix for this problem, and users may need to rely on Microsoft's Known Issue Rollback (KIR) Windows servicing process. This process automatically uninstalls problematic updates within 24 hours on consumer and non-managed business devices. If the rollback does not occur automatically, a device restart might be necessary.
Rollback Mechanism for Enterprise Devices:
Microsoft acknowledges that enterprise devices managed by organizations require a different approach. These organizations need to implement the rollback mechanism by configuring a Group Policy. The Group Policy can be accessed through Computer Configuration > Administrative Templates. Depending on the current Windows version, one of the provided Group Policy downloads should be deployed.
Support and Expectations
Microsoft reassures users that issues in preview rollouts are normal and, in fact, expected. The company uses these early releases to gather valuable user feedback and resolve bugs before a broader release through Patch Tuesday updates. While Microsoft takes no responsibility for issues caused by third-party UI customization apps, it is actively addressing the video codec problem across supported Windows versions.
