MEMORY_MANAGEMENT BSOD on VMware! (25099)
[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
I was told by a Microsoft assistant to come here for help regarding an insider update issue.
As the title reads, a Microsoft assistant told me to consult this community regarding the issue I am facing now. A while ago, I foolishly did not read the fine print and opted into the dev channel of the insider program, because I was having difficulty installing Windows 11. I later found out to my horror that, I could not opt out until a particular window was announced. I have been waiting since then, and updating my computer in hopes that one of these updates will allow me to swap back to the beta channel, and then, hopefully to a stable version of Windows. When I attempted to update today to the "Cumulative Update for Windows 11 Insider Preview (10.0.26120.2705) (KB5050636)", I received the "Install error - 0x800f081f" message, and all the results I have searched have so far given me nothing but pieces of advice that make me fearful for the safety of my computer data. Is there anything I can do that will not run the risk of data deletion, or is it hopeless? I feel like I've run down every alley here. Thank you.
