Registry keys not purged from dopus64 ver 9

ActiveX/COM Issue LocalServer32"C:\Program Files\GPSoftware\Directory Opus\dopusx64.exe" HKCR\CLSID{1D361D1A-C9B7-49F4-9A50-4C2B691F7C3A}
ActiveX/COM Issue LocalServer32"C:\Program Files\GPSoftware\Directory Opus\dopusx64.exe" HKCR\CLSID{579DD804-98B0-450C-AE21-6D5928D9DA13}
ActiveX/COM Issue LocalServer32"C:\Program Files\GPSoftware\Directory Opus\dopusx64.exe" HKCR\CLSID{591E8F2A-FFAB-4BC9-8152-4FD18425AA7E}
ActiveX/COM Issue LocalServer32"C:\Program Files\GPSoftware\Directory Opus\dopusx64.exe" HKCR\CLSID{C37C87AC-0080-4D51-8060-7568B0C6D73A}
ActiveX/COM Issue LocalServer32"C:\Program Files\GPSoftware\Directory Opus\dopusx64.exe" HKCR\CLSID{EC6BB2F5-1ACA-437C-96AD-A50658CDC89F}

The above registry keys turned up by CCleaner after upgrading to Dopus 10 after deleting the dopus64.exe

From what you said in another thread, dopusx64.exe doesn't seem to have been uninstalled at all on your system. I'm not sure why and haven't seen it happen myself.

If you regularly use CCleaner and similar, something in the registry may have been "cleaned" incorrectly and that thing may have been what the Opus 10 installer uses to detect whether or not it needs to uninstall dopusx64.exe from an Opus 9 installation. Registry cleaners do more harm than good.

Feel free to delete the registry values. Nothing will use them, either way as nothing in Opus 10 uses dopusx64.exe and nothing outside of Opus knows it exists.

This may seem like a truly simple minded approach – that's me all over – but one way in which I have deleted this sort of garbage in the past is to reinstall and remove the software that created the settings in the first place, rebooting at every possible opportunity.

Of course, this may also mean removing Opus 10 before you go down this path, saving settings before you do it, but some people prefer that to messing around in the registry.