Can't Clone VM can't take Snapshots "an error occurred while taking a snapshot one of the parameter"

[Ezra4no1]

Has anyone experienced a similar problem?
I have a new install of Vmware Workstation 16 Pro 16.1.2 build-17966106.

I currently have only one VM created running Win2016.
Trying to take a snapshot and I am getting the following error:
"an error occurred while taking a snapshot one of the parameters supplied is invalid"

I am getting this same problem when I try to clone the VM.

Anyone have any idea how to fix this or what the problem is?

I don't know what parameter vmware is pointing to, but I have ran this same setup before without any problems, only difference now is I am using the new current version of VMware workstation with a clean install on a newly installed OS on the host machine.

The host machine is an older HP DL380 G7 with 160GB of ram with dual Intel Xeon Processor E5645  (I believe) and a raid5 from it's disk array.

[Vikramaditya_J]

Just check snapshot limitations:-

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-53F65726-A23B-4CF...

[a_p_]

Not sure what exactly causes this.

To start troubleshooting, provide some information like the host OS, and the host file system on which the VM's files are stored.
In addition to this create a file listing (dir*.* > filelist.txt or ls -lisa > filelist.txt), the compress/zip the filelist.txt, the VM's configuration (.vmx) file, the latest vmware.log file, and - depending on the virtual disk's file format - the small descriptor/header .vmdk file(s), and attach the .zip archive to your next reply post.

André

[Ezra4no1]

Thanks for the response.

The Host OS in Win2019, File System NTFS
I believe I included the files requested.
Thanks.

[a_p_]

I cannot see anything that explains the issue. I even created a new VM, and replaced the configuration files with your's. The only difference is that I'm running VMware Workstation on a Windows 10 host, but Windows Server 2019 is also officially supported as a host OS.

What may be worth a try, is to start VMware Workstation in elevated mode ("Run as Administrator") to see whether this makes a difference.

André