Trending issue with Distributed Cache and July 2026

UPDATE: This issue is fixed by the August 2026 updates.

The July 2026 update was released July 14, 2026. This introduced many security fixes but this can cause issues with your SAML, OIDC, or FBA implementations. This can prevent tokens from being added or read from dcache.

Here are some logs from my 2019 farm:
07/18/2026 12:18:03.74 w3wp.exe (0x0FF8) 0x1914 SharePoint Foundation DistributedCache air38 Medium Token Cache: Failed to add token from distributed cache. Key: ‘0e.t|microsoftentratrust|user1@TestTestTest.onmicrosoft.com’, Exception: ‘System.NotSupportedException: Specified method is not supported. at Microsoft.SharePoint.IdentityModel.SPTokenCache.NotSupportedCookieTransform.Encode(Byte[] value) at Microsoft.IdentityModel.Tokens.SessionSecurityTokenHandler.ApplyTransforms(Byte[] cookie, Boolean outbound) at Microsoft.IdentityModel.Tokens.SessionSecurityTokenHandler.WriteToken(XmlWriter writer, SecurityToken token) at Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter writer, SecurityToken token) at Microsoft.SharePoint.Administration.Claims.SPTokenCacheEntry.SerializeToken(SecurityTokenSerializer tokenSerializer) at Microsoft.SharePoint.IdentityModel.SPDistributedSecurityTokenCache.Put(String key, Object value) at Microsoft.SharePoint.IdentityModel.SPTokenCache.AddCachedTokenV1(String cachekey, SPTokenCacheEntry value)’. 908628a2-2a7c-10e3-545f-1f5de6df25d3

07/18/2026 12:18:03.74 w3wp.exe (0x0FF8) 0x1914 SharePoint Foundation DistributedCache air39 Medium Token Cache: Reverting to local cache to Add the token. Key: ‘0e.t|microsoftentratrust|user1@TestTestTest.onmicrosoft.com’. 908628a2-2a7c-10e3-545f-1f5de6df25d3

Log entry from SPSE:
07/23/2026 14:34:31.14 w3wp.exe (0x6128) 0x2814 SharePoint Foundation DistributedCache aa6e6 Unexpected Unexpected error in ByteArrayToObject – Exception ‘System.NotSupportedException: Specified method is not supported. at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenHandlerV2.ReadToken(XmlReader reader) at System.IdentityModel.Tokens.SecurityTokenHandlerCollection.ReadToken(XmlReader reader) at Microsoft.SharePoint.Administration.Claims.SPTokenCacheEntry..ctor(SerializationInfo info, StreamingContext context) at ReadSPTokenCacheEntryFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] ) at System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context) at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract) at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns) at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver) at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver) at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(XmlDictionaryReader reader) at Microsoft.SharePoint.DistributedCaching.SPDistributedCacheUtils.ByteArrayToObject[T](Byte[] Buffer)’.

The PG is currently investigating the issue above and hoping to get a fix sooner than later. I would suggest using sticky sessions or persistence at your NLB. Failing to read a token from the dcache will fall back to the local cache(the STS). If the request hits a different WFE than the one you and the token is unable to be located (dcache and local), SharePoint invalidates the clients FedAuth cookie and makes them reauthenticate.

Trending Issue with SharePoint June 2026 update and 2010 workflows

This is resolved with July 2026 Update.

The June 2026 update for SharePoint 2016, 2019, and Subscription Edition have an issue with SharePoint 2010 Workflows. We saw a similar issue with September 2024 updates (see my post here: SharePoint 2016 2019 SE – Workflows are not working after September 2024 update – Adventures of SharePoint OnPrem).

All SharePoint 2010 workflows are going to show up as Failed on Start. The ULS logs will show the following error:

06/11/2026 20:19:43.74	w3wp.exe (0x2308)	0x0E18	SharePoint Foundation	Legacy Workflow Infrastructure	66eav	High	spNoCodeXomlCompiler.IsGoodWorkflow: Potentially malicious WorkflowCodeTypeReferenceExpression: <ns2:WorkflowCodeTypeReferenceExpression QualifiedName="Microsoft.SharePoint.WorkflowActions.Helper" Type="Microsoft.SharePoint.WorkflowActions.Helper" xmlns:ns2="clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" />	3ca81ca2-13ac-50de-cf2c-8aa40f51dfd5

Adding more lines to the web.config will not resolve this issue. The PG is aware and investigating this issue at this time. I will be updating this post as the investigation continues.

Description of the security update for SharePoint Server Subscription Edition: June 9, 2026 (KB5002873) – Microsoft Support

Description of the security update for SharePoint Server 2019: June 9, 2026 (KB5002874) – Microsoft Support

Description of the security update for SharePoint Server 2019 Language Pack: June 9, 2026 (KB5002876) – Microsoft Support

Description of the security update for SharePoint Server 2016: June 9, 2026 (KB5002880) – Microsoft Support

Description of the security update for SharePoint Server 2016 Language Pack: June 9, 2026 (KB5002881) – Microsoft Support

SharePoint WFM versions and Download links

I will be updating this post as the updates for SPWFM (SharePoint Workflow Manager) are released. Make sure to upload the SPWFM Client on the same version on all SPWFM and SharePoint servers.

Release DateBuild VersionKB NumberKB LinkDownload LinkClient Download
April 14, 202616.0.19725.202105002844April 14, 2026, update for SharePoint Workflow Manager (KB5002844) – Microsoft SupportDownload Update for Microsoft SharePoint Workflow Manager (KB5002844) from Official Microsoft Download CenterSharePoint Workflow Manager Client (16.0.19725.20210)​​​​​​​
Feb 10, 202616.0.19127.205065002814February 10, 2026, update for SharePoint Workflow Manager (KB5002814) – Microsoft SupportDownload the update for Microsoft SharePoint Workflow Manager (KB5002814)​​​​​​​.SharePoint Workflow Manager Client (16.0.19127.20336)​​​​​​​
Nov 11, 202516.0.19127.203365002799November 11, 2025, update for SharePoint Workflow Manager (KB5002799)Download Update for Microsoft SharePoint Workflow Manager (KB5002799)SharePoint Workflow Manager Client (16.0.19127.20336)​​​​​​​
Oct 14, 202516.0.19127.202625002785October 14, 2025, update for SharePoint Workflow Manager (KB5002785)Download Update for Microsoft SharePoint Workflow Manager (KB5002785)SharePoint Workflow Manager Client (16.0.19127.20262)​​​​​​​
Aug 12, 202516.0.18526.205185002750August 12, 2025, update for SharePoint Workflow Manager (KB5002750)Download Update for Microsoft SharePoint Workflow Manager (KB5002750)SharePoint Workflow Manager Client (16.0.18526.20518)
Jun 10, 202516.0.18526.203625002737June 10, 2025, update for SharePoint Workflow Manager (KB5002737)Download Update for Microsoft SharePoint Workflow Manager (KB5002737)SharePoint Workflow Manager Client (16.0.18526.20362)​​​​​​​
May 13, 202516.0.18526.203165002726May 13, 2025, update for SharePoint Workflow Manager (KB5002726)Download Update for Microsoft SharePoint Workflow Manager (KB5002726)SharePoint Workflow Manager Client (16.0.18526.20316)​​​​​​​
RTM16.0.15601.20418Download SharePoint Workflow Manager

SharePoint 2016 – April 2025 KB 5002692 fails to install

UPDATE: This KB was fixed and released. Please download a new version of KB5002692.

The security update for SharePoint 2016 in April 2025 will not install. This is not like the past where some processes are locking DLLs preventing them from updating.

SharePoint 2016 update: Description of the security update for SharePoint Enterprise Server 2016: April 8, 2025 (KB5002692) – Microsoft Support

This will fail to install due to a DLL that is signed incorrectly. The OPatch logs will show the DLL fail the verification. Find your Opatch logs by going to %temp% and opening sts-x-none_MSPLOG.LOG. Look for the following line:

 Assembly Error:Strong name signature verification failed for assembly '%1'.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.
Microsoft.Office.Project.Server.PWA,fileVersion="16.0.5493.1000",version="16.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL" 

Currently there is no fix for this issue. I will be updating this post as information becomes available.

SharePoint 2016 2019 SE – Workflows are not working after September 2024 update

The September 2024 updates fixed a security issue but this caused the web.configs needing entries for workflows to function.

SharePoint SE: Description of the security update for SharePoint Server Subscription Edition: September 10, 2024 (KB5002640) – Microsoft Support

SharePoint 2019: Description of the security update for SharePoint Server 2019: September 10, 2024 (KB5002639) – Microsoft Support

SharePoint 2016: Description of the security update for SharePoint Enterprise Server 2016: September 10, 2024 (KB5002624) – Microsoft Support

This will affect SharePoint 2010 workflows. We will see event tag ‘c42q0’ in the ULS logs. The KBs have the fix listed but this should be applied to ALL servers. This is due to any SharePoint 2010 workflows with a Pause. This will have the workflow be picked up by the Workflow timer job. OWSTimer will reference the entries in the web.config for the web application on server that is running the job.

How to fix this?

Manually add in this into every web.config for every server.

We can also utilize SharePoint’s WebConfigModifications. The PowerShell below will add in the line as described in the KBs:

<System.Workflow.ComponentModel.WorkflowCompiler>
   <authorizedTypes>
     <targetFx version="v4.0">
        <authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" Namespace="Microsoft.SharePoint.WorkflowActions.WithKey" TypeName="*" Authorized="True" />
    </targetFx>
   </authorizedTypes>

NOTE: The script does check to see if the Owner is already added in to prevent duplicate entries. This will add in the entry for ALL web applications. This will also apply the change to all the servers.

Add-PSSnapin Microsoft.SharePoint.PowerShell

# Define the modification
$modification = New-Object Microsoft.SharePoint.Administration.SPWebConfigModification
$modification.Path = "configuration/System.Workflow.ComponentModel.WorkflowCompiler/authorizedTypes/targetFx"
$modification.Name = "authorizedType[@Assembly='Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null' and @Namespace='Microsoft.SharePoint.WorkflowActions.WithKey' and @TypeName='*' and @Authorized='True']"
$modification.Sequence = 0
$modification.Owner = "Sept2024Workflow"
$modification.Type = [Microsoft.SharePoint.Administration.SPWebConfigModification+SPWebConfigModificationType]::EnsureChildNode
$modification.Value = "<authorizedType Assembly='Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null' Namespace='Microsoft.SharePoint.WorkflowActions.WithKey' TypeName='*' Authorized='True' />"

# Get all web applications
$webApps = Get-SPWebApplication 

foreach ($webApp in $webApps) {
    Write-Host "Applying changes to $($webApp.Url)"
    # Add the modification to the web application
    If($webApp.WebConfigModifications | ? {$_.owner -eq "Sept2024Workflow"})
    {
        Write-Host "$($webapp.Url) already has fix for Sept2024Workflow.  Skipping"
    }
    Else
    {
        $webApp.WebConfigModifications.Add($modification)
        $webApp.Update()
    
        # Apply the changes
        $webApp.WebService.ApplyWebConfigModifications()
        Write-Host "Completed changes to $($webApp.Url)"
    }
}