Windows 10 Anniversary Update Causes Freezing Issues For Some

If you downloaded the Windows 10 Anniversary Update, you may be experiencing issues as I type this. Specifically, you might be seeing short term freezing of the PC that has the update on this. That is you’ll be doing something and then the PC will freeze for a few minutes before return to “normal.”

This apparently is a bug as Microsoft has confirmed the bug in a blog post which can be found here

“Microsoft has received a small number of reports of Windows 10 freezing after installing the Anniversary Update on systems with the operating system stored on a solid-state drive (SSD) and apps and data stored on a separate drive. This issue does not occur when starting Windows 10 in Safe Mode. If you are experiencing this issue, we will be providing updates to this thread… We ask for your patience while we continue our investigation and please check back on this thread for an update.”

Until Microsoft gets around to fixing this, here’s what you can do to not be the next victim:

  • Don’t update: The best solutions are the easiest ones. If this update hasn’t hit your PC yet, don’t let it do so. Go to Settings > Update & Security > Windows Update > Advanced Options > Defer Upgrades to avoid the update for now.
  • Roll things back to a known working state: There’s a little known feature of Windows 10 that allows you to roll things back to a known working state that can get you up and running if the update already hit your PC and caused it to be wonky. Navigate to Update & Security, click to view Update History followed by Recovery Options, then follow the prompt to Get Started. From here you are given the option to keep all of your files, or remove absolutely everything. Note that keeping your files removes all apps and settings too, but it’s a small price to pay when compared against the Anniversary Update causing issues.
  • Go back to an earlier build: Similar to the roll back, this puts you back to an earlier working build of Windows 10. Go to Update & Security > Update History > Recovery Options > Go back to an earlier build > Get Started. Here’s the catch, you have a 10 day window to do this. So this may not be an option for all. But it is worth trying.

Beyond these three suggestions, users who are affected by this bug may simply have to wait for the folks in Redmond to fix this. Pity.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: