Is this the reason Windows 10 TH2 was removed?
Windows 10 Threshold 2 keeps making headlines these days, but not necessarily thanks to performance improvements that it delivers to computers already updated to the latest OS.
After the company pulled the plug on Threshold 2 ISOs a few days ago, users have come across another important bug, this time affecting BitLocker encryption.
Neowin points to a TechNet forum discussion where users claim that, in most of the cases, if BitLocker encryption wasn’t enabled in the RTM version before installing Threshold 2, there’s no chance of getting it to work after deploying the new release.
One of the users whose computers got impacted by the BitLocker issue explains in a post:
“If you enable the encryption on build 10240, and then upgrade to 10586, the encryption will remain and will work properly on build 10586. If you then attempt to ‘Reset this PC,’ and choose the ‘keep nothing’ option, it will warn you that bitlocker will be disabled. Once it's done cleaning, if you attempt to enable encryption, it will again show the error. Even if you don't reset the PC, but simply disable Bitlocker on 10586 and then attempt to re-enable it, it will no longer work.”