After SCVMM 2022 Upgrade, I'm unable to create new virtual machines.

ዩቶር Abyssinia 71 Reputation points
2023-10-31T12:32:29.1333333+00:00

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.*

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,744 questions
System Center Virtual Machine Manager
Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
980 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,048 questions
Windows Server Infrastructure
Windows Server Infrastructure
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Infrastructure: A Microsoft solution area focused on providing organizations with a cloud solution that supports their real-world needs and meets evolving regulatory requirements.
544 questions
{count} votes

3 answers

Sort by: Most helpful
  1. ዩቶር Abyssinia 71 Reputation points
    2023-11-02T13:20:20.5333333+00:00

    I ended up reinstalling the VMM server and resolve the issue.

    Thanks

    1 person found this answer helpful.
    0 comments No comments

  2. XinGuo-MSFT 17,931 Reputation points
    2023-11-02T01:45:20.3533333+00:00

    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.

    0 comments No comments

  3. VC-2024 0 Reputation points
    2024-01-31T12:13:17.7033333+00:00

    We recently noticed this issue as well when trying to deploy a VM using a template. What worked out for us after testing multiple things was:

    The DLLs from here "C:\Program Files\Microsoft System Center\Virtual Machine Manager\bin" :

    Microsoft.componentstudio.controls.dll Microsoft.ComponentStudio.ComponentPlatformImplementation.dll Microsoft.ComponentStudio.ComponentPlatformInterface.dll Microsoft.componentstudio.controls.dll Microsoft.ComponentStudio.Serializer.dll

    #we renamed them to .old

    #We installed the 1809 ADK and copied over the DLLs (from above) from that installation to the bin folder.

    #restarted VMM

    #deployment via template works again

    In the latest updates for ADK for 2022, Microsoft removed VBScripting so that is our main guess on this. But this works, for now at least.

    Big thanks to AMG for researching and helping with this one.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.