Lync 2013 / SfB 2015 Client Update – April 2019

It’s April already – Autumn/Fall here in Oz, or Q2 if you’re more the practical type – and have an update to the Office 2013-based Skype for Business client. Our last update was February, and this one (Kb 4462207) takes us from 15.0.5101.1000 to either 15.0.5125.1000 or 15.0.5127.1000, depending on whether you trust the kb or the Help/About version more.

What’s Fixed

This update fixes the following issues:

  • Kb 4495279 Skype for Business stops responding when receiving a toast notification of an IM or an incoming call in Citrix VDI environment.
  • Kb 4495282 Update the country name from “Macedonia, Former Yugoslav Republic of” to “North Macedonia” for Skype for Business 2015 (Lync 2013).

What’s New / Changed

Nothing documented.

Known Issues

Nothing documented.


It’s all good if you’ve been diligent in your patching.

If however your patching isn’t to current you’ll need to check you have *all* of these pre-req’s. The Office 2013 SP1 requirement still applies if you’re using Outlook 2010. (Lync 2013 in all of its flavours – e.g. Lync Basic – is still a component of Office 2013).



Current Version


Update for Office 2013 (KB3054853) (NOTE 1 BELOW) 1.0 9 June 2015
LyncHelpLoc (kb3191937) 1.0 22 May 2017
Microsoft Office 2013 Language Pack Service Pack 1 (KB2817427) 1.0 13 February 2014

NOTE1: “You do not have to apply update KB3054853 if you applied the April 14, 2015, update (KB2889923) or the May 12, 2015, security update (KB3039779) for Lync 2013 (Skype for Business)”


This is the client fix itself:

  • x86 (lync2013-kb4462207-fullfile-x86-glb.exe)
  • x64 (lync2013-kb4462207-fullfile-x64-glb.exe)


I have all the pre-req’s already installed, had exited the client before we started & was not prompted for a reboot.

Before / After



SfB 15.0.5111.1000 MSO 15.0.5101.1000 SfB 15.0.5125.1000 MSO 15.0.5101.1000
Before-kb4462207 After-kb4462207

Revision History

6th April 2019: This is the initial post.

– G.

Leave a Reply

Your email address will not be published.

... and please just confirm for me that you're not a bot first: Time limit is exhausted. Please reload the CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.