You cannot run the BCDBoot.exe tool to repair the BCD store of a Windows 7-based or Windows Server 2008 R2-based system partition by using a computer that is running Windows XPHARDWARE NETWORKING LINUX SOFTWAREIt Tech Technology

It Tech Technology

COMPUTER HARDWARE NETWORKING

Breaking

Home Top Ad

Post Top Ad

Friday, September 28, 2018

You cannot run the BCDBoot.exe tool to repair the BCD store of a Windows 7-based or Windows Server 2008 R2-based system partition by using a computer that is running Windows XP


Fixes a BCDBoot.exe tool issue that occurs when you try to run the BCDBoot.exe tool from a computer that is running Windows XP to repair the BCD store in a Windows 7-based or Windows Server 2008 R2-based system partition.

Hotfix Download Available

Symptoms
Consider the following scenario:
You have a computer that is running Windows XP.
You attach a hard disk drive that contains a Windows 7-based or Windows Server 2008 R2-based system partition to the computer.
You try to run the BCDBoot.exe tool to repair the Boot Configuration Data (BCD) store in the system partition on the attached hard disk drive.

In this scenario, the repair operation may fail. 

If you copy and then run the BCDBoot.exe tool on the computer that is running Windows XP, you receive an error message that resembles the following:
BFSVC: Failed to close the system store. Status = [c0000121]
If you run the BCDBoot.exe tool in the Windows 7-based or Windows Server 2008 R2-based system partition, you receive an error message that resembles the following:
BFSVC: BfspSetSecurityDescriptor(\\?\GLOBALROOT\Device\HarddiskVolume3\Boot) failed! Last Error = 0x7f


BFSVC: Error copying boot files from F:\Windows\boot\PCAT to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot! Last Error = 0x7f Failure when attempting to copy boot files.

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 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 Web site:
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
There are no prerequisites for applying this hotfix.
Restart requirement
You do not have to 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 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 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 and for Windows 7" 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 x86-based versions of Windows 7
File name File version File size Date Time Platform
File nameFile versionFile sizeDateTimePlatform
Bcdboot.exe6.1.7600.20751146,43209-Jul-201005:04x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bcdboot.exe6.1.7600.20751175,61609-Jul-201005:42x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bcdboot.exe6.1.7600.20751362,49609-Jul-201004:30IA-64

Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
This hotfix can be installed on a computer that is running Windows 7. If the Windows 7 operating system is inaccessible, follow these steps to repair the BCD store:
Copy the hotfix to a computer that is running Windows Vista or a later version of the Windows operating system.
Open a command prompt, type the following command, and then press ENTER to extract the .exe file:
.exe -x


Note You are prompted to select a directory to extract the files.
At the command prompt, type the following command, and then press ENTER to extract the contents of the .cab file to the :
Expand -f:*.*
Locate the BCDBoot.exe file in the , and then run the BCDBoot.exe file to repair the BCD store.
For more information about the BCDboot command-line options, visit the following Microsoft website: 
General information about the BCDboot command-line options
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

from Microsoft Support - Windows XP https://ift.tt/2OhMQ2I

Post Bottom Ad