You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 if the computer is a failover cluster node

Consider the following scenario:

• You have a computer that is running Windows Server 2008 R2.
• You configure the computer as a failover cluster node.
• You try to enable BitLocker on a non-shared hard disk volume of the computer.

In this scenario, the operation fails and you receive the following error message: Note Windows Server 2008 R2 supports enabling BitLocker on a non-shared disk on a failover cluster node.

The following is an example scenario:

• You install Microsoft Exchange Server 2010 on a computer that is running Windows Server 2008 R2.
• You configure the computer as a member of a database availability group (DAG).
• You try to enable BitLocker on a non-shared hard disk volume on the computer.

In this scenario, the issue occurs, and you cannot enable BitLocker on the volume.

The issue occurs because BitLocker incorrectly enlarges the limitation scope when BitLocker judges whether BitLocker can be enabled on a disk volume.
BitLocker does not support cluster shared disks. Unfortunately, BitLocker incorrectly checks whether the current computer is a cluster node when BitLocker judges whether BitLocker can be enabled on a disk volume. If a computer is a failover cluster node, BitLocker does not enable BitLocker on a non-shared disk.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem that is described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running the following operating system:

• Windows Server 2008 R2
• Windows Server 2008 R2 Service Pack 1 (SP1)

Registry information

You do not have to change the registry to use this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	SR_Level	Service branch
  6.1.760 0.20xxx	Windows Server 2008 R2	RTM	LDR
  6.1.760 1.17xxx	Windows Server 2008 R2	SP1	GDR
  6.1.760 1.21xxx	Windows Server 2008 R2	SP1	LDR

• GDR service branches contain only those fixes that are widely released to address widespread, very important issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2