Interesting.
One VM computer = one folder. Do you have something else?
As such, different VMs should have NO effect to each other.
Original Message:
Sent: Dec 19, 2024 09:12 PM
From: mikas
Subject: Windows 11 24H2 cant run any vmware vm's
Seems I got this issue solved to some extent though I still cant say what caused this. What I did:
For one Windows 10 vm:
*Always start workstation as Admin
- Deleted .vmx config file. Created new vm using the existing .vmsd. Configured it as it should be in workstation. Not started actual vm yet.
- Removed the vm from workstation tab, closed workstation.
- Edited newly created .vmx file and removed lines:
numvcpus = "4"
cpuid.coresPerSocket = "4"
- Started workstation, selected just configured Windows 10 vm.
-> VM started as it should (defaulted to one core only) without errors and no more "Module 'CPUID' initialization failed" in log.
- After that I changed cpu parameters back to normal 4 and still everything works.
After this one Windows 10 vm had started once rest of the vm's (other old Win10, Ubuntu, CentOS and new Win10) work now as well. This is without needing to edit .vmx files or other configurations for those. None of the vm's were working previously nor I could create new ones without getting the same error.
Seems like workstation had to reinitialize the CPUID detection one time as this Windows 10 vm .vmx file didn't have any CPU parameters assigned. This is just speculation and I cant say what really caused this even after fresh install of host system.
Original Message:
Sent: Dec 16, 2024 10:27 PM
From: mikas
Subject: Windows 11 24H2 cant run any vmware vm's
Hey. I got the "Collect Support Data" working after another VMWare workstation reinstall and posted that .zip file to this thread. I'll attach the log from the failed attempt to this post as well. From the log file: "Module 'CPUID' initialization failed." which has been the same problem from the start.
Original Message:
Sent: Dec 16, 2024 08:46 AM
From: Doug Covelli
Subject: Windows 11 24H2 cant run any vmware vm's
The support bundle you uploaded was empty. Can you upload a vmware.log file from a failed power-on attempt?
Original Message:
Sent: Dec 12, 2024 06:45 PM
From: mikas
Subject: Windows 11 24H2 cant run any vmware vm's
I am still trying to solve this problem. No old or new VM's (windows, Linux, dos, any) can be started as stated in initial post. I've done multiple VMware workstation pro reinstalls and also cleaned up the remains after uninstallations with Broadcom uninstall guide. Host windows is currently upgraded to the latest December patches of WIN 11 Pro 24H2. Still I get the same "Module 'CPUID' initialization failed" error in logs and vm startup stops "instantly". Any help or pointing to some direction where to look at would be appreciated.
Original Message:
Sent: Nov 09, 2024 07:58 PM
From: mikas
Subject: Windows 11 24H2 cant run any vmware vm's
I used to run Windows 11 23H2 and vmware workstation 16.2.5 with multiple vm's. I upgraded to Windows 24H2 and I was able to run vm's still. (I cant be sure did I upgrade vmware workstation to 17.6.1 immediately or a bit later). Now I run latest patch KB5044384 for Windows 24H2 and I cant run any vm's as immediately at startup I get error: "failed to power on'<xxx>.vmx'. This is true for all vm's and if I try create new its the same outcome. I suspect that the KB5044384 patch broke something but I cant be sure nor I cant roll back. I've tried with hyper-v and/or hypervisor platform on and off. Fully disabled VBS, credential guard etc. and the outcome is always the same. Only thing wrong I can see from the logs is: Module 'CPUID' initialization failed. Its exactly the same regardless if VBS, Hyper-v etc. is on or off. I can run VirtualBox with or without hyper-v hypervisor wit no problems. Is there something that I am missing and how could I fix this except reinstalling host to older version?