Fixing compatibility issues in the Microsoft Lync Server 2013 SDK involves bypassing hardcoded installer requirements and adjusting project properties to accommodate newer operating systems, newer versions of Visual Studio, and the transition to Skype for Business.
Because the SDK is structurally frozen, developers must use specific registry workarounds and compilation fixes to maintain functionality in modern environments. Bypassing Installation Compatibility Blocks
The most common issue occurs when trying to install the Lync 2013 SDK on a machine that uses a newer environment (such as Visual Studio 2015+ or Skype for Business / Office 2016+). The installer checks for legacy dependencies and will halt with an error.
The “Visual Studio 2010 Not Found” Error: The installer throws an error if it does not find Visual Studio 2010 SP1. You can bypass this check by installing the lightweight Microsoft Visual Studio 2010 Shell (Isolated) Redistributable Package to trick the installer dependency engine.
The “Microsoft Lync 2013 Not Found” Error: If the machine runs Skype for Business instead of Lync 2013, the installer blocks execution. There are two methods to bypass this:
Registry Hack: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Lync, create a new string value named InstallationDirectory, and leave the data field blank. Run the installer and then delete the key.
Manual Extraction: Use an archive tool like 7-Zip to extract the contents of lyncsdk.exe. Locate the internal raw .msi file (x64 or x86) and run it directly to install the SDK components without the prerequisite scans. Fixing Code & Compilation Failures
Once the SDK is installed, upgrading the project code or running it alongside modern Office configurations introduces specific runtime and compilation breaks.
“Embed Interop Types” Exception: Developers migrating to newer development environments frequently experience a FileNotFoundException related to the Microsoft.Office.Uc assembly. To fix this, locate Microsoft.Office.Uc under your project references, open its Properties window, and change Embed Interop Types from True to False.
Disabled Server Check: When running code written with the Lync 2013 SDK against older topologies or unique environments, you can experience an “incompatible server version” handshake block. This can be bypassed by opening an elevated Command Prompt and running Abdul Munim’s Registry Tweak:Reg Add “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\15.0\Lync” /V “DisableServerCheck” /D 1 /T REG_DWORD /F Addressing UI Suppression & Video Interoperability
Broken App Sharing (UI Suppression): If your SDK application uses UI suppression to render custom video/audio components, incoming application sharing displays may break (rendering a blank or gray rectangle) due to newer Windows Update graphics overlays. Testing apps outside of strict UI suppression or forcing video rendering to rely on the H.264 SVC video codec via your Edge Server configurations helps mitigate rendering failure. If you are dealing with a specific error code, let me know: What version of Visual Studio are you compiling with? Are you targeting Lync 2013 or Skype for Business? What is the exact error message or crash symptom?
I can provide the exact code block or configuration step needed to fix it. Can’t install Lync 2013 SDK with Skype for Business 2016
Leave a Reply