However it didn't work, as you suppose that 21HI.ISO might only support install.esd from Sources folder. Thanks for reading! your description, it seems you tried to boot your 21H1 image including (install.wim) which has been modified and captured by DISM. When I copy the new install.wim (removing install.esd from the install media as well) back to the installation media, the resulting new ISO doesn't work, setup complains a device driver must be missing cuz it can't find anything to work with.Īll of these steps are being done in a virtual machine (VirtualBox)Īny tips or suggestions, or references to documentation on how to do this properly would be greatly appeciated. Copy new install.wim to the original ISO, removing install.esd Use DISM to capture the modified Windows to a new install.wim.Ħ. Use Sysprep to return the installation to 'uninstalled' OOBE mode so next boot will re-initiate hardware detect and OOBE.ĥ.
Check for updates, install a few applications, make a few profile changes to the administrator account.Ĥ. But the end result is, when I delete the install.esd file from the sources folder and replace it with a install.wim, the installation media simply doesn't work anymore.ģ. I cannot find any information on generating an esd file, as they appear to be encrypted or something? I'm a bit confused about the matter.
This generates a new install.wim image I can put onto the installation media.Ģ1H1's installation media has changed from using install.wim, to using install.esd.
I am using DISM to capture my installed and re-sealed via sysprep copy of Windows 10 with customizations. I recently acquired the 21H1 iso image to regenerate my deployment images and ran into a snag when attempting to add a recovery partition to the image that allows the user to reinstall windows from installation media included in the image.īasically, previous to 21H1, the iso images contained a 'install.wim' archive within the 'sources' subfolder of the installation media.
0 kommentar(er)
