Embed virtual installation disks in the boot manager

I know that the operating system can be installed in a virtual hard disk (VHD). Since the boot manager but not in the VHD file, but on the first primary hard drive of the system, this data when changing the hard drive or deleting the disk are lost. In the following we therefore describe how an existing installation to a VHD Vista / Windows 7 Boot Manager can be integrated again, or this, if no boot manager is gone, can be created. But the problem with me is that, after installing Windows 7 in a virtual hard disk (VHD) file, the installer automatically adds the necessary entries to the boot manager to boot the system from the VHD file. The boot manager is not in the VHD file, but exists on the boot partition of the system. :blink: I am not able to find out the problem. Maybe I did incorrect installation, so also provide some useful steps for installing. Please help me.

Within Disk Management, Windows 7 is basically the (input to input / search box of Windows 7 "hard drive" or "diskmgmt.msc"), which is under System - Administration finds>, dealing with virtual disks in charge. Create a new VHD, it offers the Disk Management only the types and set dynamically. Note here that in a dynamic disk the size you specify the "maximum" is taken up by this guy on the system, while at the "Fixed size" of these taken place directly in hardware, regardless of the data contained therein. id you create a virtual disk, it must first - as any other storage devices - are initialized. The next step we shall now take volumes to partitions on the virtual hard disk. You can use the whole space or part to use for volume and will thus bring more than one drive on a virtual hard disk. In the last step drive letter and file system are awarded with which the volume is then integrated into the system. For the operating system, these volumes are now like any other partition. If you want to disconnect the virtual disk in a running system again, you can do so via the Disk Management. Use the right mouse button on the virtual hard disk appears there the necessary entry. If we choose to separate the function, this must be reconfirmed. Existing VHDs can in Disk Management with the command "Add virtual hard disk" are included. The following dialogue is only one path to the VHD file and the option, if the disk is to be integrated read-only. The small tool Disk2vhd partitions created using existing VHD files used in the article can continue to use the way itself.

The program Diskpart, which is started from the command line, you have not only been using the Disk Management presented capabilities for creating, integrating and separating VHDs, but much more specialized. To start the Diskpart command prompt with administrative rights is necessary (cmd + Ctrl + Shift + Enter). Diskpart is not a command, but a program that expects to launch other commands. All possibilities of Diskpart (not only for VHD) is available with "help". To exit Diskpart, the command "exit" is necessary. Virtual disks can use the create command as vdisk file = f: \ test.vhd maximum = 25000 type = create fixed. Instead of the fixed type, you can also specify expandable (dynamic). Hard disk type differential is created with diskpart by specifying the main hard drive. So you created the vdisk create command file = f: \ testdiff.vhd parent = f: \ test.vhd a difference file, which is associated test.vhd. Now, if the binding testdiff.vhd in the system, the content is displayed test.vhd of any changes but testdiff.vhd stored in the. This system is particularly suitable for a Windows 7 installation for testing purposes. If, on system problems, you can create the delete testdiff.vhd easy and a new one. The Windows installation itself is not affected.

Unfortunately, when re-embedded VHDs startup will no longer be automatically included, so you should try again until the Disk Management. This is something simple with a small freeware Attach VHD , which in the context menu of VHD files and integrates with a single click VHDs into the system one way or embed this can disconnect from. An automated integration at the start, which would increase the benefits of VHDs essential is only indirectly and with the command "diskpart" possible. In various postings on the Internet (search VHD attach) is advised, for example, that creates a batch file. The syntax for the attach.cmd then is:

diskpart / sc: \ scripts \ disk.txt

In the 2 Disk.txt file (located in c: \ scripts \) then are the details of what Diskpart to perform well. In the example of the path F 2 VHDs be involved.

select vdisk file = "f: \ test.vhd"
attach vdisk
select vdisk file = "f: \ test2.vhd"
attach vdisk

This system has the disadvantage that you have to accept the changes, thanks to UAC by diskpart at every system startup.

In addition to the installation to a real partition, the Ultimate and Enterprise editions of Windows 7 are installed on a virtual hard disk. This installation has the advantage that the existing partitions must first make any changes. The virtual disk is - like any other file - just on a partition with sufficient space and is involved from there on startup test of Windows 7 as a virtual drive and then used as a hard disk. If you want to eliminate the installation, you can simply delete the file and remove the boot manager with tools like EasyBCD record Windows 7, so that it starts again, the old system as before. The loss of speed when working with a virtual hard disk in a real system (not in a VM) are only detectable through measurements and not be felt in the daily work. To create a virtual hard disk, proceed as follows:

1. First you start by pressing Shift + F10 prompt and here diskpart.
2. Then one chooses to select volume (ID) the correct volume (volume list) on which the virtual disk will be created as a file.
3. The next step is placed over the vdisk create command file = c: win7.vhd type = fixed maximum = 25000 virtual disks \.
4. be \ is exemplary only and must be replaced by the on which the virtual hard drive is finally to be saved: The path c. The guy fixed firmly states that it is a fixed size and not a growing, virtual hard disk is about. The latter can be expandable with the command set, it uses less disk space, but costs performance, especially when starting and stopping of the system on that disk. The size of the virtual disk you put maximum established with the parameter.
5. last step, choose the hard disk created with select vdisk file = c: \ Win7.vhd of (path only as an example) and binds them attach vdisk as a disk with.
6. After entering exit at the command prompt, and then update the disk view of the virtual disk is now visible.
7. The indication that Windows is not on this disk can be installed, you can ignore, since it still works.

:thumbup1:

Sometimes scenario occurs where it's already a Windows Vista or Windows 7 on the hard drive. In this scenario, the system already use Windows Vista and / or installed Windows 7 and therefore the boot manager already exists on a partition. The VHD-installation should now be taken only in addition to the boot manager. Ensure the entries of the first boot manager with the command bcdedit / export "c: \ bdsicherung" in the event that something goes wrong with the change. The original code can bcdedit / import "c: \ bdsicherung" read back again. As a first step one starts from the executable system out the command line CMD with administrator privileges (CTRL + SHIFT + ENTER). Then you put the command / bcdedit {default} / d "Windows 7 VHD" a copy of the default entry in the boot manager to copy, whereupon a new output is guid} {. This copy is best via the clipboard (mark it with the mouse, then RETURN to copy) in the text editor Notepad. The / d assigns a name (Description). At the bottom you will find our new record that still must be edited now. From the command line the following three entries must be entered, in which case the {guid} and the path (drive, path and file name) should be adjusted.

• bcdedit / set {guid} device vhd = [X:] \ win7.vhd
• bcdedit / set {guid} osdevice vhd = [X:] \ win7.vhd
• bcdedit / set {guid} detecthal on

For easy entry, it is advisable to prepare the first entries in the text editor, then copy and paste it on the QuickEdit mode in the command line. The QuickEdit mode, you can activate the properties of the prompt by pressing in the title bar of the right mouse button and then "Properties" selected. If this mode is activated, the clipboard contents with the right mouse button to be copied directly into the body of the prompt. This saves labor and typos in long strings.

There are 3 types of virtual hard disks:

1. Virtual hard disk with fixed-size - A virtual disk of this nature occupies the specified as the maximum size to a real hard drive, even if the virtual hard disk, no data are available (empty container with a fixed size). The advantage of this variant is very fast read and write access, which is distinguished in their daily work from that of a real hard disk.
   
2. The virtual disk to dynamic size - This hard drive type is the size dynamically, ie only the size of the contents therein. As can be adapted for writing on this hard drive the size of each type needs to the write and read operations are generally much slower than the fixed type. Dynamic disks do not automatically shrink and retain their largest state, even when files are deleted it in the meantime. The shrink is done manually.
   
3. Virtual hard disk as the difference with a 2nd virtual hard disk - The 3rd Type stores only changes and additions that are to be made to another, read-only virtual disk (difference). The 3rd Type lends itself therefore as a drive to undo a virtual disk with a fixed size, which includes an operating system.