btmp's Accepted Solutions

@wilahas a good point if this might be a constant thing. If it's a one off instance you could probably get away with just mounting (It's actually called 'Map...' by Workstation) the VMs drive (while it is shut down) and using windows explorer (on the host) to cut it from the mounted VM drive and paste it directly to your desired location. If it's not a one time thing you could also consider adding the target location as a Shared Folder inside the VM (with tools installed) and only enable it when you want to move something there [or if you aren't worried about it you could also leave it enabled] or potentially even just save the files directly there so that both the Host and VM can access the files (Only one or the other, at any given time, will be able to write it that way. Neither can write to said file while the other has it open) -I do believe that the user (in the VM) will need Admin rights to access the Shared folder for use this way.

2021-08-04T18:56:23.724+08:00| inst-build-17171714| I1: BaseDriverManager::DifxApiLogCallback: vmx86 (Difx): vmx86.inf: checking signature with catalog 'C:\Program Files\Common Files\VMware\Drivers\vmx86\Win7\vmx86.cat' ... 2021-08-04T18:56:23.771+08:00| inst-build-17171714| E1: BaseDriverManager::DifxApiLogCallback: vmx86: Signature verification failed while checking integrity of driver package 'vmx86.inf' ('C:\Program Files\Common Files\VMware\Drivers\vmx86\Win7\vmx86.inf').| winerror code 2148204809 (A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.) My first suggestion would be to ensure you have updated the Win7 Host. Specifically with KB4474419 to ensure it can validate SHA2 Digital Signatures.  

The dump shows a SYSTEM_SERVICE_EXCEPTION related to ntoskrnl.exe That in itself isn't all that helpful so I'll have to default to a rather generic suggestion: Update Everything...Start with Windows, Make sure it has the LCU. Then worry about updating VMWare Workstation 15 to version 15.5.7-17171714 and last but not least don't forget your other system drivers such as your those for your GPU. Once you've ensured everything's up to date, try again and see if it still happens...good luck!

Looks like a missing media file not included in the N version by default. Adding that should fix the first at least and we can hope that it gets VMWare Workstation rolling as intended for you. https://www.microsoft.com/en-us/software-download/mediafeaturepack