Question
People commonly ask on the Zoom Developer Forum:
When using the Windows C++ Meeting SDK alongside a gRPC dependency (which brings in its own cares.dll via vcpkg), I get a pop-up: “sdk.dll is using cares.dll from an unknown publisher. Are you sure you want to run this software?” Disabling 3rd-party module verification via the registry didn’t help. How can I get rid of this popup?
Answer
This warning appears because the SDK is loading a different cares.dll than the one bundled and signed by Zoom, triggering the SDK’s verification dialog. The fix is to ensure the SDK uses Zoom’s signed cares.dll, not the one brought in by your toolchain (e.g., vcpkg).
Steps to resolve:
-
Prevent conflicting cares.dll from being in the app’s runtime directory - Stop your build/post-build steps (e.g., vcpkg) from copying its cares.dll into your bin/output folder. - Engineering guidance: avoid placing the SDK DLLs in the same path as other third-party DLLs used by your app to reduce collisions.
-
Ensure Zoom’s signed cares.dll is first in the DLL search path - Use the cares.dll that ships with the SDK (e.g., zoom-sdk-windows-5.14.5.15340/arm64/bin/cares.dll, signed by Zoom.us). - Place SDK binaries in a directory that is searched before any directory containing third-party cares.dll versions.
-
As a temporary workaround - After each build, replace the third-party cares.dll in your bin folder with the Zoom-signed cares.dll from a fresh SDK download.
-
Optional: Explicitly control module loading - You can attempt to load the intended module via LoadLibrary before SDK init to influence resolution, though this may not apply to cares.dll in all cases.
Zoom Developer Forum Examples
Some examples of this question are:
