COMPUTERS WITH solid state drives (SSDs) are suffering at the hands of Microsoft's Windows 10 Anniversary Update after reports that the operating system is freezing.
The borkage has all the hallmarks of a driver problem given that it doesn't occur in Safe Mode, and seems to affect systems where apps and data are on a different drive to the operating system.
There's no fix for this at the moment (Microsoft said that it is working on it) but there are some workarounds.
No. Wait. Not so much 'workarounds' as 'give-ups', as the instructions currently being provided involve rolling back to the pre-Anniversary version.
This will be particularly irritating if you have a small SSD drive and have already wiped the rollback partition. Echoes of Updategate.
Our question is this: given that the Anniversary Update has been available for months via the Windows Insider programme, how does something as significant as this sneak through to the stable release?
As more and more people upgrade to SSDs, which are tumbling in price, and with even smaller laptops having room for multiple drives in the form of mSATA or M.2, surely someone must have had this problem?
Or could this be the same bug that is holding up the release of Kevin's Windows 10 Mobile Anniversary Update? Add an SD card, bork your phone. It's quite possible.
At the moment, you can roll back (if the files are still there) using the Recovery Console or the settings in Safe Mode.
In a rare act of defending Microsoft, we should point out that the house Windows 10 lappy with a brand new Crucial MX300 drive is giving us absolutely no hassle at all, despite some commenting that they're having BSODs and temporary lock-ups even on a single drive, so it's not a universal thing.
Definitely sounds like a driver conflict to us. µ
But it keeps the juicy details firmly under wraps
And Sonny and Cher is on the radio
Gets its post-Windows 7 towel on the sun-lounger