This "fix" cannot bring back the missing data from the ~128 deleted snapshot files, but it should repair the snapshot chain, which may help you to access, and backup important data.
I've created an empty stub file, so that you do not need to hex-edit an existing file. Please extract the .vmdk file from the attached .zip archive to the VM's folder.
With the file in place edit the VM's settings, and in Options -> Snapshots -> "When powering off:" set "Take a new snapshot" back to the default "Just power off". This option only creates snapshots, but never deletes them automatically. That's why you ran out of disk space. Once done, take another manual snapshot to preserve the VM's current state!
At this point you may now try to power on the VM to see how the guest file system looks like, and how much data you can extract/backup. If the operating system cannot start, there will be a "Plan B" for how to access the guest data. Let's talk about this later if required.
Depending on the corruption, you may need to start with a new VM to which you can restore the extracted/backed up data. Alternatively, it should be possible to reset the VM to the latest stable state, which however is from 12/09/2020. Again, let's talk about this option later.
If you decide to proceed with the current VM, let me know, so that we can do some housekeeping, i.e. manually consolidate the snapshots.
André
Important: If the VM is highly important, don't try the above mentioned steps. Avoid any changes to the physical disk (the H: drive), but run a data recovery tool to see whether some of the deleted .vmdk file can be recovered!
