My skype for business(office 365) is crashing and hanging after some calls .

Can anyone else confirm this reg key resolved the crashing. I am in a similar situation with about 100 users. We use SfB Server 2015 with a call center solution called Clarity Connect.

Our SfB cleints are the same version of 16.0.16626.20134. They also have Teams installed but in a different mode.

Seeing TONS of crashes and hoping this will fix.

Registry key fix does seem to be working. Tested for 2 hours last night without any crashes. Deployed to all workstations overnight and haven't had any reports of crashes so far this morning (just over 2 hours).

Edit: Took longer this time, but the crashes did start again after a few hours.

Even with the above registry change and a reboot, closing out Microsoft Word still crashes Skype on the latest version of Office, 16.0.16626.20086 . Registry entry doesn't seem to solve the issue so far at least for me. The leftover winword.exe left in the background has to be task-killed from Task Manager, otherwise Outlook will get hung up on "Loading Profile" when trying to open Outlook.
Can roll back to 16.0.16529.20182 and the issue is 'fixed', however the issue will come back when Office updates again.

BenLaRoche-0186 we have same problem

This seems to have been solved in client version "27/1.0.0.2023080109"

(you can see the Teams client revision by right clicking the Teams icon in the System Tray and selecting "Collect support files". Save to a folder, and look for "clientVersion": "27/1.0.0.xxxxxxx" in the

"MSTeams Diagnostics Log (date)_PM.txt" file

I tried the regedit and it did not work. Same issue happening. Added DWORD (64) of EnableARIATelemetryFeature = 0 and issue continues to occur.

Hi everyone, I as mentioned previously the reg change did not work for us either. I ended up opening a case with MS and are currently collecting procdump logs for them to monitor. I have referenced this thread and the issue TM663429. Similar to others our users are saying this started in mid-July.

I will ask our support engineer about the client version 27/1.0.0.2023080109 as @donlassini mentioned.

We have tried the following so far:

adding reg keys

Exiting Teams and just running SfB

Turning off logging in SfB client and clearing profile cache folders

Currently collecting procdump logs

From Microsoft:
"Also we got the information from our Product Teams that the issue was already addressed globally in the build 1.0.0.2023080109 and this is what's being delivery next to our customers in General ring. However, please note that users who got the mitigation have this build 1.0.0.2023071203, which is also good. "

You could probably download and install one of these specific versions using the ODT (remember disabling updates); however I would only do that on a very few machines unless I had the infrastructure to mass deploy.

This is definitely a headache. I am in a similar boat as @igibason . We have S4B 2015 as well. Hopefully we can move to an updated Teams version. We are 1.6.00.18681 here.

Used GPOs to change the Update Channel to Monthly Enterprise Channel. After policies are applied and updates are run Office Apps should roll back to Version 2305. Seems to have solved the crashing issue for now

@donlassini you stated "This seems to have been solved in client version "27/1.0.0.2023080109"

I am still seeing SfB crashes on my clients. Are your users using the SfB client, if so what version is the SfB cleint running?

Same problem. This has been going on for a month now and I was hoping this Patch Tuesday would offer a fix.

A new update was released by Microsoft (new build) overnight. Previously it was Build 16626.20134. After the update, I am showing Build 16626.20170. However, the issue still occurs with Skype crashing following closing Excel, Word, PowerPoint, or Access.

I have been closing Teams and SfB, clearing cache, then Checking for Updates in Teams.

I then see build 1.6.00.20074 on my clients. Most of them say its working a lot better but still have others who's SfB clients are crashing.

Been sending ProcDump logs a MS case I have opened.

I will keep an eye out for that 16626.20170 build in Office.

Here's how I got it to quickly switch over to the Semi Annual enterprise channel

Set the Group Policy to the Semi Annual like the instructions in say in https://video2.skills-academy.com/en-us/deployoffice/updates/overview-update-channels

To force it over faster, I run these commands on workstations, which will make Office close and then reopen the applications but be in Semi Annual mode in about 10 minutes. Usually have some delay between the commands. Obviously there's a lot of ways to change the channel, these are just what I did to prevent actually having to reinstall Office, and get it to go fast. Results may vary.

#Change the settings to SemiAnnual via click to run
"C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /changesetting Channel=SemiAnnual

"C:\Program Files (x86)\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /changesetting Channel=SemiAnnual

#Have click to run double check and 'realize' the channel changed (checks the Group Policy setting)

schtasks.exe /Run /TN "\Microsoft\Office\Office Automatic Updates 2.0"

#Try to make sure the Office Click to run actually starts updating it and will close and reopen office forcibly.

powershell.exe -C "$result = Start-Process -FilePath 'C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe' -ArgumentList "/update user displaylevel=false forceappshutdown=true" -PassThru -Wait;$result"

powershell.exe -C "$result = Start-Process -FilePath 'C:\Program Files {x86)\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe' -ArgumentList "/update user displaylevel=false forceappshutdown=true" -PassThru -Wait;$result"

#double check version a while later after it updates

powershell.exe -C "Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object -ExpandProperty VersionToReport"

Can confirm there are two separate issues. The first one - SfB randomly crashing and restarting - is fixed by making sure everything is up-to-date for Office 365 / SfB and Teams. However, users still experience problems with SfB crashing when closing Excel, Outlook and Word.

if you want to apply office 365 semi annual just create registry edit group policy

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate

create New string value name updatebranch value data Deferred

please test one pc locally and check the version

office 365 semi annual enterprise channel working fine we dont face SFB CRASHING ISSUE UNTILL NOW

Seeing the same here...in fact I even rolled someone back to current channel and they started crashing right away!

If we keep them on semi annual won't they eventually get the update that caused this? I was told they already pushed out an update that fixed it. But clearly Skype is still crashing.

How's everyone doing? My Teams at least as stopped with the ridiculous log files it seems. I haven't noticed much with my Skype. My current version of teams is 1.6.00.20074(64 bit)

Now this morning the clients I put on Semi-Annual are back to Current Channel and are having issues answering Skype for Business calls. I checked our Group Policy and we are not forcing any changes.

I also notice when I do attempt to flip them back to Semi-Annual the Office App will pop up stating the latest updates are already installed and won't change anything.

Is anyone else still having skype client crashing issues?

can you please tell me how you upgrading from semi to current or current to semi channel via Msi or policy?

Seems like a GPO is the way to go. But I have been doing it via cmd prompt so I don't have to wait for the policy.

CMD as admin

cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun

OfficeC2RClient.exe /changesetting Channel="SemiAnnual"

OR

OfficeC2RClient.exe /changesetting Channel="Monthly"

OfficeC2RClient.exe /update user

After the update cmd the Office installer should pop up and start applying the update. However recently I have had clients revert back to the CurrentChannel after doing this and now I cannot get them to SemiAnnual or Monthly. The Office pop up states lastest updates are already applied.

So today I may roll out a GPO. This is getting really rough for us as our users are having a hard time answering calls via Skype.

1,this policy users can control whether the updatechannel option is show under file>account.this option allows users to select which update channel they want to receive updates from also you need to select which update channels will be shown as options to the user

2,this policy users cannot select the channel its totally controlled office updates by office administrator

as per this attached group policy image you can controll your office 365 updates