Microsoft fixes bug behind Windows 10 freezing, desktop issues

Microsoft has fixed a known issue that triggers errors and temporarily causes the taskbar and desktop to disappear on Windows 10 systems.

The company has also linked the same issue to instances where user devices stop responding to input and freeze.

“You may encounter an error in which the desktop or taskbar may disappear momentarily, or your device may become unresponsive,” Microsoft explains on the Windows Health Dashboard.

The list of affected Windows platforms includes the following client versions: Windows 10 version 20H2, Windows 10 version 21H1, Windows 10 version 21H2, and Windows 10 version 22H2.

Microsoft suggests restarting affected devices to work around disappearing desktop or taskbar and system freezing issues.

Resolved via restoring known issues

Microsoft has also offered a fix for the problem through the Windows Known Issue Rollback (KIR) servicing feature which allows Redmond to roll back buggy non-security fixes deployed through Windows Update.

KIR patches typically automatically push to all affected devices within 24 hours, with Microsoft advising affected users to reboot systems to expedite deployment.

However, IT administrators will need to install and configure special Group Policy associated with the Windows versions of the affected systems to resolve the issue on corporate-managed Windows devices. You can download Group Policy for Windows 10 20H2 and later from here.

After running the downloaded MSI installer, administrators must navigate to Local Computer Policy > Computer Configuration > Administrative Templates using the Group Policy Editor on their domain controller to select the version of Windows that they want to target to deploy the KIR patch.

You can find more information about deploying and configuring KIR Group Policies on a hybrid Azure AD or AD DS domain using Group Policy on the Microsoft support website.

Over the weekend, Redmond also fixed Windows Kerberos authentication and Windows DirectAccess connectivity issues triggered by the November and October updates.

Comments are closed.