“onecore\com\combase\dcomrem\resolver.cxx(2279)\combase.dll!00007FFC728F64D0: (caller: 00007FFC728F3927) ReturnHr(1) tid(35f4) 80040154 Klasse nicht registriert”
Has anyone an idea how to fix this? I am building a VST3 with Juce in Microsoft Visual Studio on a Windows x64 PC.
The Plugin crashes sometimes right after this call.
I am also seeing this in Visual Studio 2019, JUCE 6.0.7. I wish I knew if there was some way to deal with it:
'AudioPluginHost.exe' (Win32): Loaded 'C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.1316_none_9e7a364fe461dbd7\comctl32.dll'.
'AudioPluginHost.exe' (Win32): Loaded 'C:\Windows\System32\WindowsCodecs.dll'.
'AudioPluginHost.exe' (Win32): Loaded 'C:\Windows\System32\thumbcache.dll'.
'AudioPluginHost.exe' (Win32): Loaded 'C:\Windows\System32\policymanager.dll'.
'AudioPluginHost.exe' (Win32): Loaded 'C:\Windows\System32\msvcp110_win.dll'.
onecore\com\combase\dcomrem\resolver.cxx(2279)\combase.dll!00007FFEA2603690: (caller: 00007FFEA2601A8B) ReturnHr(3) tid(74cc) 80040154 Class not registered
onecore\com\combase\dcomrem\resolver.cxx(2483)\combase.dll!00007FFEA2601AB2: (caller: 00007FFEA25A9FB9) ReturnHr(4) tid(74cc) 80040154 Class not registered
I fixxed my bug, which was not related to the Combase.dll print out.
The print out (Combase.dll class not registered) is still there and everythings running fine! Maybe you do not have deal with it…
Yeah, but it would be nice not to see it… it always makes me think that the JUCE guys missed something. Because this prints out in the AudioPluginHost before I even load my plugin.
If you Google this, lots of non-Juce and non-C++ developers are also seeing this message. No need to point to Juce 
Funnily I landed here by google, was the second hit after SO.
I see this message from running Projucer.
But I agree, it’s probably benign and best to be ignored.
I’ve always ignored it, but it annoys me that when I clean up, debug the code, and remove warnings, this bullshit keeps popping up over and over again.
Any solution? Can’t it be hidden in some way?
Hey, I’m facing a similar error right now. Could you tell me how you resolved it?
I fixxed a bug, which was not related to the combase.dll print out. As mentioned earlier, it seems to be ok to ignore the print out. I still have the combase.dll print out, but it is not causing problems.
