The Windows Servicing Guy

Tips and tricks from a Windows support engineer on issues related to servicing

Bitlocker updates for SP2 are available

Bitlocker updates for SP2 are available

  • Comments 7
  • Likes

As a followup to my post over the summer, the Bitlocker tools which were not working with SP2 have been updated.  They are NOT on the Download Center as of yet and are only available internally right now.  They will be released on the Download Center sometime at the end of the month as far as I am aware, barring any major setback.

If you have an urgent need for the tools you can call into Microsoft Technical Support and request that they send you the fix which you need.  To make sure that you get the proper binaries, reference internal article 2001039 when you speak to an engineer, it will help them find the proper pathing to the files.

Keep in mind that the current KB articles that cover these updates are valid for the usage of these binaries and will not be updated for the re-release of the tools for SP2.  I hope this helps.

--Joseph

Comments
  • Is there a Qfecheck for Windows XP Professional x64 Edition? There is a Qfecheck for Windows 2000, XP and XP 64-bit Itanium but not for XP x64. Please make it available, it's a highly useful tool for scanning multiple systems.

  • It's available for XP x64, just call in for 282784 and tell them you need the x64 build of the files.  It looks like they were never published with the article.

  • I'm not in the US but in India. Please for heaven's sake make it available for download with the article. The Windows Server 2003 32-bit version, and XP x64 and Server 2003 x64

  • Btw are you sure it's the x64 version and not the IA64 one?

  • Never mind I obtained using the email method. Thank you so much for letting me know. Henceforth, I'll be checking with the "Request a hotfix" form.

  • No problem, glad it worked out for you.

  • Hi, do you have any further updates - despite checking with the MS download center on a daily basis the tools have yet to appear.  Whilst the workarounds are fine - I'm want to distribute via our ConfigMgr infrastructure without having to script up.