Enable Bitlocker XTS-AES 256 Full Disk Encryption during OSD

I’m updating our TS for Windows 10 (1511) and wanted to take advantage the new encryption.
I had to change a few steps, import some keys, and use good old manage-bde, but it’s working, and at the end of the day, it is populating the keys into both AD & MBAM
Issues I ran into was getting it to use full disk encryption, instead of used space only, and getting it to use XTS-AES 256.  Hopefully you’ll find this useful.

We are using MBAM 2.5 SP1, ConfigMgr 2012R2 SP1 w/ MDT 2013 U2 Integrated.
Source information I used to help get this working: apppackagetips.blogspot.com & and idea about using Manage-Bde
Assumptions, you’ve already setup your partitions to support Bitlocker – More info here, and You’ve setup your TS to turn on and Activate the TPM Chip in the bios and you have NO “Pre-provision BitLocker” Steps enabled.  I had to disable both  Pre-provision steps to get this to do full disk encryption: 

TS Steps for our Enable Bitlocker Steps, this is near the end of the entire TS. (All of the steps I’ve set to continue on Error)

  1. “Stop MBAM Service” - Since we are using MBAM (which is installed in our actual image), the first step is stopping the MBAM Service (Net stop mbamagent)
  2. “Partition Drive for BitLocker” – This is a generic MDT step that I left in.  I have not tested to see if I can disable it, but for now, it’s working with it there. – This will cause TS to fail if not set to continue on Error
  3. “Enable XTS 256-bit Encryption” – This imports a registry file with settings needed to use XTS-AES 256 Encryption – Reg File lower in this blog (regedit /s XTS_256-bit.reg)
  4. “Apply MBAM Policy Settings” – This is another registry setting import for MBAM, I could merge the two, but kept them separate for simplicity (regedit /s MBAMSettings.reg)
  5. “Start MBAM Service” (Net start mbamagent)
  6. “Enable Bitlocker” – Generic TS Step – I found that this creates some of the required settings needed, but didn’t actually start the encryption – This will cause TS to fail if not set to continue on Error
  7. “Enable Bitlocker Manage-Bde” – This step actually was successful in starting the Encryption Process.  Until I added this step, encryption would not start automatically, and I had to manually start it post deployment. (manage-bde -on c: –RecoveryPassword)
  8. Restart computer.  This kicked in the encryption process.

Registry Files:
XTS_256-bit.reg (I export these settings from a current Windows 10 Client that had bitlocker setup how I wanted via GPO, info found here)

Windows Registry Editor Version 5.00





MBAM Settings: (You will need to export this from one of your current MBAM clients, to get the correct Registry data, but here is mine as example – your service endpoint strings will be completely different than the example, as well as other potential differences depending on your Security policy)

Windows Registry Editor Version 5.00



After OSD, and you’ve logged in, you should be able to confirm your settings: manage-bde –status

The computer remained on over the weekend, and I then tested recovery from AD & MBAM today… successfully:



Hope this is useful, I know it’s not really pretty, but it worked for me to get XTS-AES 256 encryption working on Windows 10 (1511), and populating AD & MBAM with the recovery keys.

As always, if you find a way to improve this, or have comments, please post your comments below.  I’m pretty good about getting back to you in a timely manner.

9 thoughts on “Enable Bitlocker XTS-AES 256 Full Disk Encryption during OSD

  • May 27, 2016 at 9:17 am

    Hey Gary, great article.

    Are you using MBAM integration with SCCM? I've been noticing a pattern where Windows 10 machines that use XTS-AES 256 are not appearing in the MBAM Supported Computers collection. All my machines that were upgraded from Windows 7 using AES 256 do appear int he collection.

    Strange considering the collection query doesn't look for anything related to encryption ciphers.

    Have you run across this as well?

    • May 27, 2016 at 10:16 am

      I have not integrated MBAM w/ ConfigMgr. I wasn't comfortable doing the integration at the time I setup MBAM, and to make life easier replacing my ConfigMgr server in the future, I kept them separated. I currently don't have any collections for bitlocker. If you figure it out with XTS-AES 256, please reply with your query, I'd like to see that.

  • May 28, 2016 at 6:19 am

    Hello Gary, this is realy a very nice article.

    How looks the compliance status of your encrypted machines in the MBAM Portal under the subcategory Reports? All my machine which are encrypted with XTS-AES-256 are not compliant with my MBAM-policies. The Portal does not recognize that the policy settings are XTS-AES-256. I'm very confused about that. Do you have an idea or solution about that problem?

    Regards Luke

  • May 25, 2017 at 10:55 am

    This is a very helpful article. In 1607 Microsoft has made it very hard to capture the TPMOwner password to the MBAM database. Have you successfully done this. Some of my research makes it seem that it is no longer necessary.

    • June 5, 2017 at 12:07 pm

      We do not capture that. I believe you are correct in that it is no longer needed. We have not needed it in our environment

  • September 15, 2017 at 11:40 am

    Hi - Excellent Article. Can we use the same step for the 1703 as well. How about using Invoke MBAM powershell script ? Since I am getting weird results. So we have the following in TS:
    1. Convert BIOS to UEFI
    2. Set Registry value for XTS_AES256
    3. Pre-provision Bitlocker
    4. Apply OS
    5. Persist TPM Owner with the script SaveWinPETpmOwnerAuth.wsf
    6. Apply Drivers/Apps
    7. Install MBAM with Dec 2016 Patches
    8. Invoke MBAM Script - Invoke-MbamClientDeployment.ps1

    After the OS is imaged and when i run the manage-bde -Status C: - I get the following
    BitLocker Version : 2.0
    Conversion Status: Used Space only Encrypted
    Encryption Method: XTS-AES 256
    Protection Status: Protection Off
    Lock Status: Unlocked
    Indentification Field: Unknown

    Not sure what is this all about

  • September 15, 2017 at 12:48 pm

    I see an MBAM error in the event viewer as An error occurred while sending encryption status data - Error Code -2143485933. What could be the possible reason ?


Leave a Reply

Your email address will not be published. Required fields are marked *