Windows 10 Anniversary Update freezing on you? Microsoft is looking into it.

Have you encountered problems with your computer freezing since you installed the Windows 10 Anniversary Update? If so, you’re not alone. And while there’s no proper fix for the issue yet, Microsoft is aware of the problem and are addressing it.


While the response from users has been generally positive, many are reporting that their updated PCs have started to freeze randomly.  According to a thread started by a Microsoft rep and posted on the company’s discussion forums, the freezing issue occurs on machines “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.


The freezing issue became apparent shortly after Microsoft released the Windows 10 Anniversary Update at the beginning of this month. Neowin first reported on this issue August 6 and pointed to a Reddit thread that had over 600 comments from users who encountered the freezes. That thread now has 883 comments as of this writing.


Although Microsoft is looking into what’s causing this freeze-inducing bug, it doesn’t have a patch yet. In the meantime, you can roll back to an earlier build of Windows 10 as a workaround, the company notes.   For full instructions, and for further updates on this issue, visit the thread on the Windows Club forum.


I am guessing Microsoft realized it has been causing so many issues as Microsoft has now made their Anniversary Update a manual download, originally when you check for updates they would automatically download and then install their new release.


We ask for your patience while we continue our investigation and please check back on this thread for an update.

Actify have reached out to Microsoft for help to fix this, but have not yet received a response, nor has Microsoft released any updates to Windows 10. We understand the urgency to resolve this problem and our development team has been working hard to create a fix for this issue and have managed to find a solution. See the update