Lync 2013 Client Update to Skype for Business – April 2015

IT’S HERE! Today marks the release of the new Skype for Business Client update to Windows Update. Much has been written in anticipation of this of late and there are plenty of references I’ve captured below.

Until Office 2016 is released, THIS is your client-side update path to Skype for Business: Install Lync 2013 from Office 2013 and then patch it with this (or a later) update & the necessary pre-req’s. You will also use this patch to turn your “Lync Basic” client into a “Skype for Business Basic”. (Read more of the free Basic client here).

If you want to manage the rollout of this internally via SCCM or WSUS, the two KBs you’re interested in are these:

What’s fixed in this update?

There are no fixes here as applying this patch is installing a brand new client. Whilst you might start with a patched Lync 2013 Client, it’s replaced with the brand new Skype for Business client.

What’s new?

Skype for Business! Key points to look out for include:

  • all NEW sounds !!!!!
  • new tray icon
  • the Title Bar now shows the new name
  • the “new meeting” button in the Outlook calendar’s toolbar has changed:
  • the “join meeting” link in your Outlook meetings has changed to “Join Skype Meeting”:

Note: these apply regardless of whether you’re running the client with the Lync 2013 skin or the Skype for Business skin.
Updated April 16th: : When running with the Lync UI (‘skin’), I’m seeing the title, tray and task-bar icons remain the familiar Lync ones.

Known Issues

Just a couple:

  • KB 3051158 “Help isn’t working” error occurs when you open the “Skype for Business Help” window in Skype for Business
  • KB 3051516 “Copy” and “Select All’ menu items are disabled for the first instant message in a conversation in Skype for Business
  • KB 3051517 Receiver cannot open or save transferred files in a chat room in Skype for Business
  • KB 3053114 Cannot open links without the “http://” prefix and the links that are to an OneNote page in Skype for Business
  • KB 3051160 Cannot join meetings by using Lync 2010 after you install OneDrive for Business
  • KB 3053998 Memory leak occurs when you transfer a file that is larger than 5 megabytes (MB) in a conversation in Skype for Business
  • KB 3054008 CPU usage increases largely when you have multiple animated emoticons in conversations in Skype for Business




Current Version


Office 2013 SP1 (KB2817430) 1.0 18 February 2014
LyncHelpLoc (kb2889853) 1.0 13 March 2015
LyncLoc (kb2863908) 1.0 7 March 2014



Don’t forget the pre-req’s as well. Even if your client is patched to current now, the LyncHelpLoc pre-req has also been updated.


Alas, yes! And after you do, a “first run” help box will pop:


Reader Viz had kindly pointed out in the comments below that a new key is added for this – it’s not just reusing Lync’s old “FirstRun” key:

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync] “IsBasicTutorialSeenByUser”=dword:00000001

To suppress the display, create this key and set it to 1 before you let the update run.

Before & After

Here’s a before and after comparison of the x64 client on my Windows 8.1 machine. I was previously running the Technical Preview Client, so the title bar was already “About Skype for Business”.



SfB15.0.4707.1000 MSO 15.0.4707.1000 SfB15.0.4711.1002 MSO 15.0.4711.1000
Before-4707-1000 After-4711-1002

So the new version number is “4711”? That won’t be hard to remember – that’s my smother-in-law’s favourite perfume!



<More to come!>


– G.


  1. After some playing around I managed to find the reg key:



    Set to 0 to view the tutorial on startup.

  2. Hi Mattias,

    That’s strange, as I tested this on a Windows 8.0 machine with no Office and Lync Basic today.

    Windows update added kb2889853 and appeared to make no obvious difference to the way Lync looked on-screen (other than the change to the “MSO” value in Help/About). I then manually d/l and installed kb2889923 and it went in OK – and we’re now in the expected Skype for Business experience.

    The end result – regardless of the skin set by EnableSkypeUI – is that the title bar’s dropped “Basic” from the name. It now self-reports as either “Microsoft Lync (Lync)” or “Skype for Business” – but it’s still operating as the Basic version. You can tell that easily by going to the Call Forwarding settings and seeing that the only option you have – one solitary radio button – is to “turn off call forwarding”.

    Methinks some of this might be further refined in upcoming updates…

    – Greig.

  3. We pushed both kb2889923 and kb2889853 with WSUS to about 300 Machines and kb2889853 installed fine on all of them.
    kb2889923 was installed without problems on all machenes running Lync(about 10 of 300) the rest still got the unpatched Lync Basic client.

    I got the same result when I try to patch a machine manually.

    We are running Windows 7 x64, office 2010 and Lync Basic x86 all on swedish versions

  4. Same here, I’m getting the “The expected version of the product was not found on the system” this is somehow strange, as I’ve installed the Lync client (at this customer) for the first time Tuesday and by this morning it was automatically updated to Skype For Business Basic… Somewhat unfortunatly, now I have to go back to the client PC’s to explain it twice to the end-users ;-)

  5. I have a similar issue to Mattias in so much as kb2889923 is showing up as ‘Not Applicatble’ in WSUS for all machines in my University running Win7 x86 + Office 2010 and Lync 2013. We originally deployed Lync 2010 (msi via GPO) and then when Lync 2013 was released we deployed that (again using msi vis GPO) whilst at the same time removing Lync 2010. I seem to recall reading an article recently that explained this is expected when using the msi to deploy Lync but for the life of me I cannot find the blog post!! Take my personal work PC, if I run a report within WSUS the KB shows up as Not applicable but I can’t find out why this is the case. I had a look in windowsupdate.log but nothing stands out.

    Is anyone else experiencing something similar?

    • Check you have the pre-req’s.

      It sounds counter-intuitive, but run Office 2013 SP1 and then re-try the Skype for Business update. Whilst the REST of your Office suite is still 2010, Lync 2013 is part of Office 2013, and it needs whatever’s in the Office SP1 for it as a precursor to the SfB update.

      – G.

      • Office 2013 Sp1 was the missing part for me. After installation of Sp1 for 2013 WSUS updated the client to Sfb.

        But it seems like the Basic client is not ready for Sfb. This is a list of things that I found so far:
        Most labels and text still says Lync instead of Sfb.
        The plugin for Outlook is not updated
        The settings only contains a few alternativs, most of the alternatives are missing.
        There are several graphic errors in menus, for example help menu and the present tab(you cant se what you are going to present).

        I get the same problems on all PC I tested on.
        Can anyone else confirm the the same problems with Sfb basic?

        • Hi Mattias,

          My patched-up Lync Basic client is looking as expected here. The only obvious difference is that it no longer says ‘Basic’ in the title bar. What settings are missing for you, and are they missing in both modes (LyncUI/SkypeUI)?

          Is there any chance it’s specific to the translations? Are you running it in en-US or sv-SE?

          – G.

          • Hi Greig!
            There is no Basic in the title bar in my client in SkypeUI. In LyncUI there is no text in the title bar at all.
            The graphic errors only appear in SkypeUI. If I look at the fly-out menue for help there should be three choices, In SkypeUI I only se one of them(I can choose the other two but I dont see the text).
            Hard to explain without Pictures…

            I´m also think this could be related to the translation and hopefully corrected in the next upgrade.

  6. Office 2013 SP1 is prereq for S4B update otherwise you will get error “The expected version of the product was not found on the system”.

    [4/14/2015] NOTICE: Support for Microsoft Office 2013 RTM has ended. Starting with the April 2015 release, all Office 2013 updates will only apply if Office 2013 SP1 is installed. See KB2817430 for more information about acquiring Office 2013 SP1.

  7. Good Information !
    We recently upgraded to Office 2013 and now using Lync2013 client (server is still 2010). We are running into this strange issue where during the lync meeting , Lync crashes for few users. What happens is , when the user 1 stop presenting her desktop and user 2 start sharing her desktop, lync crashes for few users and have to re-login. It doesn’t crash for the presenter , but crashes for a few attendees. Usually we have around 20 attendees in the meeting and it happens everytime when user 2 start sharing the desktop during the meeting.
    Error in event viewer shows faulting module path: c:\windows\syswow64\msvcrt.dll
    Any help is appreciated.

  8. We have Windows 8.1 with Office 2013 Std x86 and Lync 2013. It seems we cannot update to version 15.0.4927 and I don’t know why. I tried several updates and none of them are solving our issue. Our Office 2013 Std was already delivered with SP1 so proplussp2013-kb2817430-fullfile-x86-en-us.exe wasn’t necessary anymore but I tried to be sure.
    These are the ones we tried:
    We also have users with Windows 7 / Office 2010 / Lync 2013 and after applying Office 2013 SP1 it worked. So Office 2010 works but not Office 2013


    • Have you tried a Repair of Office?

      When you say you can’t update, what is the error you’re receiving? What patch version are the clients running today?

      If a Repair doesn’t bring results, I’d be inclined to give a test machine *several* runs past Windows Update, then look for the pre-req’s for the next patch update following the version they’re running. Failing that, look at uninstalling the most recent Office/Lync updates and reapplying them.

      Good luck with it. Please let me know how you go with it….

      – G.

Leave a Reply to Mattias Cancel reply

Your email address will not be published. Required fields are marked *

... 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.