Windows 8.1, Boot from VHD, natively

Hi,
I used this procedure
http://technet.microsoft.com/en-us/library/hh825691.aspx in order to be able to boot from VHDx.
I have a working VHD, booted into winpe, scratched my new Lenvos Yoga 11S (diskpart, clean), then attached the vhdx, was able to copy bootfiles via bcdboot w:\windows /s w: (w is virtual drive) but after reboot it says "default device missing or boot failed.
No os anymore at all :-(
This is my config
https://www.dropbox.com/s/4aqirkqn6qnrbgo/2014-11-17%2020.23.15.jpg?dl=0 please advise.
J.
Jan Hoedt

Hi,
"default device missing or boot failed"
It sounds like a issue with your BIOS configuration or boot drive.
1.Please see if you can enter the BIOS configuration and change the boot device order.
2.Some one fixes this issue for a Lenovo system by changing the boot mode to "Legacy", please see if it fits your situation
You can find similiar issue in the links below:
http://blog.vtechsquad.com/2014/01/02/how-to-fix-default-boot-device-missing-or-boot-failed-error-in-windows-8/
https://forums.lenovo.com/t5/Lenovo-3000-and-Essential/Default-Boot-Device-Missing-or-Boot-Failed/td-p/1378491
https://forums.lenovo.com/t5/Idea-Windows-based-Tablets-and/Yoga-2-Pro-Boot-errors/td-p/1665397
NOTE
This
response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you.
Microsoft
does not control these sites and has not tested any software or information found on these sites.
Yolanda Zhu
TechNet Community Support

Similar Messages

Boot from VHD generates Error 0xc03a0001

So I created a VHDX which contains an installed windows 7 environment.
Booted my windows 8.1 environment, attached the vhdx and added the VHDX environment to my boot.
BCDBOOT F:\WINDOWS
Reboot, choose windows 7 and get this error;
0xc03a0001 -> An unexpected error has occurred.
When I lookup this error, it means "The virtual hard disk is corrupted. The virtual hard disk drive
footer is missing."
So I re-created the vhdx and the system on it, but it spawns the same error.

i found this article maybe very useful to investigate your issue
http://reboot.pro/topic/16141-troubleshooting-os-boot-from-vhd/
VHD BOOT TROUBLESHOOTING
VHD boot problems are rare, when following exactly the Tutorials linked in this Post Signature. Most are caused by a corrupted BCD (Boot Configuration Datastore) or missing boot-critical disk & controller drivers, enabling reading the VHD or hard disk
where its saved. If they occur, follow the troubleshooting steps for natively supported & unsupported OS boot from VHD:
1) install latest Windows Virtual PC (with 1024Mb+ RAM assigned), attach Win7 VHD to it as IDE disk and try to boot as hard drive. If it doesn't, it may be because of missing or errors in BCD, missing Bootmgr, mismatch of disk Sig, or incorrect partition
offset set in BCD, DetectHAL element is Off or missing, missing disk driver, or volume wasn't marked Active. This may occur, since Win7 & ThinPC may lack BCD sample store in their WindowsBoot folder, resulting in wrong BCD structure when using BCDBoot
command to add BCD to the new VHD. To fix, use suggested repair sequence. However, if you face 0x7B error during boot from VHD, you may need to add missing disk driver(s) entries to VHD's OS Registry, and add the driver installation packages, so that OS can
autoinstall the drivers after boot. Read this and that explanation threads, and use suitable tools, like included with IMG_XP driver utilities and its collection of Registry fixes. Or, once you found missing driver INF packages, attach the VHD, mount its OS
Volume to an empty folder and inject the drivers offline with DISM as per Install Unsupported OS to VHD Tutorial. If the VHD boots after that, proceed to step 2.
2) copy that Win7 VHD from HD to a bigger fixed contiguous VHD, add boot environment to the bigger VHD disk with EasyBCD or Visual BCD Editor installed on your system HD, add Win7 boot entry to it, attach the big VHD to Win VPC as IDE disk, try to boot Win7
from VHD natively inside VPC. If it doesn't, fix the big VHD's BCD using the below repair sequence. After it does, proceed to step 3, if you want test booting with Grub4DOS & WinVBlock.
3) add Grub4DOS to the big VHD, fully install WinVBlock to Win7 after booting it natively from VHD or as IDE disk inside VPC, make Win7 VHD contiguous, attach the big VHD to the Win VPC as IDE disk, try to boot Win7 VHD from it via G4D & WinVBlock menu.
If errors, try to find matching versions of Grub4DOS & WinVBlock (older G4D may work well with WinVBlock - Feb. 2011, can take from wimb's IMG_XP folder). If Grub4DOS shows "File not found" error on boot, and the file name is correct in its Menu,
the problem seems to be in mounting the large VHD disk. You must reboot G4D to continue tests or restore original disk mapping. Make sure to test sign WinVBlock 64-bit, and switch On Test Mode in Win7 64-bit, or use F8 at boot. Should boot... but at times
WinVBlock disk may cause OS instability & file access issues after boot.
Boot troubleshooting requires some practice, so easy way to start - native boot VHDs & EasyBCD.
REPAIR BCD STORE WITH VISUAL BCD EDITOR
- Boot Win7 from your host drive, attach the VHD with related to BCD boot problems, when attached to VPC as hard drive
- Make sure OS volume on VHD is marked as Primary & Active, and mount it as V: drive
- Start Visual BCD Editor, open BCD Store from V:BootBCD
1. If there is no BCD Store on the VHD:
- Select Repair Boot Record from Menu, select V: , tick Vista/7&Fix MBR --> OK,
- Select Repair BCD from Menu, BCD Drive V: , Win7 folder V:Windows --> OK
- Exit Visual BCD Editor, detach the VHD and reboot in VPC to check if the errors were fixed
2. If there is BCD Store on the VHD:
- Delete all entries under Loaders section on the Left Pan
- Click Edit Boot-Menu, delete all Boot Entries from the DisplayOrder list
- Proceed to Repair Boot Records, then Repair BCD from Menu
- Reload BCD from the VHD by selecting Open Store again from Menu
- Add any missing OS Loaders in Loaders section on the Left Pan, and rename their entries as you like
- Click on each entry on the Left Pan, and inspect its elements on the Right Pan. Make sure they make sense for the hard drive boot, are similar to a reference VHD's BCD that boots OK (GUIDs may differ), and linked to correct BCD Objects GUIDs
- Click Edit Boot-Menu, and add or edit boot entries list and display order to match Loaders list on the Left Pan
- Exit Visual BCD Editor, detach the VHD and reboot in VPC to check if the errors were fixed
REPAIR BCD STORE WITH EASYBCD
You can use EasyBCD instead of Visual BCD Editor to create or repair a BCD store:
- Install and start EasyBCD
- Select BCD Store on the VHD, using File Menu and open it
1. If there is no BCD Store:
- select BCD Deployment on the Left Pan, click Install MBR, then select partition V: --> Install BCD
- Click Add New Entry --> Windows Vista/7 --> Drive V: --> Add Entry
- Exit EasyBCD, detach the VHD and reboot in VPC to check if the errors were fixed
2. If there is BCD Store:
- select BCD Backup/Repair on the Left Pan, tick Recreate/Repair Boot Files --> Peform Action, then tick Reset BCD Configuration --> Perform Action
- Exit EasyBCD, detach the VHD and reboot in VPC to check if the errors were fixed
- If not, reattach the VHD as V: drive, open Console, run bcdboot v:windows /s v: to recreate BCD manually
- Detach the VHD and reboot in VPC to check if the errors were fixed
- If not, boot from the VHD natively from the host's Boot Menu (if its OS supports native boot from VHD), install EasyBCD and try fixing VHD BCD Store and boot sectors with it, then test boot again
- If it still doesn't boot, and you added all required boot time drivers to OS on the VHD, post the exact boot error and Windows Safe Mode driver load step, when the error occurred, in a new thread asking for help.
sorry for the long copy paste

Win 7 boot from VHD "License Error: Booting from VHD is not supported on this system"

I am trying to set up my TP 500 model 2242-CTO to boot from a virtual hard drive, per the instructions at
http://blogs.technet.com/keithcombs/archive/2009/05/22/dual-boot-from-vhd-using-windows-7-and-window...
I get all the way thru the Win 7 setup, but just as the login screen is presented, I get the subject message. That's the end of story, can't go further.
I just updated the BIOS and hard drive firmware to the latest versions on the Lenovo site as of today (3.09), and the hard drive firmware said no update needed.
Anybody know what will work? Just academic now, as I will go ahead an reinstall win 7 normally....
Thanks !

Not true, mine is win7 pro and works, I think the problem is that lenovo makes a custimized boot for their utility

Boot from VHD with exisiting vhd

I'm trying to set up booting from VHD from an existing vhd and have 2 questions.
(1.)
What I did was running a disk2vhd on the exisiting Dell laptop install. What I want to do now is being able to boot from this VHD alongside my real physical install with a dual boot configuration. So one normal install on a physical disk and a second boot option
pointing to the vhd (created with the disk2vhd).
I found a bunch of articles describing how to set up boot from vhd starting from scratch. But how should I configure a second boot option pointing to the vhd that I want to boot? I tried modyfying the BCD file using BCDedit but the vhd won't boot. When I
boot the same vhd in a hyper-v VM it starts just fine. Should I do any additional steps for that to work? ANy article that you know of that describes this scenario?
(2.) A second question about hibernation. When I have booting from 2 different vhds set up is it possible to put vhd1 in hibernation, reboot and choose to boot from vhd2, put that one in hibernation and switch back to vhd1 after a reboot? Anyone ever tried
that?
Any help is appreciated.

no need to start several topic. I already replied here:
http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/0514aa0e-4513-4686-82d6-e186541b515a
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Windows 7 wont boot from CD

Hello, i recently had my mac Laptop serviced which involved wiping the hard drive, and now i have to re-install windows.
i have my windows 7 ultimate CD and my mac is running fully updated software, every time i hit start installation of windows on boot camp, or even boot from the CD instead of going into mac, the screen goes black and just idols, eventually the fans turn off and it appears to be completely off, moving mouse/pressing keys has no effect, but it is on, and in order to get anywhere i have to hold the power button to turn it off and then press it again to turn it on, can boot into mac okay, but i need the windows side working ASAP.
what can i do to fix this?

You may have a faulty Windows disk. Can you borrow a different one to try starting with?
I had a non functioning Vista disk a couple of years ago and Microsoft willingly replaced it via a phone conversation.

Getting Windows 7 to Boot from Second Disk Drive

Recently I purchased a solid state drive for my HP desktop. The desktop is running 64 bit Windows 7 Premium (HP upgrade from Vista).
My goal is to have the operating system boot from the new SSD and not from the original hard drive. I have done the following:
1. Installed SSD and plugged it into SATA slot 1 on motherboard. The original drive remains in SATA slot 0.
2. Formatted SSD and assigned new drive letter "K" (next available) in Windows 7.
3. Using Acronis, I "recovered" a previous backup of the operating system onto the SSD including boot sector.
3. In BIOS, selected boot order for SSD to be ahead of original drive.
However, when starting Windows, the operating system is clearly running from the original drive, not the SSD.
Questions:
1. In older operating systems, it mattered what SATA slot the "boot" drive was plugged into. Should I have plugged the SSD into slot 0 on the motherboard instead of slot 1? Does it matter with this PC and Windows 7?
2. Does the Windows 7 operating make calls to drive C without regard to where it boots from? If yes, how do I rename the SSD to "C"? (I'm thinking I should unplug the original drive from the motherboard altogether then try a rename).
3. Are there other issues I have not recognized? Loading the OS from an SSD sounded so simple before I started!
All advice will be gratefully appreciated. Thank you.

Hi, you will need to either change the drives bootup order in the BIOS or select it from the bootup menu at startup (press F9 I think). See this topic Re: HP Pavilion Elite e9180t Storage Upgrade in Desktop Hardware for more details. Good luck.
Thanks,
HP Employee

HP ENVY dv6-7246us SSD Upgrade, Problem Installing Windows 7 with boot from usb/dvd disc.

Hello everyone,
I have recently purchased the dv6-7246us and have upgraded the HDD to a SSD. The problem I am having now is that I can't boot from the usb or a dvd disc that contains the Windows 7installation. Originally this laptop had an HDD with Windows 8. I have changed the boot order multiple time to boot from the USB Harddrive and the DVD/CD-ROM disc and still have no luck booting up from the installation. Is there a solution to this problem?
Thanks,
Robert
This question was solved.
View Solution.

Hi, Robert:
Did you go into the BIOS and change it to Legacy Mode?
I believe you need to do that in order to boot from another device other than the hard drive.

Windows partition wont' boot from internal secondary HDD? No bootable device error

Here is my scenario: I previously had a 500GB bootcamped HDD in my 2012 macbook pro. The boot camp partition was running windows 7 and the mac partition was running 10.9. I replaced my original HDD with a 250GB SSD, took out my optical drive, and replaced that (op drive) with my original HDD. When i boot from the main drive, the SSD, it successfully recognizes the HDD with the 2 different partitions on it. But when I try to boot into my windows partition(on the HDD) by holding option at startup and selecting the windows partition, I keep getting a black screen "No bootable device. Insert boot disk and hit any key". I tried installing rEFIt, but still no luck. Here is the output from partition inspector:
* Report for internal hard disk *
Current GPT partition table: # Start LBA End LBA Type 1 40 409639 EFI System (FAT) 2 409640 487127591 Mac OS X HFS+ 3 487127592 488397127 Mac OS X Boot
Current MBR partition table: # A Start LBA End LBA Type 1 1 488397167 ee EFI Protective
MBR contents: Boot Code: None
Partition at LBA 40: Boot Code: None (Non-system disk message) File System: FAT32 Listed in GPT as partition 1, type EFI System (FAT)
Partition at LBA 409640: Boot Code: None File System: HFS Extended (HFS+) Listed in GPT as partition 2, type Mac OS X HFS+
Partition at LBA 487127592: Boot Code: None File System: HFS Extended (HFS+) Listed in GPT as partition 3, type Mac OS X Boot
Ive seen similar post, but none specific to my scenario. Any input would be greatly appreciated. I am trying to preserve the contents of my original HDD as it contains important school files I will be needing.

Please download Gdisk from http://sourceforge.net/projects/gptfdisk/ . You do not have a valid MBR on disk1 so Windows will not boot, even though you can see the volume in OS X Finder on the HDD.
Use Gdisk to recreate a Hybrid MBR which includes GPT#4.
Here is an example. Please notice the spaces between 2,3 and 4.
sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 0.8.10
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 59BDFEEB-1EB4-4529-94FE-3CBC2C3CD513
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 2604 sectors (1.3 MiB)
Number Start (sector)    End (sector) Size       Code Name
   1              40          409639   200.0 MiB   EF00 EF
   2          409640       401060383   191.0 GiB   AF05 Macintosh HD
   3       401060384       402329919   619.9 MiB   AB00 Re
   4       402331648       490233848   41.9 GiB    0700 Microsoft basic data
Command (? for help): r
Recovery/transformation command (? for help): h
WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
just hit the Enter key at the below prompt and your MBR partition table will
be untouched.
Type from one to three GPT partition numbers, separated by spaces, to be
added to the hybrid MBR, in sequence: 2 3 4
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF): AF
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default AB): AB
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #4 (MBR partition #4)
Enter an MBR hex code (default 07): 07
Set the bootable flag? (Y/N): y
Recovery/transformation command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/disk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
Now Reboot and verify the output of fdisk again.

I have heat issues into MacBook pro after installing windows 8. when boot from windows ha've overheating. how can I fix it??

Have heat issues into MacBook pro when boot from windows partition how can I fix it??

panarpan wrote:
Have heat issues into MacBook pro when boot from windows partition how can I fix it??
Are you saying you're running Windows in BootCamp or Windows as a Virtual Machine? You can increase the fan speed on the Mac using smcFanControl and use the software OGELTHORPE recommended to observe improvements.
smcFanControl is a Mac application and doesn't work in Windows, but if you set a higher minimum fan speed (which is how smcFanControl works) while running OS X, when you reboot into a BootCamp partition, that minimum speed tends to be carried over.

Windows Refuses to boot from 2 brand new Macbook pro 13 2011 model laptops

I'm having the same problem.
I bought a macbook pro 13inch 2.3 ghz core i5 base model yesterday. I gave it the normal windows partition as i normally do with all my macs and tried to install Win7.
The installation was ok except that it took the macbook pro like 40 seconds to finish showing the Black screen with the blinking cursor .
I then Installed Bootcamp 3.2 and restarted, it took its normal 40 secs to show the black screen and blinking cursor after i had selected windows to boot and then it restarted!
I tried 4-6 times but it keeps giving me the same result.
I then reformatted 4 times both the Windows and Mac partitions and tried to repeat the windows installation but it kept giving me the same result.
A friend of mine bought his macbook pro 13 base model today and when i tried installing, it gives the same result! What is wrong?
I then installed Parallels 6 on both laptops and immediately it booted the already installed windows partition.(*but i don't want to use parallels )
But when i restart and hold down the option key and choose windows, it keeps giving me the black screen with the blinking cursor and the restarts itself.
I have used 10 or more macbook pros and airs in the past and they've never given me this sort of problem.
What is wrong???

Having Windows on GPT and EFI; not having default OS set to Windows.
Having boot options in msconfig set to default (30 seconds) instead of reducing to 5 seconds (if present, it may not be).
40 seconds is slightly longer I guess for you than OS X but people with trouble are reporting 1-4 minutes. I think 40 is in normal range.

Installing the Windows IoT insider preview on SD card when booting Windows 10 from VHD Native Boot

The setup instructions for the raspberry pi 2 mention that "you
will need to follow these instructions on a physical Windows machine (and not a VM) because you need access to the SD card reader."
Will this work if you boot Windows 10 natively from a VHD (like
this) or does the virtualization still get in the way?

If you insert the SD card and can see it in explorer or when you perform the diskpart command to list drives, then it should work, since in effect the VHD is the native OS at that point. If you don't see the card, then you'll have to perform a local
install.
Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided 'as is' with no warranties and confers no rights.

Boot from VHD Upgrade

So why has Microsoft not learned that customers need the ability to upgrade Windows when using native VHD boot??? I have a lot of systems that we installed Windows 7 and Windows 8.1 on Native VHD Boot, but cannot upgrade the OS. My workaround
was to get a Windows Server 2012 Hyper-V host up, create a VM that uses the source VHD to upgrade the OS. But that's not practical for 100's of systems. Can someone please explain why this limitation exists? If the Windows Installer supports
Native VHD Boot and Install, why can't an upgrade?

Hi Arman mohseni,
From my observation, if I click download now, it would create a BITS task:
We can use following command to check:
Import-module bitstransfer
Get-bitstransfer –allusers
From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
Alex Zhao
TechNet Community Support

IMac running on Mac OS 10.5.8 & Windows XP wont boot from Mac OS

I have an iMac running Mac OS 10.5.8 and Windows XP (ServicePack 3) on Boot Camp 2.2. This configuration has worked for me perfectly for the past 2 years up until recently. From nowhere, the system is now refusing to boot to Mac OS but boots into Windows XP without any problem.
I have tried to repair the Boot Camp 2.2 in Windows XP via the repair/update option from the Boot Camp installation but its giving a fail message;
The installer has encountered an unexpected error installingthis package. The error code is 2727.
I have also tried to verify and repair the Macintosh HD partition using the Disk Utility but its giving me the following error message;
On verify disk
Invalid Sibling link
Volume check failed
ERROR: Filesystem verify or repair failed.
I could repartition and start all over again but there are some files and emails I need to retrieve from the Mac partition before I delete and repartition.
Is there any shareware software that I can install on theWindows XP partition and be able to access/retrieve my files in the Mac partition?

you can't repair Mac OS X from Windows.
What you need to do and realize is that Disk Utility is not good enogh or reliable enough and you need 3rd party disk repair utility.
Or just restore Mac HFS from backups.
You may want to install Mac OS on another external hard drive
Recover the files there - probably best to have two partitions.
you should have already created multiple backup sets: clone type and TimeMachine
Disk Warrior is $90 or there is TechTool Pro 6 for almost same
Cloning is easy enough either from Mac OS X DVD Disk Utility Restore or from another hard drive.
Cloning as a Backup Strategy
Carbon Copy Cloner
WinClone VMware HDD Upgrade
MPG - How To Guides - How to clone a volume
SuperDuper

Windows 7 only boots from bios, Start-up repair cannot identify windows.

So I recently bought a Samsung SSD 840 PRO 256GB to replace my 80GB Intel SSD. My plan was to migrate Windows 7 to the new drive, delete the old drive and install Ubuntu 14.04 on it. I used this tutorial to transfer the data: https://www.youtube.com/watch?v=qYK-C4rIxrI
It didn't work the first time, so I tried a second time (it overwrote the data from the first try.) and it looked like it worked. I unplugged everything except the Samsung, and it booted fine. Then I took the Samsung off and installed Ubuntu 14.04 on the
old drive (which seems to have its own issues, but I will deal with that later.)
When I try system repair, I am unable to choose an OS to repair. When I try bootrec /rebuildbcd it says it cannot recognize the file system and to make sure the system drivers are loaded.
BUT, I can still boot to Windows if I select the drive in bios. (I think Ubuntu is broken, because that wont boot at all.)
My priority is to get windows working, hopefully without reinstalling.

I fixed it somehow, but that was not the problem. I re-installed Ubuntu on the old drive, except I completely deleted all the stuff on the drive first. Then I rebooted both drives separately, they both booted automatically. Now everything works except the
grub boot loader.
I did say that I could still boot to windows by selecting the Samsung in the bios... so your answer didn't help.
I think that the old drive might have been overwritten the wrong way and there was still something from that drive messing with the boot order. That might explain why it worked when I had only the Samsung hooked up.

Installing Windows PE to Boot From A Removable Drive

This article on Technet says, "On UEFI-based PCs, Windows PE requires a boot partition formatted using the FAT32 file format." I've successfully formatted WinPE-boot
USB media using NTFS. The article goes on to recommend locating WinPE in a FAT32 partition and files larger than 4GB in a separate NTFS partition. Any reason why we shouldn't use a single NTFS partition?

Hi,
I think the article mentioned that Windows PE requires a boot partition formatted using the FAT32 file format is under the condition UEFI, not means Windows PE must formatted using the FAT file format.
In addition, why UEFI based PC need FAT32 file format PE, I think it should Considering the compatibility problems.
You can refer to the link below which had another explaination:
UEFI based systems such as the Surface Pro or other UEFI systems require that the boot files reside on FAT32 partition. If they are not FAT32 the system may not see the device as bootable.
http://blogs.technet.com/b/askcore/archive/2013/03/20/creating-bootable-usb-drive-for-uefi-computers.aspx
http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
Roger Lu
TechNet Community Support

Windows 8.1, Boot from VHD, natively

Similar Messages

Maybe you are looking for