Arezco

Cleaner 1112 does seem to prevent this issue from happening, by the way. However, It didn't fix it for me once the damage had already been done.

The update did not fix the issue for me (or I didn't wait long enough), but changing the mentioned registry value did seem to do the trick. BUT I had to change the value from both HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\ and HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\ Changing from Wow6432Node alone was not engouh. As Marcos mentioned, both registry keys are owned by SYSTEM and neither regular users nor admins can edit them by default. I first had to change the ownership of the keys, then edit permissions to allow modifications, change the values, and finally change the ownership back to SYSTEM. So try this at your own risk...