Forum Discussion
"Issue occurred while checking for updates." new Teams cannot update...
Currently running the new Teams client version 23247.1112.2396.409 in a corporate environment with CIS benchmarks configured via GPO, SSL packet inspection and content filtering, etc... So, lots of opportunity for our security posture to create interference with normal operation of new software, which I suspect is the case here. When visiting the About Teams page, Teams attempts to update to the current version but fails with the message "Issue occurred while checking for updates."
An MSTeamsUpdate_xxx.log at AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs is generated with each attempt. The logs will contain the following:
2023-10-06T17:07:19-05:00 0x00006e64 DeploymentProviderMSIX: Start staging update package from:https://statics.teams.microsoft.com/production-windows-x64/23257.2616.2423.5046/MSTeams-x64.msix
2023-10-06T17:07:19-05:00 0x00006e64 <ERROR> Scenario: shell_msix_update [stop,failure] CurrentVersion:23247.1112.2396.409, DeviceInfo_OfficeMachineId:afbdc3bb-f071-3944-8851-874a99c45bef, ErrorText:The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
, ExtendedErrorCode:0x80070422
, GenericErrorCode:0x80073cf9
, InstanceId:e6f747b3-e518-4a98-8020-b6524457d0e0, LatestVersion:23257.2616.2423.5046, Scenario.Mode:3, Scenario.Name:shell_msix_update, Scenario.Status:failure, Scenario.Step:stop, Scenario.Steps:[{"Scenario.Status":"failure","Scenario.Step":"stop","delta":68,"elapsed":159,"elapsedSinceProcessStart":382,"previousStep":"start","sequence":1,"stepDelta":68}], Scenario.StepsEx:[{"CurrentVersion":"23247.1112.2396.409","DeviceInfo_OfficeMachineId":"afbdc3bb-f071-3944-8851-874a99c45bef","ErrorText":"The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.\r\n","ExtendedErrorCode":"0x80070422\n","GenericErrorCode":"0x80073cf9\n","LatestVersion":"23257.2616.2423.5046","UpdateCheckReason":"MainAppUpdateCheck","UpdateFailureCount":17,"UpdateUrl":"https://statics.teams.microsoft.com/production-windows-x64/23257.2616.2423.5046/MSTeams-x64.msix"}], UpdateCheckReason:MainAppUpdateCheck, UpdateFailureCount:17, UpdateUrl:https://statics.teams.microsoft.com/production-windows-x64/23257.2616.2423.5046/MSTeams-x64.msix, delta:68, elapsed:159, elapsedSinceProcessStart:382, previousStep:start, sequence:1, stepDelta:68
2023-10-06T17:07:19-05:00 0x00006e64 UpdateStateStoreWinRTAppData: previous app session:49e8598f-b1cf-4cf5-9020-603eea11df8d current app session:49e8598f-b1cf-4cf5-9020-603eea11df8d target version:23257.2616.2423.5046
2023-10-06T17:07:19-05:00 0x00006e64 UpdateStateStoreWinRTAppData: Storing update attempt for app session:49e8598f-b1cf-4cf5-9020-603eea11df8d,target version:23257.2616.2423.5046
Can anyone provide any insight into what may be happening here?
Thank you.
18 Replies
ardamis UPDATE from our end:
Finally found in our environment what was causing the failure to update, or even launch after a day or two after a clean install.Short story: we had a setting in one of our GPO's that set security permissions for the "C:\Program Files" directory. Part of that setting was set to "Replace" existing settings, instead of the "Propagate" option. Which means that any system added permissions will be wiped out during the next GPUpdate cycle.
What to look for:
Immediately after installing New Teams, and while it is working normally, check the properties of the App directory. Located at "C:\Program Files\WindowsApps\MSTeams_24004.1309.2689.2246_x64__8wekyb3d8bbwe". Your version may be different, but the path should be the same. Go to the Security tab, and look for the APP Service account: "S-1-15-3-1327587233-2730283621-3908338074-337181141-3891108920-2047653661-4124462636".
That is unique to the MSTeams App, and should be identical across all workstations.
If New Teams quits working, and that account is missing from the security tab, you have something in your environment setting directory permissions to one of the higher level directories. In our case it was a GPO Replacing permissions to the "C:\Program Files" directory. We changed the rule to "Propagate". Now, New Teams, and all other Apps installed within that directory, are working as designed.
Seriously, I hope this helps. It was one of the longer investigations I have had to do in a while.
Best of luck.
ericappelboom Thanks! issue is resolved after changing delivery optimization registry value to 0.
However, i can see the version updated to Early Access (R3.6 or EA) build of Microsoft Teams.
Is there any way to control this?
bing_gaoMicrosoft
ardamis Please check id delivery optimization is disabled. The new teams updater requires delivery optimization service to be running. What is Delivery Optimization? - Windows Deployment | Microsoft Learn
bing_gao Yes, This error will occur if Delivery Optimisation is disabled in GPO evidenced by RKEY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\DODownloadMode = 100
Set it to 0 and Teams2.x will autoupdate
The old value has been deprecated https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-reference#download-mode
yep - this was the solution for my maschine to! i've tested it with value 0 and 99
THANKS MAN!
Same issue. Additionally however, New-Teams will stop launching altogether, with the generic error message of "The parameter is incorrect".
This happened to us a while back after upgrading Windows 10 from 1809 to 20H2, and some HP Apps started behaving the same way. Eventually there were some updates to the HP Apps, and they started working again. Although, there were several MS updates in the interim as well.
I don't believe this is an environment setting restricting access to Teams update server. The initial install of New-Teams, using the "teamsbootstrapper.exe", will reach out and download the latest version of New-Teams. I may be wrong though. I'm still digging through our GPO's and FW settings to see if anything stands out. There may be an exception needed if New-Teams requires an entirely different update server.
I'll post if I do find anything.
Good luck!
JAG
After having this error for months I brought a new user on this week and they were able to update. Tested on existing devices going into add or remove programs uninstalling new teams app. Going back into old and using the slider to download new teams again. Once switched I now get that I have the latest client installed today. Time will tell if new updates can come down but it can connect now.
It looks like this issue has been fixed in the very latest release but needs a manual uninstall
- Monehton, I'll be interested to hear how that does in the coming week. We are having the same issue as reported above. What would be nice is to have information about the service that is doing the updates, and the endpoints/URLS that the client is reaching out to pull these updates down. That way, we can more easily identify if security software is interfering. Our classic Teams client is not having difficulty pulling updates.
ardamis The log is referencing MSIX, which is Microsoft's "modern" app package format. It is my understanding that this technology is based on the AppX format which was introduced for Universal Windows Platform (UWP) apps, which are primarily installed from the Microsoft Store.
If I had to guess, I would say you have the Microsoft Store Install Service service disabled, and this is causing the issue you are seeing.
- Having same issues. Logs not the same error but same issue updating. Have a call logged but not got past the remove and reinstall
- Thanks for taking the time to respond, Leon.
Can you provide more information about the Teams update service? Does this appear in services.msc, or is there a process name I can look for in Task Manager? Are there any services that it depends on that must be running, that might have been disabled?
I don't see anything outright preventing "ms-teamsupdate.exe" from running (it generates a small log file when I run it directly and presumably is generating the log file referenced in the original post). I'm able to access the URL of the MSIX package file on statics.teams.microsoft.com in the log entry and successfully download the file via a browser, so it doesn't appear to be a lack-of-connectivity issue.
Thank you. Hi ardamis,
The error message in the screenshot indicates that the Teams update service is not able to start. This could be happening for a number of reasons, like:
- The service is disabled.
- The service is blocked by a third-party antivirus or firewall program.
- The service is unable to access the Teams update server.
To troubleshoot this issue, you can try the following:
- Make sure that the Teams update service is enabled.
- Disable any third-party antivirus or firewall programs that you are using.
- Try updating Teams manually by downloading the latest update package from the Microsoft website.
- If you are still having problems, contact Microsoft support for further assistance.
Here are some additional things to check in your corporate environment:
- Make sure that the Teams update server is accessible from your network.
- Check your GPOs to make sure that there are no restrictions on the Teams update service.
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
(LinkedIn)I am getting the same for quite something. It it is there.
