This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I recently upgraded VMM from 2019 to 2022 without issues, but when I try to create a new VM from an existing VM Template, it fails at the VM configuration phase. I've in-place upgraded the operating system of the VMM server from Windows Server 2016 to Windows Server 2022. I've also installed the Windows Server 2022 version of ADK.
Below is the error that I get from the VMM console.
Error (20413)
VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\SCVMM.b0d6393c-e02e-4d6e-b1b1-5ad509ee0613\report.txt.
Recommended Action
See the report for exception type, exception message, stack trace and other relevant details. Also check the Windows Event Log for additional troubleshooting information.*
Please advise.
Below is the exception:
exceptionObject.ToString()
----------------------------------------------------
System.BadImageFormatException: Could not load file or assembly 'Microsoft.ComponentStudio.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'Microsoft.ComponentStudio.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.VirtualManager.WorkloadCreation.UnattendXMLFile..ctor(String path, Version osVersion, Architecture arch, ProductType ptype)
at Microsoft.VirtualManager.WorkloadCreation.UnattendXMLFile.CreateUnattendXMLFile(String path, Version osVersion, Architecture arch, ProductType ptype)
at Microsoft.VirtualManager.Engine.VmOperations.CustomizeVMSubtask.createAnswerFile(OSConfig osfg, String answerfilepath)
at Microsoft.VirtualManager.Engine.VmOperations.CustomizeVMSubtask.GenerateAnswerFile(IVmmDbConnection dbConnection, Boolean useSimplifiedCustomization)
at Microsoft.VirtualManager.Engine.VmOperations.CustomizeVMSubtask.RunSubtask(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.VmOperations.NewVmFromTemplateSubtask.PostVmCreationCustomize(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.VmOperations.NewVmSubtaskBase.RunNewVmSubtasks(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.VmOperations.NewVmSubtaskBase.RunSubtask(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.VmOperations.NewVmFromTemplateSubtask.RunSubtask(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run(IVmmDbConnection dbConnection)
at Microsoft.VirtualManager.DB.SqlContext.Connect(Action`1 action)
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
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].
I ended up reinstalling the VMM server and resolve the issue.
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
Please try 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.