@jdl69 @ushakiran_9 The underlying issue is that Hyper-V does a very poor job of allowing nested virtualization for third-party hypervisors for its own Hyper-V virtual machines and an even worse job of supporting it for third-party hypervisors. If Workstation detects Hyper-V components enabled on your system, it will use Hyper-V as an upper-level monitor to run your VMs. The workarounds that have been posted disable Hyper-V and any other associated Windows technology that uses Hyper-V components such as memory integrity and workstation based security. You have to find out which ones are enabled on your system (research the posts here in the forum) and get them all. Once those all are disabled, Workstation will use the VMware hypervisor and nested virtualization should work.

The situation isn't going to change until Microsoft fixes Hyper-V. They have started allow nested virtualization for Hyper-V VMs for some AMD EPYC/Ryzen chips, but they've done diddly-squat, zippo, zilch, nada, bupkis, nothing for other chipsets or virtualization offerings. Yet.