Windows 10 KB5019959 crashes into BSOD

[Ferko]

Hi,

 

I have tried to install November update for my virtual Windows 10 22H2 KB5019959 in Vmware Workstation 16 Pro latest. Unfortunately after restart of the virtual machine it always crashes into BSoD with CODE UNSUPPORTED PROCESSOR.After few BSoDs, Windows recovered into previous version but also my second try ended the same.

I have Intel 12. gen. Any hint how to overcome this issue? Thanks.

[DrRFreund]

Same for me. Installed cumulative update KB5019959 in Windows 10 VM (used for several years, always installed newest Windows-updates without problems), rebooted, got BSoD with Stop-Code "UNSUPPORTED PROCESSOR". Rebooted again and Windows 10 was automatically repaired. Windows-update-dialogue says, that KB5019959 could not be installed (error-code 0x800f0845) and was removed. Clicking on "Retry" provides the same result again. I've tried some workarounds, which I found in the Internet (Windows-update troubleshooter, scans with SFC and DISM, cleared Windows update files in C:\Windows\SoftwareDistribution\Download), but nothing did help.

[gbdutch]

Yep same here and same with the November updates for Windows 11 in a VM - something they changed is causing the issue in both OS's. Setting the VM to a single CPU core will get around it temporarily but either VMware or Microsoft needs to patch it. 

[HHPCIT]

We are also seeing the same things with Windows 10 21H2 VM's.  I've tried manually installing the update with the same result.  An example host is running Windows 11 Pro 21H2 with an Intel Core i7-11700 and 64GB RAM running VMWare Workstation 16.2.4 build-20089737.  

[HHPCIT]

I can also confirm that setting the VM to a single CPU works.  It's not ideal, but it works.  I did take a snapshot after successfully updating and set the CPU's to 1 socket, 4 cores and started the VM.  It resulted in the same UNSUPPORTED PROCESSOR error.  Reverting the snapshot (which set it back to 1 socket, 1 core) allowed the VM to start again successfully.    

[SangHLee]

I am seeing exactly the same error here on two separate guest windows 10 pro VMs. I am on intel 10th gen (Intel(R) Core(TM) i7-10710U), 32GB RAM with Windows 11 pro host. VMWare Work Station Pro 16.2.4

[Alphaleonis]

Same problem here with 12th gen Intel 12900K CPU and latest VMWare Workstation 16 Pro and a Windows 11 guest after latest Windows updates (on the guest) I got BSOD with UNSUPPORTED_PROCESSOR. After a couple of failed boots it seemed to automatically revert the update which allowed me to boot the guest.

[ThoJa]

Same for me on a Surface Pro with Intel(R) Core(TM) i5-4300U CPU @.

[BrennM]

the same here. Lenovo Thinkpad L15 Intel i5-1145G7

[LBrin]

Seems I'm having the same issue. Dell XPS 17 Intel i9-12900HK

[StanKatz]

Same issue on the same laptop.

[Tremar]

Same issue as of Dec 15 2023
Everything is fine till I do the windows updates and then Bam BSOD.
Wkstn Pro 17

Ciao
KJ

[jordanreedy]

Experiencing this issue as well. Details below:

Yesterday, we installed KB5019959 on two guest VMs, each Windows 10 Enterprise LTSC Version 21H2 Build 19044.2251. It works on my host OS, but not my coworker's. Stop Code: UNSUPPORTED PROCESSOR

My host OS information: Windows 11 Pro Version 22H2 OS Build 22621.674

Coworker's host OS information: Windows 10 Pro Version 21H2 OS Build 19044.2130

Removing the update on the guest OS works, but as stated earlier I don't have the problem on my Windows 11 host machine, only on Windows 10 host machine. I'm going to continue troubleshooting with some version upgrades and such. I'm willing to provide logs and further troubleshooting to try to get this resolved.

 

 

The below info is troubleshooting I tried but didn't fix this issue:

In my initial troubleshooting, I attempted a potential fix mentioned in another forum post: (1) Latest Dev Channel builds of Win 11 fail to instal... - VMware Technology Network VMTN. 

This did not fix, but did give a new Windows Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED

This allowed us to use 1 processor, 2 cores instead of just 1 processor, 1 core. But it did not fix the issue.

Please note, if you try the fix mentioned in the article, you'll need to reset 

bcdedit /set hypervisorlaunchtype auto

in order to get your machine to use more than 2 cores once you remove KB5019959.

 

[gkobler]

Same to my notebook with intel i9, with 1 CPU it works. No problem on my desktop PC with AMD. At the moment no solution or workaround ahead.

[jordanreedy]

My coworker and I are having the same problem. His Win10 Guest machine throws the stop code: UNSUPPORTED PROCESSER after the November CU. The same guest machine will open in my Workstation no problem. Specs are below, I hope it will help troubleshooting.

My host machine: Windows 11 Pro Version 22H2 OS Build 22621.674

Coworkers host machine: Windows 10 Pro Version 21H2 OS Build 19044.2130

The guest OS specs are as follows:

Windows 10 Enterprise LTSC Version 21H2 OS Build 19044.2251

Rolling back the update fixes immediately.

[ig-andrew-edney]

I tried one of the approaches suggested on the internet - giving the guest machine just 1 CPU (single core). That allowed it to do an update when it would not work before.

[ig-andrew-edney]

Trying to add back the extra CPU cores after the updates just brings back the BSOD - so you have to be happy with a single core VM if you install updates. Hope this gets fixed soon.

[Technogeezer]

Is Hyper-V being used as the virtualization monitor. Check the vmware.log file and see if the Monitor Type is ULM, and not CPL0.

There are posts in social media that's describing a problem with Windows hosts with Hyper-V enabled and running Windows 10 or 11 VMs with the latest Microsoft updates. The posts also say VMware is aware of this, has fixed it internally, and will be shipping a fix in the upcoming Workstation major release (shipping next week). 

[ig-andrew-edney]

Monitor mode is ULM (I am running both Hyper-V and VMware on my laptop). Good to hear that a fix should be on its way.

[chweyd]

Same here - BSOD after the latest Windows 10 upgrade but also after upgrading to Windows 11. With a single CPU no problem except that it is very slow. The recommended deactivation of hypervisor did not help - with more than one. CPU we immediately see a BSOD. Now I deactivated automatic updates and wait for a patch from VMWARE. 

Question: is that issue only affecting VMware workstation or is the player affected too?

[bmarin777]

Hi,

"upcoming Workstation major release" means that it will be available in version 17 of the Workstation, or would it be available as a "normal" update?

I had the same problem with Win11 as well in reply to another contributor saying that with Win11 the update works ...

Thank you

PS Actually I just saw the updates on the thread, and my question is answered. Thank you

[MarkPfeifer]

Workstation Pro 16.2.5 was released today with a fix for this issue.

[KeithCarter]

Downloading and installing now!  Thanks for the heads up!

[ig-andrew-edney]

I have downloaded and installed it and it works!

No need to upgrade to version 17, so that's a good saving.

Took a while, but they sorted it and that is what counts.

[Ferko]

General support for version 16 ends next Thursday so not upgrading to version 17 is just a temporary workaround imho. Unless someone plans to disable Windows updates from now on, this might reoccur also in future.

 

Product Lifecycle 

[ojm]

I have never liked Hyper-V, but I can't trust VMware any more. Even after paying for v17 upgrade, the odds of this happening again reset every 30 days, and could re-nuke my environment up to 12 times next year. Entitlement to updates is great, but there's still potential costly downtime between those updates.

[gkobler]

Found a workaround

 

Disable the Hyper-V, this helped on my PC

bcdedit /set hypervisorlaunchtype off

After issuing this command, then reboot the system

To re-enable Hyper-V, you can issue this command:

bcdedit /set hypervisorlaunchtype auto

and then again reboot for the change to take place.

 

We had the same problem before, see the following link

https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16-1-2-Pro-under-Windows-11-host-Windows-guest-in-VM/td-p/2870506

 

[BrennM]

:That works for me too.

[ThoJa]

Workaround is OK for me.

[Johan_Melander]

Error in reply

[lutz]

Same with me Processor I7-9700, windows Host win10 22H2 and guest win10 22H2, no Hyper-V nothing, always crashes with BSOD when installing Nov22 update.

Waiting for a real solution, 1 Core is not sufficient

[cdickey1]

I also get the BSOD which just started when trying to apply the latest automatic Windows 10 Update by Microsoft to guests
The BSOD happened with VM Workstation 15
I upgraded to Workstation 16 and most recent compatibility to see if that fixed it
Same BSOD with Workstation 16

A Dell computer with Intel i9-9900K CPU

Before this Microsoft Windows 10 update BSOD I have been running VMWare on this computer for a couple years with no problems

The Windows 10 Update completed on the host OS with no problems
The BSOD happens when trying to update a guest OS Windows 10

A lot of people using VMWare Workstation 16 have the same BSOD problem
Has there been any news from VMWare support about this and a solution?

 

 

[zboise]

Problem solved.

First, my Xeon desktop is not having the issue, only the 12850HX (new laptop).

Did not have problem under Windows 10 before 22H2. On Saturday, upgraded to W11 and applied updates to VM (W10). That's when it started to happen.

I've been focused the entire time on the VM, however, after recopying the VM from original source, rolling back updates, etc, I could not get around the problem. So now I am wondering if the upgrade to W11 on host also has something to do with it.

I reverted back to Windows 10. But then VMWare would not work. Not even Player. Finally got a new install of Player installed and it greeted me that Version 17 was available. Getting rid of Pro16 was difficult due to Windows downgrade, however, I then was able to install Version 17 Pro and VM with 8 cores assigned screams!

I'm sure many will not be happy to upgrade to 17, I'm just glad to get back to work again.

[smatoa]

I had the same issue after applying KB5019959.

I was able to avoid it by using 1CPU

coexisting with hyper-v
I was able to avoid it by turning hyper-v to "OFF" with the following command
"bcdedit /set hypervisorlaunchtype off"

sorry for the english of the translator

[smatoa]

I had the same issue after applying KB5019959.

I was able to avoid it by using 1CPU

coexisting with hyper-v
I was able to avoid it by turning hyper-v to "OFF" with the following command
"bcdedit /set hypervisorlaunchtype off"

sorry for the english of the translator

[ONI_Assassin]

I wonder if turning off core isolation on the host would help.

[Kinnison]

Comment removed...

[ONI_Assassin]

It seems to disable features etc, isn't the correct solution, but rather VMWare needs to spend time working on their product to work with more modern security practices and features.

[Kinnison]

Comment removed...

[DLF_UK]

Having this issue, Windows 10 host, Windows 10 guest. 

 

Hyper-V is turned off, I don't use it, so for me at least that can't be the cause/fix for this issue.

[ONI_Assassin]

Update:

Didn't work

[Virtualmee]

Same problem as all of you, different processor though so clearly major defect on VMWare side.

[Pukkio]

Any other workaround or solutions? I can't disable Hyper-V becouse I need it for android subsystem, and setting only 1 cpu the VM is incredibly slow

[KleberBueno]

Hi folks

Same issue here since Saturday.

Disabling Hyper-V did not fix it. Also, it is impossible to uninstall the update because KB5019959 is a permanent update. Tried to restore VM guest Windows 10 to some point before the update. Did not work as well.

Hopefully there should be any update from either VMWare to Microsoft on it.

 

[tfletch87]

I am seeing this same issue on Server 2019 after updating to the latest Windows updates. I rolled them back but still had the same issue. I came in today to pick back up where I left off, and somehow it magically is working. (Without updates applied.) Not sure what could have/would have changed. I still have another machine in a broken state though. Would seem November updates changed something with virtualization. I updated to the latest version of VMware Workstation Pro 16 as well to no avail.

[ojm]

This issue has cost several days of development downtime, and the entire weekend to recover. Microsoft and VMware are mature enough that this type of issue should not happen. Windows 10 22H2 host, no Hyper-V, latest Workstation Pro 16.x, no previous issues like this for several years running. 

[simon_hslu]

I have the same issues.

After i uninstalled VMware Workstation Pro and installed the Tech Preview 22H2 it worked for me without any issues. Multiple CPU's and multiple Cores. This is not adviced for Producive systems but for me a Workaround until they implement the fix.

[YetAnotherChris]

In my case...

Clean install of Windows 11, 22H2, with Workstation pro 16.2.4 as the host.  Everything was working perfectly UNTIL I enabled Memory Integrity when prompted by the windows security center app thing on the host.

After enabling that and rebooting I started having this same issue. Nothing I tried resolved the issues until I went back and turned it back off.

My bad for wanting to be "protected" lol

Maybe try turning that off if you have it enabled and are running a system like mine?

[JMorgenthaler]

Chris, like you, my host machine was Windows 11 22H2 and running latest workstation pro.  And like everyone else, I was getting the error on my Windows 10 VM system trying to install KB5019959 (processor error message, etc.) 

I just tried your suggestion of turning off the "memory integrity" security setting on my Win11 host and then tried installing the update on my Win10 VM.  And what do you know...the dang thing worked this time.  Unbelievable.  Your "fix" definitely worked for me.

For those of you getting this error, give it a try.  To turn on/off the memory integrity setting see https://windowsreport.com/memory-integrity-is-off-windows-11/

When I had it turned on, Workstation prompted me to disable "Side Channel Mitigations" (see https://kb.vmware.com/s/article/79832) which I had done.  I re-enabled this option after turning off the host memory integrity option. Don't know if it would have made any difference for the Win10 update install or not but since these were the only 2 system changes I had made recently I figured I would undo both of them to see if it fixed the problem.  I will be reenabling these options now that the update has been successfully applied but I'll keep in mind if any future updates cause the same problem.

 

[KleberBueno]

The only solution that worked for me so far Thanks  .

[lutz]

is anybody of VMWARE or MS aware of this problem ?

i have no hyper-v win10 22h2 on workstation and in VM latest vm workstation still nobody working on it ?

How to make VMWare and MS taking notice of this problem ?

[Technogeezer]

---

 wrote:

is anybody of VMWARE or MS aware of this problem ?

i have no hyper-v win10 22h2 on workstation and in VM latest vm workstation still nobody working on it ?

How to make VMWare and MS taking notice of this problem ?

---

Just because you have "no Hyper-V" on your PC doesn't mean that the components aren't there and VMware isn't using them. Virtualization Based Security, Device Guard and Memory Integrity all use pieces of Hyper-V. You need to not only disable Hyper-V in the host, but perform the bcdedit command to modify the hypervisorlaunchtype attribute (set to off, it's set to auto by default), and make sure Memory Integrity is disabled. You may also need to disable Virtualization Based Security and Device Guard.  All of them need to be done for Workstation to revert to using its own hypervisor instead of Hyper-V.

VMware is aware of the issue. A social media post indicated they have an internal build that has a fix. They have hinted that the real-soon-now Workstation 17 contains the fix. I would hope that VMware would also realize the amount of pain this is for their customers and release a final update to Workstation 16 that also fixes this issue. I'm not hopeful they will do that though.

Prior replies to this thread also indicate that the Workstation Tech Preview 22H2 fixes this issue as well, so you might want to give that a try while waiting for the Workstation 17 release. 

[ojm]

Workstation 16 to 17 upgrade had better be FREE, unless they patch 16 to fix the bug. If they try to charge money to fix this problem, they shouldn't be surprised if v17 is the most pirated version to date.

[Technogeezer]

---

 wrote:

Workstation 16 to 17 upgrade had better be FREE, unless they patch 16 to fix the bug. If they try to charge money to fix this problem, they shouldn't be surprised if v17 is the most pirated version to date.

---

To be fair this worked until Microsoft provided their latest update.. An equal amount of vitriol should be directed at Microsoft for making changes that break the competition’s products.

That being said, I agree that VMware needs to provide a fix for WS 16. WS 16 is under support until 12/22/22, and a paid upgrade to fix a bug is not customer friendly behavior. 

  can you comment on this? 

[Michael_Uray]

How can you actually report such a bug to VMware?

The support page did not allow me to send a support request, since it was not possible to chose my WMware 16 Workstation licence as product.

[gkobler]

May you have to buy seperate premium support

[wydnaa]

Same problem for me.  I have several Win 10 VMs, all trying to install updates KB5020694 - .NET Framework updates and KB5019959 - Win10 22H2 update.

Workstation Pro version 16.2.4 build-20089737.

I can't be sure which of the updates is causing the BSOD.

The much repeated workaround disabling Hyper-V didn't work for me.  Working with a single core VM won't work for me!

Thankfully, Win 10 guest recovers after the BSOD, but this really needs a proper fix.

[ezhik_]

To summarize:

A recently released set of Microsoft patches can cause an issue for Windows 10 and Server 2019 VMs. The stop code is:

"UNSUPPORTED PROCESSOR"

In particular, these two KBs:

KB5019966 - Windows Server 2019
KB5019959 - Windows 10

Recovery procedure:

1. Turn Off VM
2. Change Settings of the VM:
   a. Processors:
   - Sockets: 1
   - Cores: 1
3. Turn On VM
4. Login as an admin
5. Navigate to Control Panel > Programs and Features
6. Select "View installed updates" on the left side
7. Find Update with KB5019966 or KB5019959 and Uninstall it
8. Once successfully uninstalled, restart and shutdown the VM.
9. Revert to the original settings of the VM:
a. Processors (example):
Sockets: 1
Cores: 2
10. Power on the VM

The VM should now boot in desired hardware configuration, however the windows update package would still be available for download as it has been reverted. It appears the issue is with Microsoft and VMware and until the patches come out for both products, you might either be stuck with missing security updates or performance impact due to a single socket/core configuration.

The usual maintenance should be done once the systems are booted up again:
1. Schedule disk check:

chkdsk /f

1. Fix and cleanup the OS image:

dism /online /cleanup-image /restorehealth

 

[dgenemiller]

Core Isolation - Memory integrity is what what causing the issue with my instance.

After turning off core isolation reboot Win11 Host the KB50199559 installed with 2 proc 2 cores.

I have since updated the Win10 VM to WIn11 and tried to reenable core isolation and get incompatible drivers pop up.

 

The safenet Inc drivers look to have issue with the new update.

[Virtualmee]

Memory Integrity is off on my Win 10 64 Pro and still fails.

[sasten]

As a data point my vmware windows 10/11 virtual machines fail the MS Nov22 updates as described in this forum while my hyper-v windows 10/11 virtual machines update without issues.

[ryank3]

I am also experiencing this issue on both Windows 10 and Windows 11 VMs

[KeithCarter]

Also experiencing this issue with my Windows 10 VM.  The KB5019959 update also seemed to mess around with a lot of clock/time issues as well.

[KleberBueno]

It is an endless problem. After uninstalled Workstation Pro 16 and installed Tech Preview version I got it working again.

Today morning my host was updated with update KB5020030. Now none of the VMWare versions are working anymore. Microsoft windows update is a black box.

 

 

 

[gkobler]

V17 are release today, and it works with enabled Hyper-V

[ig-andrew-edney]

And you have to pay to upgrade (in the UK it is showing as £84.16) - so the question is, do I care enough to bother?

[ONI_Assassin]

I can confirm WSP17 does resolve the issue with the update; just waiting to check stability, but everything so far looks good.

[cdickey1]

I contacted tech support and got a phone call. They are aware of the BSOD problem. I was told I would get a license for Workstation 17 by December 1 since I bought v16 recently. Apparently the problem will be fixed with v17.
There may also be a preview version of v16 that has fixed the problem.

[Ferko]

Hi,

I see Workstation Pro 17 is out now. Did you or anyone else tried it already if the issue is fixed there? I expect Vmware fixes such bugs also for version 16 as the end of support has not yet come. Thanks.

[DodgeDeBoulet]

It's fixed for 64-bit Windows 10 guests. There is at least one report that it still occurs with the 32-bit version.

[Kinnison]

Comment removed...

[DLF_UK]

That's irrelevant. I've no interest in upgrading, I just want them to patch the version I've already paid for, which they have apparently abandoned Windows guest support for, less than a year after I purchased it.

[Kinnison]

Hi,

asked a question that may be of interest to both him and others to which it was easy to answer "without inviting him to look for it on his own".

Regards,
Ferdiando

[ojm]

Currently, this link contains false information. VMware Workstation 16 does not support Windows 10 or 11.  How do I get my money back?

https://kb.vmware.com/s/article/80624?lang=en_US&queryTerm=vmware%20workstation%20pro%2016%20sales%20licensing%20compatibility

VMware Workstation 16 supports hundreds of 32-bit and 64-bit guest operating systems. 
Here is a list of the most popular:

• Windows 11
• Windows 10
• ...

[Ferko]

I have one additional question. Is everyone with this issue running Windows 11 as host operating system? It seems to me as OK when host is Windows 10 or older. Even the Microsoft updates are installed correctly on its guest Windows 10.

If it is so, then we have to probably upgrade to Workstation Pro 17. 16 was not designed for Windows 11 as host system and it had already some problems with it. WPro16 can run Windows 11 as guest without problems on Windows 10 as host system. Or  

[ig-andrew-edney]

I hit the same problem using a Windows 10 host running a Windows 10 guest.

[Ferko]

Thanks for that. THen I guess Vmware should fix it also for 16 as support phase will end in December 2022. I was not sure as according to VMware Workstation 16.x Pro sales, licensing, and compatibility FAQs (80624) host OS can be only Windows 10 or older.

[PepeRoncino]

This BSOD issue definitely lacks some official VMware statement re v16 bugfixing. I'm still using W10P 21H2 as host/guest OS. I had to set automatic windows updates for all guests on hold, because Windows built-in self repair did not work and one VM could not be reanimated so far. So, what happens now? As already mentioned in a previous post I upgraded to v16 six weeks ago. Didn't find any official statement indicating that v17 was in the works and what essential features it would bring. Also remember well as a longterm customer/user (10+ years) that "transition"(upgrade)/support periods were much longer ...

[adamrd]

ignore me

[lakyk]

I had same BSOD problem with Workstation 16 and after upgrading to 17 it installed KB5019959

[PepeRoncino]

As I bought WSPro v16 about five weeks ago it would be nice to know more regarding the "transition period"/entitlement for a free upgrade to v17. Can anyone clarify?

[JanBreet]

Any update on this?  We as end users can't log support tickets - so we have no way to get this resolved except by buying the update 17?  Does anyone have a number we can dial?

[ezhik_]

Latest from VMware:

“””

The recommendation for the trial version usage at the moment has been suggested in an internal discussion. I would also like to inform you that our engineering team is actively working on the possibility of a workaround/resolution on version 16.

”””

[RU5]

Hello all. I would just like to add that although this issue is supposed to be fixed in 17.0, it is not for me (Windows 11 host, 2xWindows 10 guests, one 64-bit and the other 32-bit). Just putting this out there as others may also be (un)affected after purchasing an upgrade to VMWare.

[opo_vm]

I am having same problem with window 10 LTSC version,

it is working stable in version 1809, the problem will happen if update to 21H2.

 

[thommo101]

Having this problem too. Win 10 21H2 x64 host running VMware Workstation 16 Player. Guest is also Win 10 21H2 x64. Currently using the guest as an isolated internet access machine.

After seeing some stating that version 17 fixes the issue, I upgraded Player to 17. 

However now in VM Workstation 17 Player I'm unable to pass through any USB devices. They simply don't appear in the Player->Removable Devices list at all. I had no issues passing through USB WiFi adapter / USB storage in Player 16.

[ezhik_]

I reached out to VMware in an effort to get a statement, a resolution (patch for v16) or a license upgrade to v17 considering it is the version that actually works properly.

Licensing team was not able to find resolution and deflected to the Technical Account manager who did not respond to several inquiries.

Not a pleasant experience so far. Staying professional here, but this clearly does not align with my expectations for a problem resolution for the software that costs $150 and in need of upgrades every few years...

Based on this experience, I honestly cannot say that VMware support has the highest standards on customer satisfaction. Basically, you are on your own at this point.

[ezhik_]

Hello *,

I hope you are well,

My name is * General from the Licensing Team and I'm following up on behalf of my colleague that is currently out of the office.

At the moment, there is no free upgrade for Workstation 17.To have access to this, you can access to the vmware store and purchase the upgrade: https://store-us.vmware.com/


Regards,
* General | Associate Support Specialist
Support Specialist Team, VMware Inc.
Heredia, Costa Rica
Working Hours:9:00 am – 6:00 pm CST

[ojm]

VMware has breached the terms of the licenses we purchased, and their response is "give us more money".  

[Michael_Uray]

---

 wrote:

I reached out to VMware in an effort to get a statement, a resolution (patch for v16) or a license upgrade to v17 considering it is the version that actually works properly.

---

How did you actually get in touch with them?
I did not find a way to contact their support. If I am logged in, then the system tells me that I am not eligiable for support at this product. I bought this product just 5 month ago and now it is not working anymore.

[Max Mirabito]

 and all, 

I am having the same problem with Pro 16.2.4. When I launch my Win 10 VMs they do a windows patch then a reboot, I get 2 blue screens and it eventually uninstalls the patch and recovers.

But in reading this thread does it mean that WMWare does not plan to patch 16.x?

Additionally based on: "...V17 considering it is the version that actually works properly..." can I assume if I move to Pro 17.x the problem will be fixed? Has anyone actually tried 17 to verify?

Thanks in advance,

max

[DodgeDeBoulet]

I experienced the exact same issue with Pro 15.5 and the upgrade to 17 resolved it. For what it's worth, I'm also seeing a significant performance boost.

[Max Mirabito]

 Thanks for the confirmation.

Interesting so this does not appear to only affect 16.x. Maybe whatever patch Microsoft sent out is breaking VMWare pro regardless of version?

Anyway, I guess I will need to upgrade to 17 sooner than expected - the blue screens and recovery is getting annoying  at least for me. Beside I worry that at some point the VMs will no longer be able to recover, then I am toast.

Thanks again, 

max

 

[Zouhdi_El_About]

Having the same issue here. My Host OS is Win11, but vmware workstation thinks its Win10.

I have several Win10 guest systems, with all Windows-Updates on hold.

Having only 1 processor works for tzhe update, but not for my work, so thats not an option.

I've purchased vmware workstation 16 like 6 weeks ago, and i'm quiet unhappy with this situation.

Submitting a support request is also not possible for me, because my entiled account shows no products. An vmware employe advised me to register my license, but here comes the next issue: thats not possible, according to vm-website because of an "error" (no further explanation). 

I feel like this issue wont be fixed, so an upgrade to version 17 is the only way.

Cant call it a satisfying experience.

[Max Mirabito]

I can confirm that when I upgraded to VMware 17 Pro my exiting Win 10 VMs are patching  properly (VM configuration 4 CPU 12GB RAM) see screenshot below.

As indicated in other replies the 17 upgrade fixes the patching and blue screens. But what's not clear to me is why VMWare does not want to patch 16 so that people are not forced to upgrade. 

Thanks,

max

 

[ojm]

It's clear to me that VMware doesn't want to Patch 16 because they see this as an opportunity to squeeze free money out of their customers without honoring their licensing terms. Since several of my VMs were destroyed by the BSOD bug, I have to rebuild them anyway, so this is a good time to abandon VMware. I'm in the middle of rebuilding the lab environment in Hyper-V. Microsoft supports Windows 10/11, while VMware might nuke your environment at any time, without warning.

[jrg2]

The problem is definitely triggered by a change coming from Microsoft in KB5019959.

I'm running Ubuntu 18.04 as the host VMWare Workstation Pro 15.5.7 and all my 64-bit Windows 10 VM's have applied KB5019959 just fine - no problem.

Its only my 32-bit Windows 10 VM's that are BSOD with SYSTEM THREAD EXCEPTION NOT HANDLED.

Unfortunately I can't upgrade to v16 or v17 of VMWare due to this issue here which VMWare has ignore for almost a year.

My system dual boots and even when I run Windows 10 x64 as the Host the 32-bit Guests still BSOD on KB5019959.

I really don't think VMWare reads any of these boards anymore

[ezhik_]

So I have been going back and forth with VMware on this. Seems like issuing a free upgrade is not going to be an option, but here is what they advise, which sounds absurd:

Thank you for your email.

The action plan is to download and install the 30-days trial version of WS Pro 17 which should not need any license for activation and also fix your issue.

Once installed, you can upgrade the hardware compatibility of your VM to Workstation Pro 17 by doing a right click on the VM-->Change hardware compatibility on WS Pro app.

Once we have an update on version 16, you should be able to unsinatll WS Pro 17 app, install version 16 again which should activate using your WS Pro 16 license. You will be prompted to downgrade the hardware compatibility of the VM back to version 16 but in case it doesn't, please right click on the VM-->Change hardware compatibility on WS Pro app to WS Pro 16.

Let me know if you have any concerns with this, I will make sure to reach out to you as soon as I have a substantial update for version 16 on this.

Have a great day!


Regards,

[ohtakajp]

Same for me. 

[foobar4711]

16.2.5 solved it for me

[zPFmc2LQqU5tsy8]

Installing KB5021237 causes the same problem. Reducing to 1 processor core or installing 16.2.5 also solves the issue.

[Fezzik]

Latest update fixed the issue for me as well.

Needed to install Windows Hypervisor Platform as part of install for 16.2.5.

[mobiusstrip]

Has anyone else seen this issue re-appear? Like most, I updated VMware Workstation clients to 16.2.5 or 17 a couple months ago to resolve this problem. However, it recently started occurring again on VM guests running more than two cores. Reducing the number of cores prevents BSOD but makes the VM unusably slow.

The BSOD is a little different this time; SYSTEM THREAD EXCEPTION NO HANDLED

 

[ig-andrew-edney]

I've not seen anything go wrong so far...