Windows 10: Upgrade Hardware Lose Win10 Pro and Bitlocker?

I purchased Win 10 Pro with bitlocker for my current laptop. If I buy a new laptop with Win 11 Home will I have to upgrade again to get the full version of bitlocker? Cost?

:)

 

Bitlocker in Windows 10 without TPM

As others here, I have my Win8.1 C: drive encrypted without a TPM and with a password. I am still unsure whether to upgrade to Win10. Your posts:

• Told how to enable Bitlocker on Windows 10
• Seemed limited to the BETA version of Windows 10

QUESTIONS:

• Can I simply upgrade to Win10 without decrypting my C: drive AND still use the same password on Bitlocker?
• Can you confirm that Bitlocker WILL NOT revert to the default Bitlocker settings during the upgrade?
• Will everything work as in your post on the production Win10 upgrade as on the trial versions?

Having to worry about losing a thumbdrive makes me quite uneasy--especially on the road. In the event of theft, the thumbdrive would likely be with the laptop; thus, obviating the reason for using Bitlocker in the first place.

The following points have given me concerns about upgrading to Win10:

From the Win10 Specifications Page:

•BitLocker To Go requires a USB flash drive (Windows 10 Pro only).

•BitLocker requires either Trusted Platform Module (TPM) 1.2, TPM 2.0 or a

USB flash drive (Windows 10 Pro and Windows 10 Enterprise only).

Did the post "kennethrallen replied on August 1, 2015S, See post history" relate to a removable drive; did Win10 incorrectly interpret the drive as removable because it was encrypted; or was the problem apparently something else?

Thanks

DJ

 

Win10 Pro Bitlocker on by default

Can't access my laptop.

Is it possible that after windows 10 pro installation bitlocker is on? Could it depend what is the source of win10 or the laptop's manufacturer? It seems that in our Lenovo Thinkpad T570 bitlocker was on when we bought it.

Or could it be that some Lenovo program turns bitlocker on without a notice during installation?

 

BitLocker hardware encryption cannot be activated on Win10 10586/1511

Hey,

I'm having trouble enabling hardware encryption with BitLocker using Windows 10 build 10586 on a clean install with a Samsung 850 SSD. The encryption worked flawlessly before on build 10240.

I've spent hours and attempted multiple solutions and made several tests.

As mentioned, on the same machine, if clean installing build 10240 (RTM, before November update) right now, the encryption works.

I have UEFI on with Legacy/CSM off, Fast Boot on, Secure Boot on, and a clean GPT installation after using the 'diskpart clean' command.

As always, it's required to change a group policy to allow additional authentication at startup. I did that.

On a clean installation of build 10586, the wizard will say 'parameter is incorrect' when attempting to start encryption.

Microsoft did announce some BitLocker-related changes for build 10586: What's new in Windows 10, versions 1507 and 1511 (Windows 10) - What's new in Windows | Microsoft Docs

There are also new group policies added. I've tried all combinations. They now allow you to try and force a specific encryption cipher. Samsung uses XES-AES256. I tried forcing that (as well as all other combinations) but the same error returns.

Now, here's where it gets interesting, and possibly why no reports about this have surfaced yet:
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.

tl;dr: Hardware encryption via BitLocker on build 10586 cannot be enabled on a clean install. Currently-known workaround is installing 10240, encrypting it, then upgrading to 10586.

Any solutions would be appreciated, thanks!