MEMORY_MANAGEMENT BSOD on VMware! (25099)

[XenoPanther]

[UPDATE 4/21] Setting the VM to use a single core in VMware allows this build to boot without any issues. 

This is more of a heads up for people trying to install this build in VMware. Most attempts to boot this build in the latest version of VMware will result in a MEMORY_MANAGEMENT BSOD. After several restarts, you will eventually get into Setup/Windows.  Here's a feedback hub link for those who have also experienced this. https://aka.ms/AAgq409 

Does anyone have a physical machine that has 2 or more CPUs installed? If so, can you please try to boot 25099 and see if you get the MEMORY_MANAGEMENT BSOD? I would love to know if this occurs on real hardware

From what I've observed:

25099 with 6 processor cores in VMware: Fine

25099 with 4 physical CPUs: BSODs

[#2]

I think that I just solved this same error. I'm using VMware Workstation and the VM was configured to use 2 CPU with 1 core each. However, my physical computer only has 1 CPU with 4 cores. I changed the VM to use 1 CPU with 2 cores and... Success!

BTW, I had tried upgrades, booting from the 25099 ISO and nothing worked.

The feedback hub post mentioned above (https://aka.ms/AAgq409) actually pointed me in the right direction as it mentioned a CPU Microcode mismatch being the cause of the problem.

[#3]

Can't believe that something so simple was the bane of my existence. Thanks for this, it solved my problem changing it to 1 processor with 4 cores.

[#4]

Works perfcet - THX