{"id":1492,"date":"2009-07-23T02:02:56","date_gmt":"2009-07-23T02:02:56","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/2009\/07\/running-windows-from-a-usb-flash-drive.htm"},"modified":"2012-01-03T20:22:34","modified_gmt":"2012-01-03T20:22:34","slug":"running-windows-from-a-usb-flash-drive","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2009\/07\/running-windows-from-a-usb-flash-drive.htm","title":{"rendered":"Running Windows from a USB flash drive"},"content":{"rendered":"

I’ve titled this post as “Running Windows from a USB flash drive” because the same principles should be equally applicable to all Windows 7-based operating systems (and even Vista if the Windows 7 bootloader is used<\/a>)<\/del> but my specific scenario was based on Hyper-V Server 2008 R2.<\/em><\/p>\n

I got this working a few hours after Windows 7, Server 2008 and Hyper-V Server 2008 R2 were released to manufacturing but I was still using release candidate code – fingers crossed it still works with the final release!<\/p>\n

Boot from VHD is a fantastic new technology in Windows 7\/Server 2008 R2 and derivative operating systems and I’ve often wondered if it’s possible to use it to run Hyper-V from a USB flash drive (just like the “embedded” version of VMware ESXi offered by some OEMs). Well, as it happens it is – and this post describes the steps I had to take to make it work.<\/p>\n

First of all, I needed to create a virtual hard disk and install an operating system onto it. As Keith Combs noted, there are various ways to do this but only one is supported<\/a>; however there is also a handy video on TechNet which takes you through the steps of creating a VHD and booting from it<\/a>.<\/p>\n

Using the TechNet video as a guide, I issued the following commands from the command prompt to create my virtual hard disk and apply an image from the Hyper-V Server 2008 R2 release candidate DVD:<\/p>\n

diskpart
\ncreate vdisk file=driveletter:\\virtualharddisk.vhd maximum=15000 type=expandable
\nselect vdisk file=driveletter:\\virtualharddisk.vhd
\nattach vdisk
\nlist disk<\/dirtycode><\/p>\n

(make a note of the disk number.)<\/p>\n

select disk disknumber
\ncreate partition primary
\nselect partition 1
\nactive
\nformat fs=ntfs quick
\nassign
\nexit<\/dirtycode><\/p>\n

(note the drive letter for the newly mounted VHD.)<\/p>\n

imagex \/info dvddrive:\\sources\\install.wim<\/dirtycode><\/p>\n

(identify the correctentry.)<\/p>\n

imagex \/apply dvddrive:\\sources\\install.wim \/check imageindex vhddrive:\\
\ndiskpart
\nselect vdisk file=driveletter:\\virtualharddisk.vhd
\ndetach vdisk
\nexit<\/dirtycode><\/p>\n

At this point, Hyper-V Server had been imaged into my new VHD, which could then be copied to the USB flash drive.<\/p>\n

Next, to load the VHD from the Boot Manager, I edited the boot configuration data (which is what would be required in a standard boot from VHD scenario); however, as I found later, a different set of actions is needed for booting from the USB flash drive.<\/p>\n

bcdedit \/copy {current} \/d “Hyper-V Server 2008 R2”
\nbcdedit<\/dirtycode><\/p>\n

(make a note of the GUID for the newly created entry.)<\/p>\n

bcdedit \/set {guid} device vhd=[usbdrive:]\\virtualharddisk.vhd
\nbcdedit \/set {guid} osdevice vhd=[usbdrive:]\\virtualharddisk.vhd
\nbcdedit \/set {guid} detecthal on
\nbcdedit \/set {guid} description “Hyper-V Server 2008 R2”<\/dirtycode><\/p>\n

It’s worth understanding that the use of drive letters (which are transient in nature) does not cause a problem as the BCD Editor (bcdedit.exe<\/code>) extracts the data about the partition and saves it in the BCD store (i.e. it does not actually save the drive letter).<\/p>\n

After rebooting, Hyper-V Server loaded from my USB flash drive and ran through the out of box experience. At this stage I had Hyper-V Server running off the flash drive but only if my original Windows installation (with the boot manager) was available and, as soon as I removed the hard disk (I wanted to be sure that I was booting off the flash drive with no other dependencies), then the whole thing collapsed in a heap. Thanks to Garry Martin, I checked my BIOS configuration and made sure that USB device boots were enabled (they were not) but I then spent about a day playing around with various BCD configurations (as well as various attempts to fix my BCD with bootrec.exe<\/code>) until I stumbled on a post from Vineet Sarda (not for the first time, based on the comments that include one from yours truly a few weeks back!) that discusses booting from VHD without a native operating system<\/a>.<\/p>\n

Following Vineet’s example, I booted my system into Windows 7 (I could have used the Windows Recovery Environment), reformatted the USB flash drive before copying my VHD image back onto it, and issued the following commands:<\/p>\n

diskpart
\nselect vdisk file=usbdrive:\\virtualharddisk.vhd
\nattach vdisk
\nlist volume
\nexit<\/dirtycode><\/p>\n

(note the drive letter for the newly mounted VHD.)<\/p>\n

bcdboot vhddrive:\\Windows \/s usbdrive: \/v<\/dirtycode><\/p>\n

(i.e. copying the BCD from the operating system image contained within the VHD, to the physical USB drive. Note that, when running on a live system it is important to specify the target drive for the BCD in order to avoid overwriting the live configuration.)<\/p>\n

I then shut down the system, removed the hard disk and booted from the USB flash drive, after which the Windows Boot Manager loaded an operating system from within the VHD.<\/p>\n

Looking at my BCD configuration (shown here for reference), I can see the source of my many hours of confusion – the Boot Manager resides on the physical media (my USB key – which was allocated drive D: in this case) and loads an operating system from the virtual disk that is given another drive letter (in this case C:):<\/p>\n

Windows Boot Manager
\n——————–
\nidentifier\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{bootmgr}
\ndevice\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0partition=D:
\ndescription\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Windows Boot Manager
\nlocale\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0en-us
\ninherit\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{globalsettings}
\ndefault\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{current}
\nresumeobject\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{27f66313-771a-11de-90bb-00037ab36ab6}
\ndisplayorder\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{current}
\ntoolsdisplayorder\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{memdiag}
\ntimeout\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a030<\/code><\/p>\n

Windows Boot Loader
\n——————-
\nidentifier\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{current}
\ndevice\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0partition=C:
\npath\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\\windows\\system32\\winload.exe
\ndescription\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Hyper-V Server 2008 R2
\nlocale\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0en-us
\ninherit\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{bootloadersettings}
\nosdevice\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0partition=C:
\nsystemroot\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\\windows
\nresumeobject\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{27f66313-771a-11de-90bb-00037ab36ab6}
\nnx\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0OptOut
\ndetecthal\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Yes
\n<\/em>
\nIt took a while to boot (my flash drive was a freebie is not the fastest in the world) but, once loaded into memory, Hyper-V Server seemed to run without any noticeable delay. I figure that, as long as the workload is stored on another disk this should not present any problems and, given suitably fast flash memory, it ought to be possible to improve boot times as well. Running a full Windows operating System (e.g. Windows 7) in this manner is an entirely different matter – very few USB flash drives will be able to stand the constant writes and further testing would be required.<\/p>\n

Now that I have Hyper-V Server running from an inexpensive USB flash drive with no reliance on my PC’s internal hard disk, all I need to do is inject the correct network drivers and I will have a virtualisation solution for colleagues who want to run a full hypervisor on their corporate notebooks, without deviating from the company’s standard client build.<\/p>\n

Additional information<\/h3>\n

The following notes\/links may provide useful background information:<\/p>\n