Messed up installation - How to clean Plantronics Hub COM object registry?

2 posts / 0 new
Log in or register to post comments
Last post
Wed, 06/06/2018 - 06:11
#1
wwall
Messed up installation - How to clean Plantronics Hub COM object registry?
Is there a quick guide for a customer, how he can clean up / repair a Plantronics Hub installation? I just had a support case where our softphone cannot signal incoming calls on a Plantronics headset. We have a .NET application using the Windows SDK + Plantronics Hub. The assembly Interop.Plantronics.dll is rolled out along with our application, the customers additionally have to install the Plantronics Hub. The software could create the Plantronics.COMSessionManager object, receive headset button events etc. But when the software tried to create a Plantronics.COMCall object, it got a System.BadImageFormatException. So it appears, that the session manager object could be created by my x64 process, but the call object could not be created. I could reproduce this on my developer machine as well - but there I had a mix of plantronics hub and sdk installations. After de-installing all Plantronics software, manually cleaning up the registry from all Plantronics COM object references and then a clean install of the Plantronics Hub, it works on my machine without problems. So my question is: Is there a quick guide for a customer, how he can clean up / repair a Plantronics Hub installation? Thanks in advance!
Top
Thu, 06/07/2018 - 00:15
wwall
On Windows 10 x64, the current Plantronics Hub installer writes the COM object entries to HKCR\WOW6432Node:<br /> &nbsp; <blockquote> <p>[HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{F8729099-4E9F-4135-A157-D6CADBECEA88}]<br /> @=&quot;COMCall Class&quot;</p> </blockquote> <p>When the system was faulty, I had as well entries directly below HKCR\CLSID:</p> <blockquote> <p>[HKEY_CLASSES_ROOT\CLSID\{F8729099-4E9F-4135-A157-D6CADBECEA88}]<br /> @=&quot;COMCall Class&quot;</p> </blockquote> <p>This should tell a 64bit process that there is a 64bit COM object. Those entries are not present when I do a clean install of the Plantronics Hub. So I expect that any previous installer wrote those entries that are now wrong. Those entries do no matter as long as my application is running as a 32bit process. But since it is now a 64bit process, it matters. So I expect that I have to write a clean tool for removing the relevant entries below HKCR\CLSID for the Plantronics COM objects.</p> <br /> &nbsp;
Top

Add new comment