MBAM version chart


Its Rafal Sosnowski from Microsoft Dubai Security PFE Team. Some time ago I put together all versions of MBAM (Microsoft Bitlocker Administration and Monitoring) tool into one table. Small disclaimer: It is based on what I have seen in the wild and is not official information from Product Group.


Version Product
1.0.1237.1 MBAM 1.0
1.0.2001.1 MBAM 1.0 R1
1.0.2010.1 MBAM 1.0 R1 with hotfix (KB2724074 for client)
2.0.5301.1 MBAM 2.0 MBAM 2.0 SP1 MBAM 2.5 MBAM 2.5 with Hotfix Package 1 (KB2975636 for client)
2.5.380.0 MBAM 2.5 with Hotfix Package 2 (KB3015477 for client)
2.5.1100.0 MBAM 2.5 SP1
2.5.1119.0 MBAM 2.5 SP1 with Hotfix Package 1 (KB3122998 for server)
2.5.1125.0 MBAM 2.5 SP1 with September 2016 package (KB3168628 for client and server)
2.5.1126.0 MBAM 2.5 SP1 with December 2016 package (KB3198158 for client and server)
2.5.1133.0 MBAM 2.5 SP1 with March 2017 package (KB4014009 for server)


As you can see in above table, some of the version numbers will apply only to client side binaries, some of them only to server side binaries. So it is fine to have client and server components on different version levels (within one major release: 1.0; 2.0; 2.5).

Also older clients (like MBAM 1.0) can still talk to the latest MBAM server (like MBAM 2.5 SP1) however we always suggest to upgrade both client and server side and keep them on most recent version.


Version check:

If you want to check what is the current version of MBAM server side components navigate to the registry:

MBAM 2.5:




MBAM 2.0:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft BitLocker Administration And Monitoring\Setup


If you want to check what is the current version of MBAM agent navigate to the registry:



Or go directly to the filesystem and check properties of the agent service’s file which resides by default in:

C:\Program Files\Microsoft\MDOP MBAM


I hope this quick post was informative and if you have any MBAM version not listed here, please let me know and I will add it to the table.

Comments (12)

  1. Updated the chart with latest patch KB3168628 that adds support for XTS algorithm.

  2. Florian Bröder says:

    Any idea when the next MDOP Version (MDOP 2017) is released?

  3. Sean says:

    Hello Rafal

    Will KB3198158 be added to this awesome chart, or would that not apply to this context?

  4. Yes latest KB added to the chart

  5. Filip says:

    Installed MBAM 2.5 SP1 and HF3 on top:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MBAM Server – > shows SP1 HF3
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MBAM Server\Version – > shows SP1
    Is this expected?

  6. no that means deployment hasn’t been properly done. I have version 2.5.1126.0 in both registry hives.

  7. Tomas Ulbrich says:

    We have a mix of Windows 7, & 10. Currently MBAM client v.2.5.1100 is rolled out, but have deployed 2.5.1125 to Windows 10 – Build1607 systems, as we found out that they do not apply the correct encryption XTS-256 (we’re using GPOs as deployment method), [the other settings are spot on], if they are running 2.5.1100. — Do you know if there will be a full release of server/client?

    And second, I was reading you have to un-install the server components, and re-install the base + HF? – Does that wipe out the configuration settings? – Do we have to reconfigure each and everytime?

  8. Filip says:

    Based on the HF3 KB “To apply this hotfix for MBAM 2.5 SP1, you must uninstall the existing server components, install the RTM version of MBAM 2.5 SP1 Server, and then install the server components of the hotfix.” HF3 is msp file and not sure how to follow the last step. Could it be that HF2 is required in advance as it comes in exe setup wizard flavour

  9. Filip says:

    btw in case anyone else has the same issue Managed to get HF3 installed by removing features, running the msp patch then adding features again.

  10. Mike Clemson says:

    Of note, you have 2.5.1333.0 for the March 2017 servicing release, but the version is actually 2.5.1133.0.

  11. thanks Mike. fixed the typo.

  12. Drew says:

    I thought 2.5.1125.0 MBAM 2.5 SP1 with September 2016 package (KB3168628 for client and server) added support for XTS-AES-256, when I was at 1100, Cipher Strength reported as 128, after the 1125 update Cipher strength became empty on the report. I’m guess I have to install 2.5.1133.0 MBAM 2.5 SP1 with March 2017 package (KB4014009 for server) to get it to report correctly. Can any confirm that please?

    Since I upgrade to 1125 to add support for XTS-AES-256, which it did not. Now I have to uninstall all, reinstall and then apply 2.5.1133.0 MBAM 2.5 SP1 with March 2017 package (KB4014009 for server.

    Is that the correct thinking is my question?

Skip to main content