Installed WorkstationPro version 15.1.0 and upgraded to 15.5.7 and finally to 16.2.4 on Windows 7 Pro 64. The installation process for 16.2.4 seems to require Windows6.1-KB3033929-x64.msu as a pre-requisite. After upgrading to 16.2.4 I am not able to launch any of my previously working virtual machines. I have attached screenshots of the two error messages. I would be grateful for any comments. One of the error messages was discussed in a recent post by veso266 but I never tried to copy any files as suggested. I am referring to the comments by veso266 as follows: "If you get UnregisterSuspendResumeNotification not found on user32.dll or something along this lines then you probably did not copy it in the right folder" and "copy vmware-vmx located in vmware16.1_win7-21-11-2020.7z into C:\Program Files(x86)\Vmware\Vmware Workstation\x64 folder". After the first two screenshots, I copied both files from the previously cited "vmware16.1_win7-21-11-2020.7z" to the location as suggested and I began to get different errors when a virtual machine is launched. The new errors started by identifying a problem with SSLEAY32.dll, which is part of OpenSSL (if I am not mistaken). I replaced SSLEAY32.dll with a newer version that might be from Windows 10. A different error message was produced the next time I tried to launch a virtual machine, which identified a problem with libcrypto-x64.dll. I tried to locate and supply the missing .dll files one by one, relaunching the virtual machine and noting each new error message which identified a missing .dll file. After a while the messages changed to a more serious error when I supplied the missing libeay32.dll (screenshot not taken). I hope that somebody can provide a better solution than what I have found so far. At this point I changed my strategy, and applied some common sense. After a complete uninstall of WorkstationPro and the manual removal of various .dll files which I had supplied myself, I installed version 15.1.0 and then 16.1 making sure to match the date of the archive file mentioned by veso266 above with the date of the WorkstationPro installer file, so there is an agreement about the date "21-11-2020". Before permitting the installer to initiate a system restart I copied the two files into the target folder as instructed by veso266 above. I felt very grateful when a virtual machine successfully launched, and I sincerely thank the people who have made such extraordinary results possible. Then I noticed that I still had not restarted the system even though I had hastily launched a virtual machine as a test. Let's hope the good results persist after a system restart, lol.
