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.

Consider the following scenario:

• You are running a Windows Vista-based computer.
• To provide additional space on the computer’s hard disk, you run a disk management program to expand the size of a logical unit number (LUN).

In this scenario, the LUN size is not updated after you run the disk management program. This issue occurs if you use a computer that includes GUID partition table (GPT) disks.

Note: A master boot record (MBR) disk does not experience this issue.