I hit the same certificate issue trying to update from the player app. I then visited Download VMware Workstation Player | VMware and selected the "download now" option which took me to download3.vmware.com | 522: Connection timed out that is exhibiting a cloudflare distribution point timeout.
Given that where are you suggesting one goes to successfully download the vmware player 17.5.2 new installer / existing install updater?
I found another "vmware player 17.5.2 download error fix" search hit that suggested using softwareudpate.vmware.com/cds/ | vmw-desktop | player | <desired version, e.g. 17.5.2> | <latest build number, e.g. 23775571> | windows/core | <tar file, e.g. VMware-player-17.5.2-23775571.exe.tar>. Is that recommended work around?
Original Message:
Sent: Jun 12, 2024 09:30 AM
From: RDPetruska
Subject: Update of 17.x versions to 17.5.2 via Software update function
Do yourself a HUGE favor and just download the installer file yourself, and run it. There have ALWAYS been issues running the update from within Workstation since the beginning... and it merely does the same thing (there is no "patch/update" installer - only the full product installer).
Original Message:
Sent: Jun 11, 2024 08:15 AM
From: Jan Pancuha
Subject: Update of 17.x versions to 17.5.2 via Software update function
hey there, firts i thought that to manage the latest vulnerabilities in Workstation PRO and PLAYER would be easy as the software has software update function, but I was wrong and will most probably need to rollout the 17.5.2 over the existing version (which is not good).
The reason is following. I tested it on several computers (Windows 10 and 11), different networks and even two home computers. Same result - app says:
ERROR: A certificate error occurred while connecting to the update server. Check your internet settings or blah, blah...
It is apparently connecting to some old vmware server (//softwareupdate.vmware.com/cds with no proxy server
Any ideas how to solve this issue? Tried it from 17.0 and 17.5.1 with same result. AS mentioned above, I would prefer to update it this way, not placing a 17.5.2 file over it again
------------------------------
cheers
Jan.P
------------------------------