Just to hopefully save someone else some pain and agony if they run into this like we did as well. Here is what we did to fix it.
4 years later, different person, same issue. This was the fix.
https://kb.vmware.com/s/article/2150066
Go to the designated spot in the registry, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc
And change the permissions for the main folder (instructions at the link above), you’re basically adding admin, creator owner, etc to the permissions on the main vmware inc folder.
We had to change the owner for the "Vmware, Inc" folder in order to add/change permissions for the folders below. After doing that, we were able to run sviconfig without issue to replace the currently bound cert to the View Composer service.
