While still booted into WinPE, attach your VHDX to the destination PC. net use N: \\server\shareĬopy the VHDX from the network drive or storage location to the destination PC's main partition. Main partition =Ĭonnect to the network drive or storage location where you copied the VHDX in step 3.2. Create a system partition (S), and a main partition (M) where the VHDX will be stored.
Use your bootable WinPE key to boot the destination PC to WinPE.Ĭlean and prepare the destination PC's hard drive.
net use n: \\server\share\Ĭlean and prepare a new device for native boot The following maps a drive letter to a network share, creates a directory for the VHD, and then copies the VHD. diskpartĬopy the VHDX to a network share or removable storage drive. Use diskpart to detach the virtual disk from your technician PC. Detach the VHDX and save it to a network share or storage drive You can deploy the VHDX to a device that already has a copy of Windows installed on it, or you can clean and prepare the destination PC's hard drive to use the VHD. Step 3: Detach the VHD, copy it to a new device, and attach it (optional) Dism /Apply-Image /ImageFile:install.wim /index:1 /ApplyDir:V:\ On your technician PC, apply a generalized Windows image to the primary partition of the VHDX that you created and attached in Step 1.
This drive letter will appear in File Explorer. attach vdiskĬreate a partition for the Windows files, format it, and assign it a drive letter. This adds the VHDX as a disk to the storage controller on the host. create vdisk file=C:\windows.vhdx maximum=25600 type=fixedĪttach the VHDX.
In this example, we create a 25 GB fixed-type VHDX.
You can install the VHDX to a device already running other operating system installations, or as the only operating system on a device.įrom the Command Prompt, open Diskpart. This device requires 30 gigabytes (GB) or more of free disk space.
(A hypervisor is a layer of software under the operating system that runs virtual computers.) This enables greater flexibility in workload distribution because a single set of tools can be used to manage images for virtual machines and designated hardware. VHDXs can be applied to PCs or devices that have no other installations of Windows, without a virtual machine or hypervisor. Native boot for Windows 10 or later requires the. This differs from a scenario where a VHDX is connected to a virtual machine on a computer that has a parent operating system. Native Boot allows you to create a virtual hard disk (VHDX), install Windows to it, and then boot it up, either on your PC side-by-side with your existing installation, or on a new device.Ī native-boot VHDX can be used as the running operating system on designated hardware without any other parent operating system.