Bea Beltran Tech 01.24.2023 21:Jan PM EST

Microsoft Suggests Temporary Fix for Unresponsive Windows Start Menu

Windows OS users with Windows 10 20H2, 21H2, and 22H2 have been experiencing issues with their Windows Start menu. This also goes for users with Windows 11 22H2, but Microsoft has issued a temporary fix as theta re working on a patch.

Issues with Windows

The company has already acknowledged the issue at hand, but there are still no permanent solutions as of right now. The areas in the operating system that might be affected along with the Start menu are Windows search and the Universal Windows Platform.

Reports say that Clickshare, which is used for sharing the screen of a Windows device wirelessly, is also not working. The affected users might have damaged registry keys or data, as mentioned in Bleeping Computer.

This could affect apps that use Microsoft Office's API to interact with Windows, Microsoft Office, Microsoft Outlook, or Outlook Calendar. Microsoft mentioned that the Windows Update might not be the cause and that it could be originating from an update to an affected app.

Windows' Solution

Microsoft is still investigating the issue and will assist customers and provide information in an update to the Windows health dashboard entry. But for now, users are advised to uninstall apps that integrate with Windows, Microsoft Office, Microsoft Outlook, or Outlook Calendar.

Microsoft also suggested that users might want to configure certain affected apps to open on demand instead of automatically operating on start-up. This could help prevent the issue from happening again.

To resolve issues with third-party processes like Clickshare that uses Office APIs, users can download scripts to fix the issue should it happen. Although, Windows warned that the scripts won't prevent the issue from happening again.

Users can then open a Powershell prompt under the affected user identity and run ".\FixUserShellFolderPermissions.ps1" after. If the registry keys are wiped out, users can run "FixUserShellFolderPermissions.ps1 -allprofiles" on an elevated Powershell prompt.

For applications that don't work, users might need to register certain shell packages by running the command "FixUserShellFolderPermissions.ps1 -register" from the affected user. Microsoft already knows about the issue and is working on it.

Other Issues

For Windows 10 versions 20H2, 21H2, and 22H2, other issues might include one with application shortcuts. It might not work from the Start menu or other locations when users are trying to run .exe files. Changes to Microsoft Defender might resolve the problem.

Taskbar elements might also flicker which will cause device instability, which affected OS Build 19045.2130. Users could fix the issue by using Known Issue Rollback or KIR, as advised by Microsoft on its website.

It has been confirmed that upon failure to install KB5012170, users might receive a 0x800f0922 error. The security update for Secure Boot DBX might fail to install. Errors might also occur in domain join processes when an account is created using a different identity to join the domain.

As for Windows 11 version 22H2, the conversion of texts in some languages might not work as intended. The languages affected include Japanese, Korean, and Chinese. Apps that require administrative privilege might not be installed as well when using provisioning packages (.PPKG).

Remote Desktop Services collection, RemoteApp, and Desktop Connection might also fail when using Remote Desktop Services Collection.