Windows Server 2012: After KB5022352 update, doesn't allow starting Hyper-V virtual machines

Question

After installing the update KB5022352, the server does not allow the virtual machines to run. This also happened since the update KB5015874 but after 10 months the bug was not fixed and it is repeated with all cumulative packages

Answer 1

Hello

If you encounter the Hyper-V virtual machine after installing Windows Server, such as KB5022352 and KB5015874, you must solve this problem. The following is the steps you can take to eliminate and solve the problem:

Check the event log:

View any error messages or events related to Hyper-V or virtual machines, and check the Windows event log, especially system and application logs. This can provide more specific details about the issue.

Roll back update:

If the problem starts with one of the problems (for example, KB5022352) is installed immediately, please consider uninstalling or rolling this specific update to see if the problem is solved. You can perform this operation through "Program and Function"> View installation and update section.

Application of follow -up update:

Microsoft often releases updates to solve the problems introduced previously updated. Check whether there are newer cumulative updates or hotfixs, and apply them to see if they solve the problem.

Hyper-V integration service:

Make sure that the Hyper-V integrated service is the latest in the virtual machine. These services are essential for communication between the host and the virtual machine. If necessary, update integration services in each virtual machine.

Maintenance Hyper-V installation:

You can try to repair the Hyper-V installation on Windows Server. Open the "server manager", navigate to "Management"> "Add Characters and Functions", and then select "Hyper-V". Please repair and install according to the prompts.

Check the update specific to V:

Sometimes Microsoft releases ultra -V specific updates to solve known problems. Check whether there are updates specially related to Hyper-V in Windows Server 2012.

Keep in mind that using the virtualized environment, especially in the production environment, you need to be cautious. If possible, you should carefully plan and test any changes in a non -production environment. Always ensure that appropriate backup and emergency plans are formulated to minimize the shutdown time.