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.

A Windows Server 2008 system or a Windows Vista Service Pack 1 system cannot start after you increase or reduce the size of the boot volume on a GPT disk


View products that this article applies to.

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

↑ Back to the top


Symptoms

Consider the following scenario:
  • You install Windows Server 2008 or Windows Vista Service Pack 1 on a GUID partition table (GPT) disk.
  • Then, you convert the GPT disk from the Basic disk type to the Dynamic disk type.
  • Later, you increase or reduce the size of the boot partition on the dynamic disk by using the Disk Management snap-in.
In this scenario, the system cannot start. When you try to start the system, you receive the following error message:
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File:
boot_file
Status: 0xc0000225
Info: The selected entry could not be loaded because the application is missing or corrupt.

↑ Back to the top


Cause

This issue occurs because the universally unique identifier (UUID) of the boot partition changes when you increase or reduce the size of an existing partition. Therefore, the system cannot start from the boot partition.

↑ Back to the top


Resolution

Hotfix information

Windows Vista Service Pack 1

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. 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: 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 have Windows Vista Service Pack 1 installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista Service Pack 1, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Amd64_cd498108106509e3b41b41749f42043b_31bf3856ad364e35_6.0.6001.22202_none_46eb755e77ff469b.manifestNot Applicable71213-Jun-200816:33Not Applicable
Amd64_microsoft-windows-dynamicvolumemanager_31bf3856ad364e35_6.0.6001.22202_none_39acfccb57a217c1.manifestNot Applicable4,53513-Jun-200804:57Not Applicable
Package_1_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,79813-Jun-200816:33Not Applicable
Package_2_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,96713-Jun-200816:33Not Applicable
Package_3_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,80313-Jun-200816:33Not Applicable
Package_4_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,80313-Jun-200816:33Not Applicable
Package_for_kb954207_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37513-Jun-200816:33Not Applicable
Package_for_kb954207_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43913-Jun-200816:33Not Applicable
Package_for_kb954207_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42913-Jun-200816:33Not Applicable
Package_for_kb954207_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43113-Jun-200816:33Not Applicable
Package_for_kb954207_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43313-Jun-200816:33Not Applicable
Package_for_kb954207_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43913-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43013-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43713-Jun-200816:33Not Applicable
Volmgrx.sys6.0.6001.22202409,65613-Jun-200804:10x64

↑ Back to the top


Windows Server 2008

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. 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: 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
No prerequisites are required.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Amd64_cd498108106509e3b41b41749f42043b_31bf3856ad364e35_6.0.6001.22202_none_46eb755e77ff469b.manifestNot Applicable71213-Jun-200816:33Not Applicable
Amd64_microsoft-windows-dynamicvolumemanager_31bf3856ad364e35_6.0.6001.22202_none_39acfccb57a217c1.manifestNot Applicable4,53513-Jun-200804:57Not Applicable
Package_1_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,79813-Jun-200816:33Not Applicable
Package_2_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,96713-Jun-200816:33Not Applicable
Package_3_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,80313-Jun-200816:33Not Applicable
Package_4_for_kb954207~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,80313-Jun-200816:33Not Applicable
Package_for_kb954207_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37513-Jun-200816:33Not Applicable
Package_for_kb954207_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43913-Jun-200816:33Not Applicable
Package_for_kb954207_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42913-Jun-200816:33Not Applicable
Package_for_kb954207_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43113-Jun-200816:33Not Applicable
Package_for_kb954207_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43313-Jun-200816:33Not Applicable
Package_for_kb954207_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43913-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43013-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43713-Jun-200816:33Not Applicable
Volmgrx.sys6.0.6001.22202409,65613-Jun-200804:10x64

Windows Server 2008, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Ia64_1c7615b83c9bd0849d7763fa4463a303_31bf3856ad364e35_6.0.6001.22202_none_9e8ed658a6834ce3.manifestNot Applicable71013-Jun-200816:33Not Applicable
Ia64_microsoft-windows-dynamicvolumemanager_31bf3856ad364e35_6.0.6001.22202_none_dd90053d9f42af87.manifestNot Applicable4,53213-Jun-200804:38Not Applicable
Package_1_for_kb954207~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,79313-Jun-200816:33Not Applicable
Package_2_for_kb954207~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,79813-Jun-200816:33Not Applicable
Package_3_for_kb954207~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,79813-Jun-200816:33Not Applicable
Package_for_kb954207_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42513-Jun-200816:33Not Applicable
Package_for_kb954207_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42613-Jun-200816:33Not Applicable
Package_for_kb954207_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42913-Jun-200816:33Not Applicable
Package_for_kb954207_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43413-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42613-Jun-200816:33Not Applicable
Package_for_kb954207_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43313-Jun-200816:33Not Applicable
Volmgrx.sys6.0.6001.222021,033,78413-Jun-200804:21IA-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

↑ Back to the top


Keywords: kb, kbautohotfix, kbexpertiseinter, kbbug, kbfix, kbhotfixserver, kbqfe

↑ Back to the top

Article Info
Article ID : 954207
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 350