Figured it out. Chrome introduced its own root certificate store in v105. So you can disable this via GPO/policy to use Windows root store to which the VMware Plugin automatically adds its certificate.
Computer Configuration / Policies / Administrative Templates / Google / Google Chrome / Determines whether the Chrome Root Store and built-in certificate verifier will be used to verify server certificates = Set to "Disabled"
It seems to be related to the fact Chrome does not automatically accept the plugins self signed certificate @ https://vmware-plugin:8094. Where Firefox does.
Every VM with the plugin installed has its own. So cannot import into the certificate store.
This chrome flag could of worked. But VMware adds vmware-plugin dns record into the host file. So Chrome does not ack that its a localhost/127.0.0.1 request for the flag to permit use.
Figured it out. Chrome introduced its own root certificate store in v105. So you can disable this via GPO/policy to use Windows root store to which the VMware Plugin automatically adds its certificate.
Computer Configuration / Policies / Administrative Templates / Google / Google Chrome / Determines whether the Chrome Root Store and built-in certificate verifier will be used to verify server certificates = Set to "Disabled"
I found a easier solution that doesn't require disabled Chrome's certificate store. Simply add the address of "https://vmware-plugin:8094/" to the allowed sites to show insecure content. You can get there from settings > Privacy and Security > Site Settings > Additional Content Settings > Insecure Content.
