Crash on Splash screen after Win10 upgrade

Problem: After Win10 upgrade, Skype for Business (Lync) crashes at the splash screen upon launch. The dialogue that follows allows you to see debug information, but it scrolls by quickly in a disappearing DOS window, so I cannot read it. I accidentally discovered, however, that if it is launched from an administrator's shell that it does launch without crashing. It would seem to be some kind of permissions problem introduced by the upgrade.

I have attempted both the quick repair and the online repair, with no joy. I have not tried the Microsoft Fixit to completely remove office because the rest of office is working fine and I don't have all day to uninstall/reinstall things, and I've done that about a dozen times with this Win10 upgrade anyway to no avail. 

Is there a way to specifically just fix Lync without all the associated baggage of reinstalling all of Office 365 Pro?

August 6th, 2015 10:14am

Hi, hope this http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_desktop/lync-2013-keeps-crashing-on-windows-10-technical/4b1fce9a-c5de-4a34-bb78-64db626b9f66?auth=1 can help you. The issue is regarding drivers in the machine.

Regards.

Free Windows Admin Tool Kit Click here and download it now
August 6th, 2015 12:32pm

So I have the latest/greatest drivers for the Nvidia card on my machine, and because Win10 included some significant updates to DirectX I can't rollback the drivers as was suggested because the whole machine would become unusable. I'm using the video drivers updated for Win10, the last version was for Win8.1 and is incompatible with Win10.

I'm not sure this is a drivers problem as much as a permissions problem. It works just fine if I launch it as an administrator and crashes when I don't. That doesn't sound like a driver problem.

August 6th, 2015 12:39pm

In this case, you can address this issue doing both or one of the both actions in the Skype for Business 2015 file location: In my case is in the path: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office 2013.

1.- Run this program in compatibility mode for: Windows 8.

2.- Run this program as an administrator.

Free Windows Admin Tool Kit Click here and download it now
August 6th, 2015 12:55pm

Thanks, I'll try that next.

I'm finding one of the reasons I can't see a crash dump is that Verizon integrated messaging has unhelpfully overridden the entire windows default debugger and several other system defaults. It may be one of the culprits in this equation. I've never heard of a company's phone company stack overwriting system debugging functions for the entire box, its almost like it was shipped directly off the developer's desktop and out to production.

August 6th, 2015 1:35pm

Okay, that did not help. However, getting the latest Win10 cumulative patch rollup update and then removing and reinstalling my camera drivers did resolve the problems.

As an aside, since I've now discovered that Verizon has unhelpfully replaced the system crash debugger with their own, does anybody know a convenient way to roll that back to the system default? I am kinda miffed that I couldn't get debugging output to at least see what was going on because they decided to replace the system crash debugger for not just their application, but all applications on the system.

Free Windows Admin Tool Kit Click here and download it now
August 8th, 2015 10:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics