Windows Server 2022 21H2 after trying to install 2022-07 KB5015827 CU get BSOD on VMware

Seyyed Soroosh Hosseinalipour 21 Reputation points
2022-07-14T18:01:56.563+00:00

ITNOA

I have Windows Server 2022 (21H2) on VMWare (16.1.2 build-17966106) on Host (Windows 10 Pro for Workstations, 64-bit (Build 19044.1826) 10.0.19044)

When Windows try to update and installing KB50145827 CU, after restarting Windows (In installing procedure) I got a BSOD with error: Unsupported Processor

220856-image.png

after I try to boost system in safe mode, Windows try to undoing the update and after restarting , work properly,

220875-image.png

But the problem is Windows try to update again, and all story occurred again :(

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,051 questions
Windows Server Setup
Windows Server Setup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
252 questions
0 comments No comments
{count} vote

8 answers

Sort by: Most helpful
  1. Mauricio Piccolo 1 Reputation point
    2022-11-22T14:47:41.777+00:00

    maybe this is related to https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-Server-2022-21H2-after-trying-to-install-2022-07/m-p/2940024#M178747

    the "1 vcpu" workaround did not work for me (i7-12700 cpu, even disabling e-cores did not help). but after upgrading to Workstation 17 Player, the update suceeded and everything is back to normal.

    0 comments No comments

  2. Sergio Luiz Novaes 1 Reputation point
    2022-11-22T16:36:06.997+00:00

    yes, vmware player 17 solved the problem.


  3. Jacob Feindt 6 Reputation points
    2023-01-10T18:45:08.687+00:00

    I was having the same issue. Another resolution which appears to have worked for me was removing the Windows Subsystem for Linux, per VMWare KB Article: https://kb.vmware.com/s/article/90134

    Followed this post on removing: https://pureinfotech.com/uninstall-wsl2-windows-10/

    This is a viable workaround for me for the time being, I was just WSL to mess around and didn't really need it for my work currently.

    Hope this helps. -Jacob

    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.