MDT Not Generating Catalog

[Wired_Inside_90]

Hi Folks,

 

I've recently stumbled across an error with our MDT. It has been running fairly smoothly with no issues re imaging machines. However, last week I decided to view my unattend.xml and encountered this message.

 

 

Performing the operation "generate" on target "Catalog".Starting: "C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.Catalog40.exe" "D:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2019 x64\Sources\install.wim" 1 > "C:\Users\ADMINI~1.KIN\AppData\Local\Temp\2\Microsoft.BDD.Catalog.log" 2>&1No existing catalog file found.PROGRESS: 0: Starting.PROGRESS: 0: Creating mount folder: C:\Users\XXXXXXX\AppData\Local\Temp\2\IMGMGR_install_Windows 10 Enterprise LTSC 2019_wp3gwdl0.wdg.PROGRESS: 5: Creating temp folder: C:\Users\xxxxxxxxxx\AppData\Local\Temp\2\IMGMGR_install_temp_plyqu4cq.03v.PROGRESS: 10: Mounting Windows image: D:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2019 x64\Sources\install.wim. This might take a few minutes.PROGRESS: 30: Mounted Windows image.PROGRESS: 33: Serializing Data.PROGRESS: 63: Cleaning up...PROGRESS: 63: Unmounting Windows image: D:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2019 x64\Sources\install.wim.PROGRESS: 66: Deleting mount folder.PROGRESS: 69: Cleaning up...ERROR: Unable to generate catalog on D:\DeploymentShare\Operating Systems\Windows 10 Enterprise LTSC 2019 x64\Sources\install.wim: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ComponentStudio.ComponentPlatformImplementation, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.ComponentStudio.ComponentPlatformImplementation, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.CreateOfflineImageInstance(OfflineImageInfo imageInfo) at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageCatalog.Serialize(OfflineImageInfo imageInfo) at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog() at Microsoft.BDD.Catalog.Program.DoCatalog()

 

 

WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].Non-zero return code from catalog utility, rc = 2002

 

 

This is a fresh task sequence so i'm a bit stuck. Any help would be greatly appreciated!

 

 

 

Many thanks!

[robyholmes]

I had this today. Looking online it suggested the image was x86 which can't be edited on a x64 server.

[Wired_Inside_90]

Thanks for the reply Robyholmes. I did come across this i'll double check but pretty sure its running on a x64. It's also using a x64 WIM. I've seen some mentions of MDT mounting wims and keeping them in a temp file. I'll update tomorrow.

 

Cheers

[Arthur]

Microsoft released a fix for the x64 WSIM bug in the 1903 ADK on Friday.

 

Download: WSIM1903.zip

 

https://docs.microsoft.com/en-us/windows-hardware/get-started/what-s-new-in-kits-and-tools#windows-system-image-manager-known-issue

 

When using Window System Image Manager (SIM), you might encounter errors if the ADK is installed on a device running a 64-bit version of Windows. To create unattended Windows Setup answer files on a 64-bit version of Windows, download the WSIM 1903 update, and follow the included installation instructions.

 

https://twitter.com/jarwidmark/status/1139609397213224960

 

[foofighterjim]

Apologies for bringing up an old thread but I am having the same issue after applying the above fix.

 

I am just starting to test 1909, and get the exact same message as @Wired_Inside_90 when going into the task sequence to generate the catalogue.

 

Our setup is:

 

Windows Server 2016 Datacentre x64

Deployment Workbench Version 8456

ADK 1903

ADK WIN PE 1903

WISM1903 patch applied

 

I forgot all about the catalogue file and actually built a workstation with the template but it took an eternity to apply the Unattend.xml, would this have been because the catalogue file hadn't been generated and the processing was being done on the device? Would this have been likely to cause any issues with the build other than slowing it down? Anyone have any suggestions on what I can do about this?

[Arthur]

I am just starting to test 1909, and get the exact same message as @Wired_Inside_90 when going into the task sequence to generate the catalogue.

Generating the catalogue using WSIM (outside of MDT) will still work.

[foofighterjim]

Generating the catalogue using WSIM (outside of MDT) will still work.

 

That's done the trick!