Missing Release Notes for Microsoft Teams

Sascha Ehlers 5 Reputation points
2026-11-03T10:59:05.2633333+00:00

Hello, as a Teams Administrator, I am currently facing an issue where many of my users can no longer end calls using their headset buttons. In the log files, I identified the following error blocking the routine:hidService:

Error: [onDidHook] Failed to determine SfB running state. Error={}

Users running version 26288.2003.5258.9616 and earlier are affected, while users on the newer version 26288.2004.5269.3420 do not experience this problem. Users on the new version also have a new menu in the Teams settings under Devices for headset call control.

It seems this will be resolved simply by waiting for the update, as there is no easy manual way to trigger it. So this post is not about solving the Problem. I want to know: Where can I find official information regarding these specific Teams versions? The release notes on learn.microsoft.com currently only go up to 26276.513.5241.9675 (as of October 29), but the two newer versions we are seeing cannot be found anywhere in the documentation. All Users have Target Release some with optional Preview Release.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ruwim.B 7,245 Reputation points Volunteer Moderator
    2026-11-03T11:42:18.81+00:00

    Unfortunately, you cannot rely neither on the current version number nor on the available features. Microsoft, more or less randomly is pushing release versions and changing the available features.

    On my Windows 11 computer with the latest insider release 26288.2004.5269.3420(Teams Insider), the option to Sync device buttons is not available.

    User's image

    On another Windows 11 computer, with an older Teams 26276.513.52441.9675 version, this option is available.

    User's image

    Everything can change tomorrow, or a month from now.

    Was this answer helpful?

    0 comments
  2. Aetherin 3,520 Reputation points Independent Advisor
    2026-11-03T11:15:34.25+00:00

    Hi @Sascha Ehlers,

    The Microsoft page for reviewing Teams desktop build history is Version update history for Teams app deployments. However, Microsoft specifically notes that this page provides historical build information and is not intended to serve as a real-time build deployment status report.

    During the gradual rollout of a Teams update, Microsoft may increment or replace the build number that was initially released. Therefore, a build displayed in the Teams client may not appear on the page, or it may later be replaced by another listed build. As of November 3, 2026, versions 26288.2003.5258.9616 and 26288.2004.5269.3420 are not listed on the public Teams version-history page.

    The separate Release notes for Microsoft Teams admin features page focuses on administrative features and changes rather than providing a complete history of every Teams desktop client build.

    Teams desktop updates are normally released twice per month and rolled out gradually using Microsoft’s safe deployment practices. As a result, different users in the same organization may temporarily receive different builds. For information about newly released functionality, Microsoft recommends checking the Microsoft 365 Message center or Help > What’s new in Teams.

    User's image

    I could not find another public Microsoft page that provides build-specific release notes for these two versions. Therefore, their absence from the version-history page does not necessarily indicate a deployment problem.

    Since you have identified a reproducible difference between the two builds, you may also open a Microsoft 365 support request through the Microsoft 365 admin center > Help & support.

    User's image User's image

    Microsoft Support may be able to confirm whether this is a known issue and whether the newer build contains a related fix that has not yet been publicly documented. If necessary, they can escalate the case to the appropriate product team for further investigation.

    Thank you so much for taking the time.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.