Windows 10 KB3176938 fixes the freezing bug

Microsoft has finally fixed a very annoying bug that was brought along with the Windows 10 Anniversary Update. This bug was causing computers to freeze at random times after logging in. The Windows 10 Anniversary Update was released on August 2, 2016, but Microsoft officially acknowledged the bug in the middle of August.

It took about two weeks for Microsoft to fix this bug, as the Windows 10 cumulative update KB3176938 was released on August 31, 2016. Microsoft is now suggesting Windows 10 users who downgraded to a previous Windows version to install the Windows 10 Anniversary Update once again, as the issue has now been fixed.

After the launch of the Anniversary Update for Windows 10, Microsoft received a small number of reports of Windows 10 freezing when signing into Windows after installing the Anniversary Update. With the help of users and MVP’s who posted on this thread an investigation determined that a small fraction of users who had moved app information to a second logical drive could encounter this issue.

According to Microsoft, this patch will be automatically downloaded when installing the Windows 10 Anniversary Update. If you are just upgrading to this major update right now you don’t have to worry about the Windows 10 cumulative update KB3176938 as it is now included in the update package.

While the bug should no longer be present on the infected systems, Microsoft claims that there are still a good amount of users who may continue to experience the freezing problems.

If your computer runs Windows 10 and you are experiencing system freezes, we suggest you to boot the computer in Safe Mode with Networking and head to Settings >Update & Security >Windows Update >Check for updates. Once the update is installed, restart the computer and the freeze issues should be fixed.

RELATED STORIES TO CHECK OUT:

Tags:




  • Bryan Merrill

    My computer is still stuck at the lock screen when coming out of sleep, despite doing all of the latest updates. Looks like Microsoft has some work to do still. Rolling back to the previous build yet again….