Lync 2013 (and patches) with Office 2010 causing Run-time error -2147319779 (8002801d)

We've have discovered that when running Office 2010 (32-bit) with Lync 2013 (32-bit) that VBA code will give the error:

Run-time error -2147319779 (8002801d):

Automation Error

Library not registered.

when code is used to control PowerPoint.

We found that the following registry key:

  "PrimaryInteropAssemblyName"="Microsoft.Office.Interop.PowerPoint, Version=, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"

is created by the Lync 2013 installer (and some subsequent patches). But PowerPoint v15 (i.e. PowerPoint 2013) does not exist on the PCs, only PowerPoint 2010 is installed. (Other registry keys may be created that affect other components, but we've been concerned only with PowerPoint).

The Office v14 (i.e. Office 2010) equivalent registry keys have much more information:

  "PrimaryInteropAssemblyName"="Microsoft.Office.Interop.PowerPoint, Version=, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
  @="Microsoft PowerPoint 14.0 Object Library"
  @="C:\\Program Files (x86)\\Microsoft Office\\Office14\\MSPPT.OLB"

It seems that the Lync 2013 installer is erroneously adding the "2.b" key assuming that PowerPoint 2013 is installed. I discovered the following the patches also add the "2.b" key on PCs with Lync 2013 and Office 2010 installed:

  • KB3039779 : MS15-044: Description of the security update for Lync 2013 (Skype for Business): May 12, 2015 - [3039779]
  • KB2986244 : May 12, 2015, update for OneDrive for Business (KB2986244)
  • KB2986246 : May 12, 2015, update for Project 2013 (KB2986246)
  • KB2880487 : April 14, 2015 update for Office 2013 (KB2880487)
  • KB2965277 : May 12, 2015, update for Office 2013 (KB2965277)
  • KB2975901 : May 12, 2015, update for OneNote 2013 (KB2975901)

However about 16 or so other Office 2013 patches that get applied to these Office 2010 with Lync 2013 PCs do not add the "2.b" registry key e.g.  KB3039799 - Update for Outlook 2013 & KB2975808 - Update for Microsoft 2013.

I believe this is a bug in the Lync installer and six patches described above.

After we delete the "2.b" registry key, the application works fine. How can this be submitted to the Office team?

We haven't yet done full regression testing for the Office 2013 suite, so we're at risk of breaking other legacy applications if we the upgrade PCs now to Office 2013.

Ian Broadbent

Hello Ian,


Welcome to Microsoft Community.


As this is an issue with Lync 2013 your issue will be better addressed in the TechNet forum. Click on the link below to post your issue in TechNet forum.


The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly. They can either share their knowledge or learn from your interaction with us.


Thank you for your understanding.


Thank you.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated August 27, 2019 Views 415 Applies to: