[Hyper-v] Delete system reserved partition to fix booting issues after cloning win7/win8 virtual disk

After cloning a virtual disk of Windows 7/Windows 8 using Hyper-v, it was found that the system could not boot properly and the cloned disk was smaller in size than the original disk. After investigation, it was discovered that:

To ensure the security of system data, Windows introduced the BitLocker data encryption mechanism after Windows 7. When a new operating system is installed, a 100MB system reserved partition is automatically created to encrypt the boot information of the Windows system using BitLocker. The data in this partition cannot be directly cloned and used.

The solution is simple: delete this unnecessary partition and reconfigure the system's boot files to the system installation disk (usually C drive).

The specific steps are as follows. Please note to backup the system and important data before proceeding:

  1. Run Command Prompt in administrator mode and enter the following commands in order:

DISKPART> sel disk 0
DISKPART> list vol
DISKPART> sel vol 0
DISKPART> inactive
DISKPART> sel vol 1
DISKPART> active

In the above commands, disk 0 represents the disk that needs to be operated on, vol 0 is the number of the system reserved partition, and vol 1 is the number of the system installation partition. After completing all the operations, the system reserved partition will be set as an inactive partition, and the system installation partition will be set as an active partition, just like the configuration of an active partition in Windows XP or Windows 2000.

  1. After exiting diskpart, enter the following command:

C:\windows\system32\bcdboot.exe C:\windows /s C:

This command will recreate the Windows boot in the C drive.

  1. After completion, restart the computer and the operating system can be booted from the C drive.

If the above operations fail, the same operations can also be performed in the command prompt of Windows' system recovery tool for partition boot repair.

Reference link:

Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.