I found this corrected my issue with registering the provider.
Microsoft released patch 931125 in December. This patch was only meant for clients, not servers. Apparently it was still released to servers. It installs 330 root trust certificates. This ends up filling up the certificate memory on the server (16K). When the VASA provider authenticates against the server, the list of certs is truncated and it doesn't receive the certificate that it is expecting.
The fix is to delete the certificate registry key in Windows and then re-register the VASA certificate. Once done, the VASA provider snapped right in. I was able to pull the volume statistics when looking at a VM or a host, etc. I backed up the Certificate registry key.
I have included the Microsoft link for your reference.
