Windows SIM fails to create catalog for Windows 10 image

-

I found an interesting blog post by a guy named Ben R.N. who solved an issue I was having whilst attempting to load a Windows 10 image to Windows SIM in order to create a new customised install.wim.

 His post goes as follows:


"When the Windows System Image Manager fails catalog creation with 0xC1420127 or 0xC1420117

I am currently in the process of setting up an unattended installation of Windows 10. Therefore, I'm using the System Image Manager to create the Unattend.xml file, and to do that, I need a catalog file that corresponds to the WIM I'm deploying. The SIM can generate a catalog from a WIM, but in my case, it failed with codes 0xC1420127 or 0xC1420117, depending on what I tried. Eventually, I discovered that for the SIM to create a catalog, you need to satisfy three conditions:
  • Use install.wim from the \sources folder on the original installation media. A captured WIM does not work because, evidently, it doesn't actually contain the stuff that goes into a catalog.
  • Update your ADK to the version corresponding to the OS you want to deploy. I had previously deployed Windows 8.1, but there's a new version for Windows 10.
  • Clear all subkeys from HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Imagesthat do not correspond to currently-mounted images.
Also, rebooting can't hurt."

Original post can be found here: Original Post

Comments

Post a Comment

Popular posts from this blog

VM Tools fail to upgrade with vix error 21007

-
Image
The reason for the failure in my findings, is because the virtual machine hardware version is old and needs upgrading. Perform a compatibility upgrade on the VM and then try the tools again. This is the error you may get from PowerShell, the same is true using the vSphere web client: This is how you fix it in the vSphere web client:
Read more

Deploy Multiple VM's with PowerCLI and a vCenter Custom Spec.

-
This blog post assumes you have a working vCenter server with at least one host, datastore, network etc...requirements are listed below:  What is required:  Admin access to a running vCenter environment, preferably a lab! Powershell v5 and PowerCLI 6.5. A premade template, EG Windows Server 2016. A vCenter custom spec for the configuration of guest operating systems. Details of my lab are below. I am fortunate to have access to real servers where I work but a computer with enough disk space and maybe 16gb of ram will suffice. You may not be able to run as much simultaneously. My Lab: Dell PowerEdge server 128GB RAM VMware Workstation Pro 12 3 Virtual Machines located inside VMware Workstation.  2 ESXi Servers, 1 Active Directory domain controller. My vCenter server appliance (VCSA.contoso.com) is running on one of my virtual ESXi servers. The Environment: Active Directory and DNS: 10.1.1.1 DHCP provided by VMware workstation network manager. vCenter Se
Read more