![]() 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. How can this be submitted to the Office team? I believe this is a bug in the Lync installer and six patches described above.Īfter we delete the "2.b" registry key, the application works fine. 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. Microsoft Lync 2013 is the new instant messaging and. The new version is designed for the Windows platform and includes Outlook, Word, Excel, Access, PowerPoint, OneNote, Publisher and Lync. KB2986246 : May 12, 2015, update for Project 2013 (KB2986246) Microsoft Office 2013 is the new productivity suite for creating and editing documents, email spreadsheets, presenting material, etc.KB3039779 : MS15-044: Description of the security update for Lync 2013 (Skype for Business):.I discovered the following the patches also add the "2.b" key on PCs with Lync 2013 and Office 2010 installed: "PrimaryInteropAssemblyName"=", Version=14.0.0.0, Culture=neutral, PowerPoint 14.0 Object Files (x86)\\Microsoft seems that the Lync 2013 installer is erroneously adding the "2.b" key assuming that PowerPoint 2013 is installed. We found that the following registry key: ![]() We've have discovered that when running Office 2010 (32-bit) with Lync 2013 (32-bit) that VBA code will give the error:
0 Comments
Leave a Reply. |