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.

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

[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?

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

[lakyk]

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

[Kinnison]

Hi,

@PepeRoncinoasked 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%2...

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

[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

[Michael_Uray]

---

@ezhik_ 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.

[MMirabito]

@Michael_Uray 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.

[MMirabito]

@DodgeDeBoulet 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