Getting this error while starting the
Logs attached
Any advice please
==============================================
2023-07-02T22:48:01.433+02:00| vmx| I005: Log for VMware Workstation pid=18128 version=15.5.7 build=build-17171714 option=Release
2023-07-02T22:48:01.433+02:00| vmx| I005: The process is 64-bit.
2023-07-02T22:48:01.433+02:00| vmx| I005: Host codepage=windows-1252 encoding=windows-1252
2023-07-02T22:48:01.433+02:00| vmx| I005: Host is Windows 10, 64-bit (Build 22621.1848)
2023-07-02T22:48:01.403+02:00| vmx| I005: VTHREAD 23932 "vmx"
2023-07-02T22:48:01.406+02:00| vmx| I005: DictionaryLoad: Cannot open file "C:\ProgramData\VMware\vCenterServer\cfg\vsphereFeatures\techPreview.cfg": The system cannot find the path specified.
2023-07-02T22:48:01.406+02:00| vmx| I005: [msg.dictionary.load.openFailed] Cannot open file .....
2023-07-02T22:48:01.433+02:00| vmx| I005: Log for VMware Workstation pid=18128 version=15.5.7 build=build-17171714 option=Release
2023-07-02T22:48:01.433+02:00| vmx| I005: Host is Windows 10, 64-bit (Build 22621.1848)
2023-07-02T22:48:01.598+02:00| vmx| I005: IOPL_Init: Hyper-V detected by CPUID
2023-07-02T22:48:01.690+02:00| vmx| I005: hostCPUID name: 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
From the log, you are using version 15.5.7 on a Windows 11 host with Hyper-V enabled with an 11th Gen Intel CPU.
There is a known problem with Intel 11th gen and newer CPUs when Hyper-V is enabled and the crash is caused by assuming a certain CPU feature is available when it is not. I think this was resolved in version 16.2.x but not backported to 15.x series (hence there is no 15.5.8). So you have two options
(1) Upgrade to the current 17.x
(2) disable Hyper-V on the Windows host (remove Hyper-V, WSL2, disable credential guard, Core isolation memory integrity, etc etc etc)
Please, can you help me on how to
" disable Hyper-V on the Windows host (remove Hyper-V, WSL2, disable credential guard, Core isolation memory integrity, etc etc etc)"
Thank you.
I am using Lenovo P15 gne 2
Turn off Hyper-V, follow this KB
https://kb.vmware.com/s/article/2146361
There could be other items such as Windows Subsystem for Linux, Virtual Machine Platform, Windows Sandbox, Windows Hypervisor Platform that you need to disable.
Make sure that Memory Integrity is also OFF.
Windows Security -> Device Security -> Core Isolation details
If the laptop is a member of an AD domain, things like VBS or Memory Integrity could be enforced through Domain Policy. If that is the case, talk to your AD Domain security admins.
