Native Boot to VHD

I created a VHD with Windows Server 2008 R2 that is in Fix mode. I tried to move this VHD from the current machine to another machine. When I made it bootable, it came up and then errored out. Eventually I get BSOD. On the other hand,
if I have a VHD that is in Dynamic mode, I can make it bootable without any problem. Suggestions?
Thank you in advance.
IMTech

Yes, a different storage driver is a very good reason to get the blue screen. Probably there are options such as disabling RAID/ahci in new machines, but I don't think it is a good way of solving the problem. If you don't want to use sysprep, the DISM is
the way to go. No need to use WinPE, just mount the VHD to another machine ( you can do this using diskpart or disk manager in Windows 7 /2k8r2 OSs) and then install the new drivers using DISM. This can be done whenever a new driver is available at Dell
site. Details of DISM is here
at MS Technet.
If you want to do it while the VHD is running, I don't think DISM is an option. Then use dpinst.exe, which can install drivers for live Windows installations. You can find the details
here at MSDN. DPInst too support installing drivers from command line.
But why do you want to install drivers in the live system? You can mount the 'master' vhd and install all new drivers and just copy it to the new machine.
Krish

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

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

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.

Native Boot VHD with Windows Embedded 7 Standard

I notice the documentation online states that direct boot from VHD is supported, but we don't seem to be able to get this to work. Windows just hangs at Starting Windows. If we directly install or apply a WIM to disk, it boots just fine on
same hardware. Any ideas?

I followed up with the poster offline. This is a bug in FBWF that causes a hang when booting off a VHD. This occurs even if FBWF is disabled. The only workaround available is to exclude FBWF from the image or disable the driver (hklm\system\currentcontrolset\services\fbwf\start
= 4). If you face this issue please contact Microsoft at [email protected]
Srikanth Kamath [MSFT] - This posting is provided "As Is" with no warranties, and confers no rights.
Hi Srikanth,
I am facing the problem you described in your message: "This is a bug in FBWF that causes a hang when
booting off a VHD. This occurs even if FBWF is disabled. The only workaround available is to exclude FBWF from the image or disable the driver (hklm\system\currentcontrolset\services\fbwf\start = 4). If you face this issue please contact Microsoft at [email protected]"
I have made all the WES7 updates via WEDU, but I am still facing the problem: i am unable to boot off a VHD with FBWF in the image. I tried to write an email to [email protected] but
it seems like this email doesn't exist anymore.
I would really appreciate to talk with someone at Microsoft to know:
- if this bug has been resolved
- if not, if there is a workaround
Thanks a lot,
Etienne

Native boot windows 7 ultimate on VHDX

Hi
I have been searching around for this but there's seems to be no answer and so I hope Microsoft tech support can help me answer this.
I have a PC which I want to dual boot windows 7 Ultimate and windows 8.1 Professional, both on vhdx.
First I installed windows 7 ultimate onto a VHD and it is able to boot natively.
I then install windows 8.1 professional onto a VHDX and now it can dual boot both win7 and win8.1 natively (vhd and vhdx respectively) with win8 boot menu.
Then I boot into win7 and installed kb980218 (to support 4096 disk), and converted the image from vhd to vhdx and set the physicalsize to 4096.
Next the boot entry has been amended and point to this new win7 vhdx.
However when I try to boot into this new win7 vhdx, it doesn't boot up and instead goes into recovery mode, the error is "boot configuration is corrupt" when trying to repair it. FYI, booting into win8 vhdx still works fine.
My question is given the system partition boot environment is windows 8.1 as in this case (requirement of native boot), can you natively boot windows 7 in vhdx????? If so how to make this work? (there should be no difference to the guest OS whether
its' a vhd or vhdx and so given the boot environment is windows 8, my guess is it should work)
And if not, can windows 7 install in vhdx and run inside a virtual machine (e.g., with Host OS as windows 8)
Thank you.
John

>If so how to make this work? (there should be no difference to the guest OS whether its' a vhd or vhdx and so given the boot environment is windows 8, my guess is it should work)
I've never tried this and not likely to, but the base OS definitely needs
to know how to access a VHDX and since Windows 7 predates VHDX, I suspect
it can't be done.
Once the Windows 8 boot loader passes the running off to Windows 7, it's
got to have a driver to access the disk, and it doesn't.
It's basically the same problem as trying to dual boot Windows XP in a
VHD...
Bob Comer Microsoft MVP -- Hyper-V

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 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

Native Boot VHD Winload.efi Issue

I get a "corrupt or missing" winload.efi error (0xc000000e) when the machine first boots. I then hit the ESC key, select F9 (boot device options), then select either my Windows 10TP or my VHD (also W10TP). It then boots.
I have an HP Pavilion 15, with AMD 10, 12 GB RAM, VHD is in a directory on a 2nd drive.
BIOS settings are set to UEFI enabled, SecureBoot disabled. (I've swapped this back and forth and still the same.)
I've tried setting the VHD as default, nothing.
I've tried to fix it using suggestions from other OS threads, including repairing the boot and it finds nothing.

Hi IslandCoder,
The way I used is almost same with you, see picture above, I create the VHD file (about 20G size), and use command to apply the wim file to VHD:
DISM/Apply-Image /ImageFile:<image_file> /index<index_number> /ApplyDir:<image_path> command.
When it is finished, use bcdboot command to create a boot entry for this VHD device.
Use the BCDboot tool to copy common system partition files and to initialize boot configuration data:
C:\Windows\System32\bcdboot C:\Windows
If the key steps are OK, there should be no other problem. I have tested about three times with Windows 10 Technical Preview.
Alex Zhao
TechNet Community Support

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

Dual boot windows server 2008 R2 with windows 8.1 UEFI

Dear all,
i was trying to dual boot in UEFI windows 8.1 and windows server 2008 R2 but every time windows server 2008 R2 separately before installing windows 8.1 was working after this windows 2008 R2 gives me blue screen immediately even if i installed windows 8
first then windows server 2008 but for all case windows server 2008 R2 works with debug mode .
i could not understand the reason

Hi,
What is the STOP error while BSOD occurred? You could try to troubleshoot BSOD with the following method.
How To Fix a Blue Screen of Death
http://pcsupport.about.com/od/fixtheproblem/ht/stoperrors.htm
In addition, have you tried to use Native Boot to make a dual boot? For details, please refer to the following articles.
Understanding Virtual Hard Disks with Native Boot
http://technet.microsoft.com/en-us/library/dd799282(WS.10).aspx
Add a Native-Boot Virtual Hard Disk to the Boot Menu
http://technet.microsoft.com/en-us/library/dd799299(WS.10).aspx
Native Boot To VHD Part I of IV - Overview
http://blogs.technet.com/danstolts/archive/2010/03/29/native-boot-to-vhd-part-i-of-iv-overview.aspx
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Boot file for Windows 7 missing after windows 10 installation.

Hello,
Recently for the purpose of evaluation, i installed Windows 10 enterprise technical preview on a VHD mounted on a machine running Windows 7 64bit ultimate. Installation process went well but since then I cannot log onto windows 7 itself.
Machine loads directly to windows 10 without giving any option to choose the OS. When I checked the system configurations there is only one boot file displayed - windows technical preview - there is no sign of windows 7 boot file.
Wondering if anyone else experience any such issues.
If yes then how to solve this issue.
Thanks

Hi Mansoor Moin,
Can you give us more information about your situation?
Based on my understanding, you create a Native Boot to VHD on Windows 7 machine, right?
If so, this would be a mistake on deleting boot entry.
I would like to know if you can get the Windows 7 system partition in current disk management. If so, we can use following command to add a boot entry.
bcdboot F:\windows
F: represents the Windows 7 Operating system letter.
Alex Zhao
TechNet Community Support

Multiple Failures Related?

Here's an oddity. Software Update--gets only 15% into action then freezes before finding anything. Disk Utility--searches forever, and can't even find the disks. Downloaded Security Updates and Java Updates--non compos mentis, get part way through, then can't Continue.
B'b'but the OS X 10.4.9 Update (downloaded manually) did its thing just fine.
Is there some easy fix? (Throw away the Xyz, Luke...)
-iNova

Hi,
Please try this guide to make native boot from VHD for Windows 10, I have tested it, and it works fine.
Boot to VHD (Native Boot): Add a Virtual Hard Disk to the Boot Menu
http://technet.microsoft.com/en-in/library/hh825691.aspx
Make sure that you open the command prompts as Administrator before running command to create VHD and deploy Windows 10 into this VHD.
If you still get permission error, considering that permission of current account may be corrupted, please try this again by login with built-in administrator.
Kate Li
TechNet Community Support

[Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
Tip 1: How to use Refresh option to upgrade.
Scenario
In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
PC settings-> Upgrade and recovery->
Preview builds, which is as shown below.
If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
Solution
If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
image.
Step 1: Understand the basic information about install.esd.
Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
Step 2: Export the file install.wim.
The following command is used to export Windows 10 Technical Preview Build 9860 image:
Dism /Export-Image /SourceImageFile:<path_to_install.esd>
/SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
Step 4: Use Refresh option to upgrade your PC.
Go to
Update and recovery setting under PC settings, choose
Refresh your PC without affecting your files:
Note:
Applications needed to be reinstalled.
System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
Note: If you use install.esd to refresh directly, just need point the index location as 4:
Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
Tip 2: Workground to upgrade native boot VHD.
Scenario
Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
Solution
Step 1: Upgrade in Hyper-V.
Use Hyper-v to create a new virtual machine, and use your native boot VHD
as an existing virtual hard disk:
If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:
You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
Step 2: Create Native Boot to VHD.
When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
Mount the 9860 native boot VHD file.
Use the following command to create boot entry for VHD system: Bcdboot
v:\windows (v: represents the mounted virtual disk drive letter).
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

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

Native Boot to VHD

Similar Messages

Maybe you are looking for