"UNSUPPORTED_PROCESSOR". Workstation 17/Windows 11 23H2.

[Argh Bath]

As a paying customer I should have access to Support but Broadcom's Support infrastructure is an absolute disaster so it looks like free Community support might be all my money buys in 2024.

I am running VMware Workstation 17.5.2 on Windows 11. When I set up a Windows 11 VM under "easy" default settings I receive a BSOD when Windows 11 boots with the error "UNSUPPORTED PROCESSOR".
The short-term fix for this is to reduce the amount of virtual processors for the VM to 1 so it runs like dirt.

Is this a known issue pending a fix?

[Dhairya Tomar]

@Argh Bath When you see this BSOD issue, again, suspend the VM at the BSOD screen, go to the VM directory by right clicking the affected VM in the library pane->Click on Open VM directory, locate the .vmem and .vmss files and share them here.

Also request you to share the support bundle of the affected VM using below-

Help->Support->Collect Support Data.

[dfadf vebor]

1.  Try changing your "Guest OS" settings to "Other 64-bit"  (Virtual Machine Settings ---> Options ---> General ---> Other ---> Other 64-bit).
   
   
2.  This worked for me while trying to get "Windows 7 (x64)" working again, with two processors enabled, and after all of the updates got installed.
   
   
3. Otherwise you are stuck using a single processor with "Windows 7".

[RaSystemlord]

There is nothing wrong with 17.5.2 and Windows 11, in a general case. You did not share the hardware that you are running - so, difficult to speculate. The version of VMware per your hardware - the error message could be right as well.

The is no "easy default settings" - you need to understand how you configure your VM. I don't care what the GUI is suggesting for "easy".

Since 2024 November - you are not paying anything. Workstation if Free - thus there is no customer support Per your money that you are paying. I mean, not anymore, early 2024 there was, when you posted this.

[dfadf vebor]

UPDATE:

1.  I stand corrected.
2.  Looks like the virtualization software won't let you use more than one processor for Win7.
3.  After some more testing, Win7 likes to lock up when using 2 or more processor cores and using a different "OS profile".
4.  I'm sure this will be the case with other Guest OS' that are getting the BSOD when using 2 or more processor cores.

[Argh Bath]

Something fixed it, I don't know what. I don't need help with this anymore and looking at my inbox I regret posting the thread.

RaSystemlord, for the sake of the community I would advise against replying to anyone else's threads.

Thanks and respectfully, please stop posting here so I don't get any more emails.

[RaSystemlord]

Argh Bath:

For the sake of understanding this Forum, you need to understand that this Forum has a mind of its own and changes every week. Sometimes, the Answer comes before the Question - just as one example.

In this thread, there was and is only one possibility "Answer", which I used. My comment was a direct answer to your question - which somebody else commented just recently.

This IS a discussion Forum, where I DID give a relevant answer. If you don't like to get answers, do not post questions. I have no idea what you mean by "somebody else", because I was answering you who gave the original question. Furthermore, if you cannot handle e-mails, you can change your setting for NOT getting e-mails - I hope that works in this Forum, if it doesn't, don't blame me.

Perhaps, you are confusing this thread to something else. Or perhaps you mean the Win 7 discussion - not commented by me.

Or perhaps you are looking at this conversion through an e-mail thread - that gives a completely different approach who is who and is confusing in other respects, too. I am looking at THE FORUM to see who is saying what.