Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"RPC Server Unavailable" error after you set up a password in Bitlocker To Go in Windows 8.1 or Windows 7


View products that this article applies to.

Symptoms

Consider the following scenario:

  • You have client computers that are running Windows RT 8.1, Windows 8.1, Windows Server 2012 R2, Windows 7, or Windows Server 2008 R2 in a domain.
  • You enable the Require password for removable data drive policy setting in the following Group Policy Object (GPO) path:
    Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Removable Data Drive\Configure use of passwords for removable data drives
  • You plug in an external device to the client computer.
However, when you type the password and then click the Next button in the BitLocker To Go wizard,you receive an error message that resembles the following:

RPC Server Unavailable

↑ Back to the top


Resolution

To resolve this issue, install update rollup 2962409, or install the hotfix that is described in this article.

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2962409 June 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

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 this specific problem.

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, submit a request to 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

There are no prerequisites for installing this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 7 and Windows Server 2008 R2 file information and 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.1.760 1.22xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fveapi.dll6.1.7601.22664271,76024-Apr-201422:45x86
Fveapibase.dll6.1.7601.22666104,44825-Apr-201401:57x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fveapi.dll6.1.7601.22664345,18424-Apr-201422:50x64
Fveapibase.dll6.1.7601.22666113,15225-Apr-201402:27x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fveapi.dll6.1.7601.22664711,36824-Apr-201422:49IA-64
Fveapibase.dll6.1.7601.22666238,59225-Apr-201401:42IA-64


↑ Back to the top


Status

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

↑ Back to the top


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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_dd924bab8bef56003b956015525f499a_31bf3856ad364e35_6.1.7601.22666_none_f633bd30c475b082.manifest
File versionNot applicable
File size706
Date (UTC)25-Apr-2014
Time (UTC)09:34
File nameX86_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7601.22666_none_373786cf69a589ab.manifest
File versionNot applicable
File size9,058
Date (UTC)25-Apr-2014
Time (UTC)02:24
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File propertyValue
File nameAmd64_68bd319a45f150da90770a02227eec0c_31bf3856ad364e35_6.1.7601.22666_none_537eb1117878101f.manifest
File versionNot applicable
File size710
Date (UTC)25-Apr-2014
Time (UTC)09:34
File nameAmd64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7601.22666_none_935622532202fae1.manifest
File versionNot applicable
File size9,062
Date (UTC)25-Apr-2014
Time (UTC)03:01
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_7c5d08066f53c37421928ba1a7a4f3a5_31bf3856ad364e35_6.1.7601.22666_none_fe9968a90e26e30c.manifest
File versionNot applicable
File size708
Date (UTC)25-Apr-2014
Time (UTC)09:34
File nameIa64_microsoft-windows-securestartup-core_31bf3856ad364e35_6.1.7601.22666_none_37392ac569a392a7.manifest
File versionNot applicable
File size9,060
Date (UTC)25-Apr-2014
Time (UTC)02:14

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2962059
Revision : 1
Created on : 1/7/2017
Published on : 8/11/2014
Exists online : False
Views : 320