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

Article translations Article translations
Article ID: 2446607 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

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:
The drive configuration is unsuitable for BitLocker Drive Encryption. To use BitLocker, please uninstall clustering services.
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.

CAUSE

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.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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
    VersionProductSR_LevelService branch
    6.1.760 0.20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.17xxxWindows Server 2008 R2SP1GDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fveapi.dll6.1.7600.20873344,57605-Jan-201106:26x64
Fveapibase.dll6.1.7600.20873113,15205-Jan-201106:18x64
Fveapi.dll6.1.7601.21634345,60005-Jan-201106:20x64
Fveapibase.dll6.1.7601.21634113,15205-Jan-201106:17x64
Fvecpl.dll6.1.7600.20873184,32005-Jan-201106:18x64
Fvewiz.dll6.1.7600.20873573,95205-Jan-201106:18x64
Fvecpl.dll6.1.7601.17514184,32020-Nov-201013:26x64
Fvewiz.dll6.1.7601.21634573,95205-Jan-201106:17x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fveapi.dll6.1.7600.20873711,79205-Jan-201105:10IA-64
Fveapibase.dll6.1.7600.20873238,59205-Jan-201105:08IA-64
Fveapi.dll6.1.7601.21634711,79205-Jan-201105:11IA-64
Fveapibase.dll6.1.7601.21634238,59205-Jan-201105:07IA-64
Fvecpl.dll6.1.7600.20873263,16805-Jan-201105:08IA-64
Fvewiz.dll6.1.7600.20873757,24805-Jan-201105:08IA-64
Fvecpl.dll6.1.7601.17514263,16820-Nov-201010:26IA-64
Fvewiz.dll6.1.7601.21634757,24805-Jan-201105:07IA-64

STATUS

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

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_021e0c477d8787f2813606870d43c08c_31bf3856ad364e35_6.1.7600.20873_none_85aa91d87c3e9196.manifest
File versionNot applicable
File size710
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameAmd64_759f521127eaee99c9c00279f9f400e1_31bf3856ad364e35_6.1.7600.20873_none_8cc25fc451d1c75e.manifest
File versionNot applicable
File size709
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameAmd64_cd6db366a35a11ece9e0821973730991_31bf3856ad364e35_6.1.7601.21634_none_6a442ad1bfda397e.manifest
File versionNot applicable
File size709
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameAmd64_d5be9c72ebcdd7ea8dd40aa5f09aff97_31bf3856ad364e35_6.1.7601.21634_none_ec2021182ae82adf.manifest
File versionNot applicable
File size710
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameAmd64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7600.20873_none_91620b4b24e74540.manifest
File versionNot applicable
File size9,057
Date (UTC)05-Jan-2011
Time (UTC)06:59
PlatformNot applicable
File nameAmd64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7601.21634_none_9374a84b21ec5abf.manifest
File versionNot applicable
File size9,057
Date (UTC)05-Jan-2011
Time (UTC)06:51
PlatformNot applicable
File nameAmd64_microsoft-windows-securestartup-cpl_31bf3856ad364e35_6.1.7600.20873_none_b40dbcb6bde0ac1c.manifest
File versionNot applicable
File size15,717
Date (UTC)05-Jan-2011
Time (UTC)15:50
PlatformNot applicable
File nameAmd64_microsoft-windows-securestartup-cpl_31bf3856ad364e35_6.1.7601.21634_none_b62059b6bae5c19b.manifest
File versionNot applicable
File size15,717
Date (UTC)05-Jan-2011
Time (UTC)15:50
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_3a572b8539e71ae083001a00dc4cd79a_31bf3856ad364e35_6.1.7600.20873_none_2a6001f3c2001ab1.manifest
File versionNot applicable
File size708
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameIa64_62651f30279a88a478f01dc5df8c302a_31bf3856ad364e35_6.1.7601.21634_none_3ed235daa081b864.manifest
File versionNot applicable
File size707
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameIa64_bc312b2dae20ab84ea75b17db4eb6c7c_31bf3856ad364e35_6.1.7600.20873_none_9246cb1596546579.manifest
File versionNot applicable
File size707
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameIa64_d9ebce3ae07fdd420076ea6954c489cb_31bf3856ad364e35_6.1.7601.21634_none_e452064492979e80.manifest
File versionNot applicable
File size708
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameIa64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7600.20873_none_354513bd6c87dd06.manifest
File versionNot applicable
File size9,055
Date (UTC)05-Jan-2011
Time (UTC)06:55
PlatformNot applicable
File nameIa64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7601.21634_none_3757b0bd698cf285.manifest
File versionNot applicable
File size9,055
Date (UTC)05-Jan-2011
Time (UTC)06:54
PlatformNot applicable
File nameIa64_microsoft-windows-securestartup-cpl_31bf3856ad364e35_6.1.7600.20873_none_57f0c529058143e2.manifest
File versionNot applicable
File size15,715
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable
File nameIa64_microsoft-windows-securestartup-cpl_31bf3856ad364e35_6.1.7601.21634_none_5a03622902865961.manifest
File versionNot applicable
File size15,715
Date (UTC)05-Jan-2011
Time (UTC)15:39
PlatformNot applicable

Properties

Article ID: 2446607 - Last Review: February 10, 2011 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2446607

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com