Windows 10: Recovery not working after capturing install.wim from VHDX

Hi Team,OS: Windows 10 and Windows 11.we are working on a scenario, where we need to create install.wim from VHDX. During this process, we need to install office and capture usmt.ppkg. below are the steps and action we took to make it work.1 We took base no office VHDX2 Created VM and attached VHDX 3 Boot into VM and login using audit mode. 4 Installed office and capture USMT and ran sysprep command to shutdown with generalize option.5 We used DISM as well as new-WindowsImage commands to capture install.wim.when we tried to test, image is working fine with out any issues , but when w

:)

 

Is it possible to sysprep a wim file after it is captured?

I know what I am supposed to do: Run sysprep and then capture the image.

I know that you can do a lot of offline work on a WIM file using DISM. I know you can mount, edit, and unmount a WIM.

Is there some creative way to perform the sysprep steps on a WIM file that was captured from a production system?

I've looked far and wide but I've only seen people talking about the Microsoft way of doing things.

 

capture WIM image of KVM W10 VM for convert to physical (V2P)

Hi folks

@Hopachi one for you as well to try out !!!

I've got a great running W10 KVM virtual machine running with all the software working etc -- so I would like to capture the WIM image via DISM. Also I'd like all the software etc on a Windows ISO so I don't have to re-install again on a new machine.

The main problem of course is that the Windows ISO (whether you create it from UUPDUMP or MCT won't have the KVM VIRTIO drivers so won't recognize the disk your VM is stored on so can't capture the image.

Pre condition or step 0 . You should convert the Windows Virtual hard disk from QCOW2 to RAW format first if your HDD is in QCOW2 format and install the VIRTIO disk drivers if not already done. RAW always works better BTW. This is easily done via img-convert in QEMU and check that the W10 VM boots. Also ensure any data etc is solely on the Windows partition / virtual disk --same as for capturing a WIM image on a Real physical machine.

So step 1 is to Slipstream the VIRTIO drivers into the Windows install ISO.

That's done by following this excellent link -- just ignore all the proxmox stuff -- we only want to slipstream the drivers into the ISO so that we can capture the WIM image of the running Virtual Machine !!!!!.

GitHub - Zer0CoolX/proxmox-windows-slipstream-virtio-drivers: Step-by-step guide to slipstream VirtIO drivers into Windows ISO's for use in Proxmox VE

Now you can boot the ISO in your Virtual machine , get into command mode and capture the WIM via Kari's excellent tutorial.

Have fun folks !!!

Cheers
jimbo

 

How To: Create recovery partition.

it worked when i copied all the files of the disk to the recovery partition i created, but i had to use WinPE tab to add the entry.

Type: WIM Image (Ramdisk)
Name: Recovery
Path: Z:\Sources\boot.wim
and hit Add Entry
I tried it in VirtualBox and it worked.
At first, it would add a second "Windows 7" entry to the list, but when the installation is finished, the old one is deleted. (I formatted only C: partition)