This issue has already been discussed by several visitors of my site including sharing a variety of workarounds – but for completeness I’m including it here as a dedicated Trending Issue.
When running a 2010 workflow associated with a list, a column containing the workflow status is added to the list with a link to the workflow history list. Clicking this link redirects the user to the application page /_layouts/15/WrkStat.aspx.
After installing July 2026 CU the link in this column is incorrectly encoded resulting in the following error message:
Invalid WorkflowInstanceID parameter in URL.
Workarounds
- Manually edit the Url
manually fix the Url by replacing the double encoded percent char %25 chars with %. - Use a different way to open the same page
Click the ellipsis of the list item – more – workflows - Create a Url Rewrite rule to fix the incorrect Url
An official KB article outlining the required steps has now been published:
KB 5122408 – Workflow status links fail after installing the July 2026 CU
Solution
The fix for this issue is included in August 2026 CU
Permalink
Hi Stefan, great information. I just came across this problem myself. Do you know if the upcoming fix will also apply to SharePoint Server 2019, or only to SharePoint Server Subscription Edition?
Permalink
Hi Oscar,
from what I have heard all SharePoint versions will receive the fix for the WorkflowInstanceID.
Cheers,
Stefan
Permalink
Thanks Stefan, fingers crossed! 🙂
Permalink
Hi Stefan,
Short Info:
We also encountered this error in another .aspx Page: If we have workflow tasks which are created by a SharePoint 2010 Workflow and have an InfoPath Form for the taks, the same encoding error occurs.
This happens for the /_layouts/15/WrkTaskIP.aspx Form where the URL was also double encoded.
We added a rewrite rule for this .aspx page as well and it started working again.
Before we were not able to open the Form for tasks created after the July 2026 CU install. After inserting the rewrite rule it started working again.
BR,
Chris
Permalink
Thanks!
I passed this info to our engineering team.
Cheers,
Stefan
Permalink
Hi Chris,
engineering has tried but was not able to reproduce the issue.
My recommendation would be to open a support ticket with Microsoft to ensure that this can be investigated.
Cheers,
Stefan
Permalink
Hi Stefan,
Any updates about the fix for this issue?
Thanks,
Winston
Permalink
Hi Winston,
the fix is planned to be released next week.
Cheers,
Stefan
Permalink
I installed the July updates for SharePoint 2019 (on-premises) in our test environment (we always do this first), no errors reported during the patch process. The only issue I found is that the News app does not load any longer on our Intranet home page, which I believe uses iFrames (we had no issues with the June updates). There is a red circle with a line through it instead of the pictures and stories. If you hover over the page it provides the following message “app-cbc7ffda61e3f1.dsuspapps.com refused to connect.” I ran the following and restarted did an IIS reset, same result:
$farm = Get-SPFarm
$farm.AddGenericAllowedListValue(“AllowIframeAppAuthorizePageDomains”, “*.dsuspapps.com”)
$farm.Update()
I checked the developer console and see the following:
Uncaught TypeError: Cannot read properties of undefined (reading ‘indexOf’)
at HTMLAnchorElement. (usd.js:7:18)
at m.each (jquery-1.11.1.min.js:2:2973)
at m.fn.init.each (jquery-1.11.1.min.js:2:835)
at HTMLDocument. (usd.js:3:12)
at j (jquery-1.11.1.min.js:2:27244)
at Object.fireWith [as resolveWith] (jquery-1.11.1.min.js:2:28057)
at m.ready (jquery-1.11.1.min.js:2:29891)
at HTMLDocument.J (jquery-1.11.1.min.js:2:30257)
Framing ‘http://app-cbc7ffda61e3f1.dsuspapps.com/’ violates the following Content Security Policy directive: “frame-ancestors ‘self’ and then it lists a bunch of microsoft domains
I see an article that discusses this from your blog back in March of 20204, but find it odd that this would be a solution given that it’s from 2024 – https://blog.stefan-gossner.com/2024/03/12/control-content-security-policy-header-for-sharepoint-pages/
I have a message into our SharePoint consultant, but wanted to run this past you in case you had some ideas. Thank you for the work you do.
Jason
Permalink
Hi Jason,
in general the 2024 article still applies.
If you need to use a custom CSP Header you need to disable the CSP headers injects by SharePoint using the script outlined in the 2024 article.
About the behavior change you noticed in July 2026 CU – you might want to test the script form the article you quoted to ensure that verify if it solves the issue.
Cheers,
Stefan
Permalink
Hi Chris,
After applying the July 2026 CU to SP2019 On-premise, the paging in Modern experience is not working.
Neither does it display the item count if the view is configured to show count.
Is there any fix for this ?
Thanks,
Medha
Permalink
Hi Stefan,
Hope you are doing Great 🙂
We are unable to access the August 2026 Cumulative Update for SharePoint Server Subscription Edition. The KB link
https://support.microsoft.com/kb/5002893
currently returns “Sorry, page not found.”
Could you please confirm whether the KB page has been moved or if there is an issue with the publishing of the August CU?
Thank you for your help.
Permalink
Hi Stefan,
After applying the July 2026 CU to SP2019 On-premise, the paging in Modern experience is not working.
Neither does it display the item count if the view is configured to show count.
Is there any fix for this ?
Thanks,
Medha
Permalink
Hi Stefan,
Since the fix is in the CU for SP2019 and SPSE, will there be a separate hotfix released for SP2016 to fix this bug in their ‘last patch’ ?
Or are all SP2016 customers expected to implement the web config rewrite section?
Permalink
Hi D´Arcy,
the fix for the incorrect encoded workflow links is also in the SP2016 CU.
Cheers,
Stefan