Skip to the content
The Update Bureau

SharePoint Server 2016 · Release Health

Known issues in SharePoint Server 2016

Problems Microsoft has confirmed for this version, from its official release health notes. 7 still open or mitigated.

SharePoint Server: SE 2019 2016
All products →

Active known issues

Open & Mitigated
7 active issues
  1. Open SharePoint Server 2016 Affects: Organizations and IT administrators Started with KB5002891 · Jul 14, 2026

    Customers who install the SharePoint 2016 July Public Update might find that Office Online Server can't render or edit documents

    After installing the July public update, Office Online Server might not render or edit documents.

    How to apply the workaround SharePoint Management Shell

    The workaround trusts the farm's public signing certificate so Office Online Server can render and edit documents.

    Step-by-step instructions, command & download kit
    4 steps SharePoint Management Shell Instructions (.txt)
    Show steps & kit Hide steps & kit
    Step-by-step procedure
    1. Get the STS signing certificate and export its public certificate to STS_Public.cer.
    2. Check that $pub.HasPrivateKey returns False.
    3. Register the public certificate as a trusted token issuer.
    4. Run iisreset on every SharePoint server in the farm.
    SharePoint Management Shell 
    > $stsm = Get-SPSecurityTokenServiceConfig> $live = $stsm.LocalLoginProvider.SigningCertificate> $bytes = $live.Export("Cert")> $tempFile = "$env:TEMP\STS_Public.cer"> Set-Content -Path $tempFile -Value $bytes -Encoding Byte> $pub = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($tempFile)> $pub.HasPrivateKey> $realm = $stsm.NameIdentifier> New-SPTrustedSecurityTokenIssuer `
        -Name "LocalSelfIssuerWopiFix" `
        -Description "Re-trust farm self-issuer after July PU" `
        -Certificate $pub `
        -RegisteredIssuerName $realm> iisreset
  2. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002882 · Jul 14, 2026

    When a workflow status link is selected, WrkStat.aspx displays the following error message: The WorkflowInstanceID parameter is invalid

    Selecting a workflow status link can make WrkStat.aspx show “The WorkflowInstanceID parameter is invalid.”

    How to apply the workaround Workaround

    Follow Microsoft's linked guidance for workflow status links.

  3. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002882 · Jul 14, 2026

    Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple sign-ins

    Multi-front-end farms using Trusted Provider or Forms authentication might show repeated sign-in prompts. Farms using Windows authentication should not be affected.

    How to apply the workaround Workaround

    Configure sticky sessions on the reverse proxy; this addresses most reported scenarios.

  4. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002800 · Nov 11, 2025

    Users may see “4gab5" event tags logged in the SharePoint Unified Logging System (ULS) logs when they access sitedirectorysettings.aspx by using ‘set other host’

    Users might see “4gab5” event tags in SharePoint Unified Logging System (ULS) logs when they access sitedirectorysettings.aspx using ‘set other host’.

    How to apply the workaround SharePoint Management Shell

    Adding the additional farm host allows it to access the page, which is otherwise restricted to the current farm host.

    Step-by-step instructions, command & download kit
    3 steps SharePoint Management Shell Instructions (.txt)
    Show steps & kit Hide steps & kit
    Step-by-step procedure
    1. Confirm that the additional host is safe before adding it.
    2. In the SharePoint Management Shell, add the host to AdditionalValidSPFarmHosts and update the farm.
    3. Run iisreset.
    SharePoint Management Shell 
    > add-pssnapin *> $f = get-spfarm> $f.AddGenericAllowedListValue("AdditionalValidSPFarmHosts", "your_additional_farm_host")> $f.update()> iisreset
  5. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002771 · Aug 12, 2025

    After you install KB5002771, you might experience an issue when you configure calendar overlay settings

    You might experience an issue when configuring calendar overlay settings after installing KB5002771.

    Workaround status No workaround yet

    Microsoft has not published a manual workaround for this issue yet. Defer KB5002771 on affected systems until a fix is released.

  6. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002768 · Jul 21, 2025

    $farm.RemoveGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")

    Some SharePoint page resources might fail to load, and ULS logs might show an access denied message.

    How to apply the workaround SharePoint Management Shell

    Add the valid resource path to the AllowList, then restart IIS.

    Step-by-step instructions, command & download kit
    2 steps SharePoint Management Shell Instructions (.txt)
    Show steps & kit Hide steps & kit
    Step-by-step procedure
    1. Make sure the resource path is valid and as expected.
    2. Run the commands in SharePoint Management Shell.
    SharePoint Management Shell 
    > $farm = get-spfarm> $farm.AddGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")> $farm.Update()> iisreset
  7. Open SharePoint Server 2016 2019 SE Affects: Organizations and IT administrators Started with KB5002768 · Jul 21, 2025

    $farm.ContainsGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")

    Some SharePoint page resources might not load, and an Access Denied message might appear in the logs.

    How to apply the workaround SharePoint Management Shell

    Adding the resource path to the AllowList lets the affected page resource load.

    Step-by-step instructions, command & download kit
    2 steps SharePoint Management Shell Instructions (.txt)
    Show steps & kit Hide steps & kit
    Step-by-step procedure
    1. Make sure the resource path is valid and as expected.
    2. In SharePoint Management Shell, add the resource path to the AllowList, update the farm, and run iisreset.
    SharePoint Management Shell 
    > $farm = get-spfarm> $farm.AddGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")> $farm.Update()> iisreset

No known issue matches these filters.