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.”
TechNet:
The problem appears to be limited to people who have hard drives that have hardware encryption built-in (so called Opal drives I think). It does not apply to people using bitlocker on normal drives with software encryption.
Hey all, found this source article on NeoWin.Various users have reported issues which prevent systems from being encrypted, which affect Microsoft's BitLocker encryption technology in the latest build of Windows 10. The issues reportedly occur only with clean installs of the Windows 10 November update, otherwise known as build 10586.
Microsoft TechNet Forum user 'nesoi' reports that after a clean install of the November update, BitLocker cannot be enabled in Windows 10 because the wizard to enable the feature will give a 'parameter is incorrect' error message. The user states that BitLocker willwork for users who first enable the feature in the RTM version of Windows 10 (build 10240) and then upgrade to the November update (build 10586). However, if BitLocker is later disabled—either by the user or when the operating system's reset feature is used with the 'Keep Nothing' option—the error message will appear again when users attempt to re-encrypt their systems.
Reddit users have described similar experiences and have speculated that the issues are caused by the changes made to BitLocker in the latest build of Windows 10, and that they may not dependent on hardware.
While Microsoft has yet to officially address these issues with BitLocker, they may be related to the company's recent decision to inexplicably pull its Media Creation Tool for the November update. Affected users should submit feedback to the company to help ensure that the problems will be resolved.
Issues in Windows 10 November update prevent BitLocker encryption from being enabled
I know there is another thread here started by user Cluster Head stating that MS pulled the November update due to "activation issues" but now with this post from NeoWin its hard to tell what is going on.
Link to Cluster Head's thread here:
MS Might Have Removed Win 10 TH2 ISOs Because of Activation Issues - Windows 10 blog
