Hi @Nikolay Yordanov ,
Thanks for reaching out to Microsoft Q&A.
The "Class not registered (0x80040154 REGDB_E_CLASSNOTREG)" error occurs when a required COM component is missing or not registered on the target machine. This often happens due to mismatches between development and deployment environments, such as a platform target mismatch where a 32-bit COM component is loaded in a 64-bit application or vice versa. To fix this, ensure the application's platform target matches the architecture of the COM components. Another cause is missing COM component registration, which can be resolved by running regsvr32.exe path\to\your\component.dll
in an elevated command prompt. Insufficient permissions can also prevent access to the COM component, so try running the application with administrative privileges or adjusting the manifest. Missing dependencies can be identified and resolved using tools like Dependency Walker. To prevent this error, ensure all necessary COM components are registered, the application and COM components have matching architectures, and no dependencies are missing. These steps should help resolve the error and ensure smooth deployment across different Windows environments. environments.
stackoverflow.com
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Please let us know if you need further assistance.
What are the prerequisites for using Azure.Communication.Calling.WindowsClient
Nikolay Yordanov
0
Reputation points
The code works fine on my dev machine (Windows 11).
But when deployed on Windows Server 2016 or Windows 10 I get the following exception:
Getting error on the line instantiating
CallClient:var callClient = new CallClient();
1 answer
Sort by: Most helpful
-
Shree Hima Bindu Maganti 3,600 Reputation points Microsoft External Staff
2025-03-07T08:41:58.6266667+00:00