Trending issue: SharePoint 2010 workflows are failing after installing July 2026 CU

- - 106 Comments

After installing July 2026 CU you might experience failures with SharePoint 2010 workflows.
The reason is that – depending on the workflow actions used in your workflows – additional types might need to be allow listed.

Symptoms:

In the ULS log you will find entries similar to the following:

w3wp.exe (0xXXXX)   SharePoint Foundation   Legacy Workflow Infrastructure   c42q0   High   Potentially malicious xoml node: <ns0:CodeMethodInvokeExpression.Parameters xmlns:ns0="clr-namespace:System.CodeDom;Assembly=System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> ...

Solution:

To resolve this issue ensure to add the following authorizedType entry exist in all web.config files for your SharePoint web applications:

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

Automation

To simplify this task, I created a PowerShell script which uses the SPWebConfigModification class to add this entry automatically on all servers in the farm to a given web application:

106 Comments


  1. I am testing this in my Staging farms still, and would like clarification as to where this line needs to be applied.

    I have copied it to each of the web.config files on all of my SP servers in the following location:

    C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\CONFIG

    Do I then need to add the line to the following, where I have multiple web apps

    C:\inetpub\wwwroot\wss\VirtualDirectories

    Thanks

    Reply

      1. I have now added a sample script to apply the change to the post above.

        Reply

        1. You’re the man. Thanks Stefan.

          Reply

  2. I have updated all web.config files for all web applications to all servers in the farm, but the issue persists.
    Do we also need to remove all other authorizedType entries and include only the one mentioned above?
    Is there any importance on the order where we need to add the entry?

    Thank you!

    Reply

    1. Hi Georgia,
      no – absolutely not!
      All of them need to stay!

      To simplify the task you can run the following PowerShell script on one server in the farm hosting the web application. It uses SPWebConfigModification to update the web.config on all servers in the farm for a given web application:

      https://blog.stefan-gossner.com/fix-systemcodedom-ps1

      Cheers,
      Stefan

      Reply

      1. Hi Georgia,
        in case the issue is not resolved, check the ULS log and provide details about the errors you see.
        Cheers,
        Stefan

        Reply

        1. I have run the Powershell script, but still no resolved.

          These are the errors form the ULS logs:

          07172026 175514.89 w3wp.exe (0x271C) 0x39B4 SharePoint Foundation Legacy Workflow Infrastructure 4letu High Block the namespace clr-namespaceMicrosoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type LookUpManagerOfActivity fd2b28a2-af73-3092-6135-4687313015e6
          07172026 175514.89 w3wp.exe (0x271C) 0x39B4 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node ns2LookUpManagerOfActivity __Context={ActivityBind ROOT,Path=__context} ReturnValue={ActivityBind ROOT,Path=manager} xName=ID38 UserValue={ActivityBind ID39,Path=ReturnValue} xmlnsx=httpschemas.microsoft.comwinfx2006xaml xmlnsns2=clr-namespaceMicrosoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null . If this type is considered legitimate, add TypeName=’LookUpManagerOfActivity’ to the authorizedTypes section in server config. Ask your farm administrator to add the corresponding assembly to farm property WorkflowTrustedAssemblies. fd2b28a2-af73-3092-6135-4687313015e6
          07172026 175514.89 w3wp.exe (0x271C) 0x39B4 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High CompileBytes Web httpshost, Site httpshost, Tenant , Error parsing xoml ns0RootWorkflowActivityWithData xClass=Microsoft.SharePoint.Workflow.ROOT xName=ROOT xmlns=httpschemas.microsoft.comwinfx2006xamlworkflow xmlnsns1=clr-namespaceMicrosoft.SharePoint.WorkflowActions.WithKey;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null xmlnsns2=clr-namespaceMicrosoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null xmlnsx=httpschemas.microsoft.comwinfx2006xaml xmlnsns0=clr-namespaceMicrosoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null ns0RootWorkflowActivityWithData.WorkflowFields ns0WorkflowDataField Type=System.String Name=__list ns0WorkflowDataField Type=Microsoft.SharePoint.Workflow.SPItemKey, Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c Name=__item ns0WorkflowDataField Type=Microsoft.SharePoint.WorkflowActions.WorkflowContext Name=__context ns0WorkflowDataField Type=Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties Name=__initParams ns0WorkflowDataField Type=System.Guid Name=__workflowId ns0WorkflowDataField Type=System.String Name=__historylist ns0WorkflowDataField Type=System.String Name=__tasklist ns0WorkflowDataField Type=System.Int32 Name=__itemId ns0WorkflowDataField Type=Microsoft.SharePoint.Workflow.SPItemKey, Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c Name=create ns0WorkflowDataField Type=System.String Name=manager ns0RootWorkflowActivityWithData.WorkflowFields ns0OnWorkflowActivated WorkflowProperties={ActivityBind ROOT,Path=__initParams} xName=ID1 ns0OnWorkflowActivated.CorrelationToken wf0CorrelationToke… fd2b28a2-af73-3092-6135-4687313015e6
          07172026 175514.89 w3wp.exe (0x271C) 0x39B4 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High …n OwnerActivityName=ROOT Name=refObject xmlnswf0=httpschemas.microsoft.comwinfx2006xamlworkflow ns0OnWorkflowActivated.CorrelationToken ns0OnWorkflowActivated ns0ApplyActivation xName=ID2 __WorkflowProperties={ActivityBind ROOT,Path=__initParams} __Context={ActivityBind ROOT,Path=__context} SequenceActivity Description=Step 1 xName=ID3 IfElseActivity xName=ID4 IfElseBranchActivity xName=ID5 IfElseBranchActivity.Condition RuleConditionReference ConditionName=__Rule_ID5 IfElseBranchActivity.Condition ns0ClearHashtableActivity Collection={xNull} xName=ID20 ns1LookupActivity ListId={ActivityBind ROOT,Path=__list} LookupFunction=LookupString __Context={ActivityBind ROOT,Path=__context} FieldName=Title ListItem={ActivityBind ROOT,Path=__item} xName=ID23 ns0CoerceStringActivity CoercionFunction=AsDNString __Context={ActivityBind ROOT,Path=__context} xName=ID22 ns0CoerceStringActivity.Value ActivityBind Path=ReturnValue Name=ID23 ns0CoerceStringActivity.Value ns0CoerceStringActivity ns0AddToHashtableActivity ValueType=System.String Collection={ActivityBind ID20,Path=Collection} Key=Title xName=ID21 ns0AddToHashtableActivity.Value ActivityBind Path=ReturnValue Name=ID22 ns0AddToHashtableActivity.Value ns0AddToHashtableActivity ns1LookupActivity ListId={ActivityBind ROOT,Path=__list} LookupFunction=LookupString __Context={ActivityBind ROOT,Path=__context} FieldName=CanvasContent1 ListItem={ActivityBind ROOT,Path=__item} xName=ID26 ns0CoerceStringActivity CoercionFunction=AsDNString __Context={ActivityBind ROOT,Path=__context} xName=ID25 ns0CoerceStringActivity.Value ActivityBind Path=ReturnValue Name=ID26 ns0CoerceStringActivity.Value ns0CoerceStringActivity ns0AddToHashtableActivity Va… fd2b28a2-af73-3092-6135-4687313015e6

          Reply

          1. Yeah – in your case there are many more missing classes from a different assembly and namespace.
            Seems your authorizedType entries were not up2date before.

            Please add this one as well:
            <authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True” />

            Cheers,
            Stefan


          2. I also added the new entry.
            Unfortunately, still the same.

            please check the ULS logs:

            07/17/2026 18:25:11.79 OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42qz High CompileBytesPERF: It took 0 ticks to load the authorized types. b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80 OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure 4letu High Block the namespace: clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: RootWorkflowActivityWithData b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80 OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns0:RootWorkflowActivityWithData.WorkflowFields> </ns0:RootWorkflowActivityWithData.WorkflowFields> <ns0:OnWorkflowActivated.CorrelationToken> </ns0:OnWorkflowActivated.CorrelationToken> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <IfElseBranchActivity.Condition> <RuleConditionRefere… b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80* OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42q0 High …nce ConditionName=”__Rule_ID42″ /> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> . If this type is considered legitimate, add TypeName=’RootWorkflowActivityWithData’ to the authorizedTypes section in server config. Ask your farm administrator to add the corresponding assembly to farm property WorkflowTrustedAssemblies. b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80 OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42q8 High CompileBytes: Web https://host, Site https://host, Tenant , Error parsing xoml: <ns0:RootWorkflowActivityWithData.WorkflowFields> </ns0:RootWorkflowActivityWithData.WorkflowFields> <ns0:OnWorkflowActivated.CorrelationToken> <wf0:CorrelationToke… b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80* OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42q8 High …n OwnerActivityName=”ROOT” Name=”refObject” xmlns:wf0=”http://schemas.microsoft.com/winfx/2006/xaml/workflow” /> </ns0:OnWorkflowActivated.CorrelationToken> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:AddToHashtableActivity.Value> </ns0:AddToHashtableActivity.Value> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <IfElseBranchA… b52d28a2-4f63-3092-6135-4c42c7188952
            07/17/2026 18:25:11.80* OWSTIMER.EXE (0x1590) 0x1A0C SharePoint Foundation Legacy Workflow Infrastructure c42q8 High …ctivity.Condition> </IfElseBranchActivity.Condition> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> b52d28a2-4f63-3092-6135-4c42c7188952


          3. Does not look as if you added it at the right place.
            Still complaining about the same class and namespace:

            clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: RootWorkflowActivityWithData b52d28a2-4f63-3092-6135-4c42c7188952


          4. I just ran the script with the entry you provided. What is the right place to add it? Should I add it manually instead?


          5. Hi Georgia,
            yes – but the script only updates one of the references.
            You either need to update it to also update the reference for the additional Microsoft.SharePoint.WorkflowActions assembly or manually add the entry to all web.config file underneath the inetpub directory.
            But if you need assistance here, best option would be to open a case with Microsoft Support who can guide you through the steps.
            Cheers,
            Stefan


          6. Thank you Stefan. Our farm is SharePoint 2019, so it is out of support now. I am not sure if I can open a ticket.


          7. I also needed to add the following namespaces:

            Also, the namespace seems that it needs to be added after adding all the other ones.

            Thanks again for the valuable help!


          8. I also needed to add the following namespaces:
            “”
            “”

            Also, the namespace seems that it needs to be added after adding all the other ones.
            “”

            Thanks again for the valuable help!


          9. We are facing the same issue. How did you manage to resolve this ?


          10. Yes, I also needed to add the following namespaces:
            [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions.WithKey” TypeName=”” Authorized=”True” /]
            [authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Actions” TypeName=”” Authorized=”True” /]

            Also, this namespace seems that it needs to be added after adding all the other ones.
            [authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.CodeDom” TypeName=”*” Authorized=”True” /]

            *For some reason, everything after <> is erased, so I replaced it with [].

            Don’t forget to run iisreset to all servers after the changes!


          11. It is actually not removed – the comments support html tags. so the XML is there – but not visible.
            You can add it be replacing <…> with &lt;…&gt;


  3. Hi Stefan,
    Thank you for providing the script, however when attempting to run, assuming in PowerShell ISE as admin, the following error is generated

    Get-SPWebApplication : The term ‘Get-SPWebApplication’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At D:\SharePoint Deployment\04 Farm Config\Net_patch_fix\Add-CodeDomAuthorizedType_Stefan.ps1:30 char:11
    + $webApp = Get-SPWebApplication $WebApplicationUrl
    + ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-SPWebApplication:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Can you resolve please?

    Many thanks

    Reply

    1. Hi Scott,

      this is a script for the SharePoint Management Shell where the SharePoint classes are automatically loaded.
      PowerShell ISE on SP2016 and SP2019 is NOT SharePoint aware.
      You need to load the SharePoint classes first using

      Add-PSSnapin Microsoft.SharePoint.PowerShell

      Cheers,
      Stefan

      Reply

      1. Many thanks Stefan,

        So basically, run SP Mgmt shell, navigate to the path where the script is and run from there?

        Reply

  4. Hi Stefan,
    Is it safe to change that in web.config file?
    But this is working in my spse site for workflows.

    Regards,
    Manish Singh

    Reply

    1. Hi Manish,
      if you do not experience any problems you don’t have to change anything.
      Not sure what you mean with “safe” in this context.
      Cheers,
      Stefan

      Reply

  5. Hi Stefan,
    Thanks a lot for this detailed information and the proposed fix. It appears that, in addition to this issue, there is a second one related to Workflow 2010 resulting from the deployment of the July 2026 Cumulative Update.

    When running a 2010 workflow associated with a list, a column containing the workflow status is added to that list with a link to the history list. Clicking on this link redirects the user to the application page /_layouts/15/WrkStat.aspx to view the workflow’s execution logs.

    Following the deployment of the July 2026 Cumulative Update, the workflow status links are broken. The WorkflowInstanceID passed as a parameter is encoded twice, which results in an error on the WrkStat.aspx page stating that the WorkflowInstanceID parameter is invalid.

    Here is an exemple of a broken workflow status link after the CU July 2026
    https://mydomain.test.ch/sites/wf2010cu/_layouts/15/WrkStat.aspx?List=6ad68331-23cb-403f-a261-5e3ddc6b4252&WorkflowInstanceID=%257b5C3B04B5%252d7099%252d42A9%252d8073%252dEBB154B9EAC9%257d

    And here is the same link which is working before the CU installation
    https://mydomain.test.ch/sites/wf2010cu/_layouts/15/WrkStat.aspx?List=6ad68331-23cb-403f-a261-5e3ddc6b4252&WorkflowInstanceID=%7b5C3B04B5%2d7099%2d42A9%2d8073%2dEBB154B9EAC9%7d

    Could you confirm the issue?

    Thank you in advance
    Best regards
    Didier

    Reply

  6. Thank you very much for providing this fix, I noticed that our Sharepoint 2010 workflows weren’t able to run if they had the Change item permission action, until I ran your .ps1

    Reply

    1. Great to hear!
      Thanks for the feedback!
      🙂

      Reply

  7. HI Stefan,

    After installing July 2026 CU on SharePoint 2016, I kept the June workaround:

    $farm = Get-SPFarm
    $farm.EnablePreParseSecurityCheckForWorkflow = $false
    $farm.Update()

    All our SharePoint 2010 workflows continue to run successfully and we did not add the authorizedType entries to the web.config.

    In this scenario, is it still recommended to update the web.config and re-enable the PreParse security check, or can the farm continue to operate using the existing workaround?

    Thanks for your guidance.
    Anwar

    Reply

    1. Hi Anwar,
      from a security standpoint you should revert this setting as soon as possible.
      Cheers,
      Stefan

      Reply

  8. I also needed to add the following namespaces:
    [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions.WithKey” TypeName=”” Authorized=”True” /]
    [authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Actions” TypeName=”    ” Authorized=”True” /]

    Also, the namespace seems that it needs to be added after adding all the other ones.
    [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True” /]

    Thanks again for the valuable help!

    *For some reason, everything after <> is erased, so I replaced it with [].

    Reply

    1. In the first two lines, is it TypeName =”” or TypeName=”*”.
      Please confirm.

      Reply

      1. with an asterisk. “*”

        Reply

  9. I also needed to add the following namespaces:
    “”
    “”

    Also, the namespace seems that it needs to be added after adding all the other ones.
    “”

    Thanks again for the valuable help!

    Reply

  10. I can say that following the running of the script, all Nintex WF tests have completed successfully.

    Did I see somewhere a link to a PS script to create the URL rewrite for the WF status link?

    Many thanks

    Reply

    1. Hi Scott,
      a KB article will be released shortly with detailed steps to create such an URL rewrite rule.
      Cheers,
      Stefan

      Reply

  11. Hi Stefan,

    After installing the July 2026 Cumulative Update for SharePoint Server Subscription Edition (KB5002882), we have been experiencing issues with Nintex workflows.
    The issues we are seeing are:

    Nintex workflows fail to start.
    Nintex workflows fail to publish.

    As part of our troubleshooting, we applied the Fix-SystemCodeDom.ps1 script referenced in the following blog post, but the issue still persists:
    https://blog.stefan-gossner.com/fix-systemcodedom-ps1

    Could you please advise if there is a known issue with this cumulative update, and recommend a fix or workaround to resolve the problem?

    Thank you for your assistance

    Reply

    1. Hi Surya,
      no this is not a known issue.
      Another customer confirmed that Nintex workflows started working after applying the script:
      https://blog.stefan-gossner.com/2026/07/17/trending-issue-sharepoint-2010-workflows-are-failing-after-installing-july-2026-cu/#comment-68805

      My suggestion would be to check the ULS log for potentially additional required authorizedTypes from Nintex or similar (look for c42q0 and 4letu event tags in the ULS log.
      If Nintex workflows still fail after this my suggestion would be to contact Nintex for assistance.

      Cheers,
      Stefan

      Reply

      1. Hi Stefan,

        I deleted the authorizedType entry that was created by the script and cleared all pending WebConfigModifications.
        After that, I re-ran the script and performed an IIS reset on all the servers. This resolved the issue for me, and the Nintex Synchronization job also running for me.
        Thank you for your help.

        I have a couple of follow-up questions:
        Do we need to add the following authorizedType entry to the web.config?

        Could you please share more details about the broken links or the steps to reproduce the URL rewrite issue?How can we test and verify this URL rewrite scenario?

        Thank you for your assistance

        Reply

        1. Hi Surya,
          the entry did not go through – ensure to change the angular brackets to [] or similar.
          The broken link are the links to the workflow status page.
          Cheers,
          Stefan

          Reply

  12. Hello,

    I just installed the latest SharePoint CU Update + Nintex release on our test farm. Updates ran without any issues. Added the necessary authorized types and Nintex workflows are still running (the flag EnablePreParseSecurityCheckForWorkflow is true). So thats the plus side.

    Right now I have noticed two issues: the one with the broken links is already mentioned here in the blog (hope there is a easy way to add a URL rewrite rule soon as we have a bunch of servers and web applications). The other issues I noticed is that the Nintex Synchronization timer job is failing after the update. Do you guys, which use Nintex, have the same issue? Anyhow, I opened a case with Nintex to get this investigated. I will post an update if I have some usefull information.

    BR Alex

    Reply

    1. Hello,

      if anyone is interested I got an answer from Nintex about the job: “the only purpose of this job is to track the usage of your subscription license. You could disable this job and it wouldn’t affect the services you’re provided”. Thats all I got and I think Nintex is on par with Microsoft, that they don’t care about onPrem stuff anymore. Anyway, I disabled the job ob our test farm and everything still works.

      BR Alex

      Reply

  13. Stefan,
    Have you heard of anyone having issues with 2013 Workflow Manager workflows failing to start due to the July patch in SP2019? I know we need to upgrade to SharePoint Workflow Manager waiting on the migration to SE in the next couple of months.

    Reply

  14. Hello Stefan,

    Thank you for all this information.

    I installed the July 2026 CU and I am also experiencing issues with SharePoint 2010 workflows. Unfortunately, the problem persists even after running the Fix-SystemCodeDom.ps1 script mentioned in your article.

    The error displayed is:

    “Invalid WorkflowInstanceID parameter in the URL.”

    In addition, the ULS logs indicate that the WorkflowInstanceID parameter appears to be URL-encoded multiple times, which causes WrkStat.aspx to fail.

    I was also surprised to notice that the July 2026 CU seems to have been removed from the Microsoft download site.

    Thank you in advance for your feedback.

    Reply

  15. We are also experiencing issues with SharePoint 2010 workflows in our SharePoint Subscription Edition platform. Upon further investigation – we figured out that below entry is missing and we have added this entry in SharePoint Web app Web.Config and then SharePoint 2010 workflows started working.

    But there is another issue – Workflow Status field link in List views is broken. We are seeing the same behavior reported by “Didier”. We will open a Support case with Microsoft.

    Reply

  16. Hello Stefan,

    On a standalone dev server (SP2019), we still facing the issue when the user is trying to publish a Nintex workflow.

    [soap:ServerServer was unable to process request. —> Failed to publish workflow: This feature has been temporarily disabled./]

    These are the entries that I already have (some were added by me manually, some were already there) in a webconfig file of the affected web application:

    [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions.WithKey” TypeName=”” Authorized=”True” /]
    [authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Actions” TypeName=”    ” Authorized=”True” ]
    [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”” Authorized=”True” /]
    [authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”    ” Authorized=”True” /]

    I did IISRESET after updating the webconfig file, but we still have the issue.

    This is from ULS log
    [0x4008 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns4:CallBAPIActivity.MultiOutputInfo xmlns:ns4=”clr-namespace:ERPConnectServices.NintexWorkflowActions;Assembly=ERPConnectServices.NintexWorkflowActions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2f01343040abd943″> <ns7:MultiOutputValueInfo.ValueStorageItems> </ns7:MultiOutputValueInfo.ValueStorageItems> </ns4:CallBAPIActivity.MultiOutputInfo>. If this type is considered legitimate, add TypeName=’CallBAPIActivity.MultiOutputInfo’ to the authorizedTypes section in server config. Ask your farm administrator to add the corresponding assembly to farm property WorkflowTrustedAssemblies. 79b529a2-17ab-4024-ffcd-d5080ea2b0b7/]

    [0x3BD0 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns0:CodeBinaryOperatorExpression.Right xmlns:ns0=”clr-namespace:System.CodeDom;Assembly=System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″> <ns0:CodeBinaryOperatorExpression.Right> <ns0:CodePrimitiveExpression.Value> true </ns0:CodePrimitiveExpression.Value> </ns0:CodeBinaryOperatorExpression.Right> <ns0:CodeBinaryOperatorExpression.Left> <ns0:CodeMethodInvokeExpression.Parameters> <ns0:CodeFieldReferenceExpression.TargetObject> </ns0:CodeFieldReferenceExpression.TargetObject> <ns0:CodeMethodInvokeExpression.Parameters> <ns0:CodePrimitiveExpression.Value> NotEqual </ns0:CodePrimitiveExpression.Value> <ns0:CodeFieldReferenceExpression.TargetObject> </ns0:CodeFieldReferenceExpression.TargetObject> </ns0:CodeMethodInvokeExpression.Parameters> <ns0:CodeMethodInvokeExpression.Method> … b5b329a2-8728-4024-ffcd-de80ac626f44/]

    Reply

  17. After the June CU we updated the webconfig files on each directory, and also used the workaround –
    $farm = Get-SPFarm
    $farm.EnablePreParseSecurityCheckForWorkflow = $false
    $farm.Update()

    Can you confirm we are now safe to set the above to true?

    Reply

    1. Hi Steve,
      if all required types are allow listed as authorizedType in the web.config then you should set this setting to true to ensure that all security fixes are active.
      Cheers,
      Stefan

      Reply

  18. If I run the PS script to update all web configs, prior to installing the Jul patch, what is the likelihood of the patch overwriting the fix.

    Is it worth applying the patch first, then running the script to apply the fix?

    Many thanks

    Reply

    1. Hi Scott,
      which script exactly?
      The one that adds the System.CodeDom as authorizedType?
      This will not be reverted.
      Cheers,
      Stefan

      Reply

      1. That’s the one.

        Thanks Stefan

        Reply

  19. Hi, I’m facing issues in multiline text column where it shows html tags by default. it appeared suddenly. i’ve tried all the solutions but still facing this issue. can you suggest me what to do to solve this?

    Reply

  20. Hi Stefan, this might be a silly question but do i have to run the script on one server in the farm and the web.config changes will be automatically replicated on all servers or the script has to be run on all servers?

    Reply

    1. Hi Rami,
      my script uses the SPWebConfigModification class which will ensure that the change gets applied on all servers in the farm – even new servers added to the farm at a later time.
      Cheers,
      Stefan

      Reply

  21. Not able to solve my problem for “The ULS error is an UnauthorizedAccessException.”, I tried to use your solution as a workaround, but failed. Anyone experienced the same?

    tong

    Reply

  22. Hello Stefan,

    My farm is currently on June 2026. However, 2010 workflows are not working. My question is when I upgrade to July 2026 patch will I be able to view the workflows syntax in sharepoint Designer? Or if I run the June 2026 script to enable workflows will that help run the workflows and able to see syntax in sharepoint designer?

    Reply

    1. Hi Mireya,
      you should be able to run them, if you ensure that all required authorizedTypes are listed in the web.config.
      I’m not sure about the SharePoint Designer aspect as I’m not aware of a problem in this area.
      Cheers,
      Stefan

      Reply

  23. I’ve just completed the SharePoint 2019 single server upgrade to the July 2026 CU, and we are now experiencing issues with the SharePoint 2010 workflows. I located multiple c42q0 entries in the ULS logs, but the configuration file appears to contain the correct reference.

    With only exception of [TypeName=“CodeBinaryOperatorExpression“] which defers from [TypeName=“*“]

    Would you be able to advise on next steps or any additional checks we should perform?

    Thank you,

    Zee

    Reply

    1. Hi Zee,

      did you run the PowerShell script I shared in this blog post?
      It should add the required entry.

      Cheers,
      Stefan

      Reply

      1. Stefan, did not run the PowerShell script, because the webconfig file already had the required entries. We will give it a try on Monday.

        Reply

      2. Stefan, unfortunately we have issue running the script, it gives the following error:

        Get-SPWebApplication : The term ‘Get-SPWebApplication’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
        At line:7 char:11
        + $webApp = Get-SPWebApplication $WebApplicationUrl
        + ~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : ObjectNotFound: (Get-SPWebApplication:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

        Web Application ‘xxx’ not found.
        At line:11 char:5
        + throw “Web Application ‘$WebApplicationUrl’ not found.”
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : OperationStopped: (Web Application…ces’ not found.:String) [], RuntimeException
        + FullyQualifiedErrorId : Web Application ‘xxx’ not found.

        Reply

        1. Hi Zee,

          Don’t worry. You probably did the same as I did first time around, and ran the script using Windows PowerShell ISE.

          If you run the script using SharePoint Management shell, this will work

          Regards

          Scott

          Reply

          1. 👍


          2. Thank you. We were able to get the script working, and the workflow issue has been resolved. 👍


  24. “OWSTIMER.EXE (0x0B6C) 0x2550 SharePoint Foundation Legacy Workflow Infrastructure 4letu High Block the namespace: clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: RootWorkflowActivityWithData”

    We are facing this issue after running the scripts. Should we look into updating owstimer.exe.config ? We have already updated the web.config on all our farm servers

    Reply

    1. Hi Aravind,
      the script only adds the most common missing authorized type which is for System.CodeDom.
      If you check the solution section above you will find the additional authorized type for Microsoft.SharePoint.WorkflowActions
      You can either manually add it to each web.config or update the script to include this to automatically apply it.
      Cheers,
      Stean

      Reply

      1. Inserting these only into web application’s web.config doesn’t help or at least is not enough in all scenarios, it is the owstimer.exe.config (“\Program Files\Common Files\microsoft shared\Web Server Extensions\16\BIN\OWSTIMER.EXE.CONFIG”) you need to add them to. Looks like the PS script only inserts to web app web.config, thus the confusion.

        Reply

        1. Hi Jussi,
          the owstimer.exe.config file should not contain ANY of these authorizedType entries.
          If there is not a single such entry, OWSTIMER will retrieve these entries from the web.config of the related web application.
          In case such entries were added to owstimer.exe.config you need to manually add all entries required.
          The recommended setup is not to have any authorizedType entries in the owstimer.exe.config as it significantly simplifies the administration.
          Cheers,
          Stefan

          Reply

  25. HI Stefan,

    We recently deployed July 2026 patch on our non-prod farm and we are experiencing with 2010 styled workflows issues, they are failing.
    We changed the below setting to false and flows started running fine now:
    $farm = Get-SPFarm
    $farm.EnablePreParseSecurityCheckForWorkflow = $false
    $farm.Update()

    I noticed you published a script and used below:
    Namespace=”System.CodeDom” TypeName=”*”

    I checked my web.config files and noticed some other namespaces as well, do we need add typename=”*” for each one of them.

    I found your below comment in one of your posts above:
    if all required types are allow listed as authorizedType in the web.config then you should set this setting to true to ensure that all security fixes are active.

    All we need is to keep our 2010 styles workflows up and running * set below property to true:
    EnablePreParseSecurityCheckForWorkflow = $false

    Please reply.

    Reply

    1. Hi Aditya,
      in general – no.
      If workflows are still failing after adding the System.CodeDom you need to check the ULS log for the specific types that need to be allow listed.
      Cheers,
      Stefan

      Reply

      1. Flow failed and gave below error:
        Legacy Workflow Infrastructure 4letu High Block the namespace: clr-namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: ApprovalTaskProcess 43fb2ba2-65eb-00ee-cf53-6e12ec7b80ce
        07/29/2026 03:59:23.26 w3wp.exe (0x220C) 0x2988 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns2:ApprovalTaskProcess Subject=”{ActivityBind ID10358,Path=ReturnValue}” Duration=”{ActivityBind ID10361,Path=ReturnValue}” TaskProcessName=”Approval Workflow Task (en-US) Copy 6″ AllowChangeRequest=”True” AllowReassign=”True” Comments=”{ActivityBind ROOT,Path=NotificationMessage}” ExpandGroups=”{ActivityBind ROOT,Path=ExpandGroups}”

        Before running this code, I added below entry in the web.config file:

        Below one was already there:

        Reply

        1. Before running this code, I added below entry in the web.config file:

          Below one was already there:

          Reply

          1. not sure why those code lines are not coming over here:
            I added entry for:
            “System.CodeDom” TypeName=””
            below one was already there:
            Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”            “


          2. Hi Aditya,
            based on the error message the following line needs to be added to the web.config in your scenario:

            Error message:
            … Block the namespace: clr-namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: ApprovalTaskProcess…

            Required Entry:

            <authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Action” TypeName=”*” Authorized=”True” />

            Cheers,
            Stefan


          3. Even after below entry in the web.config files, its failing:


          4. Hi Aditya,
            please replace angular brackets with [] to ensure that your content is preserved
            And of course there might be more authorizedTypes necessary.
            Please check your ULS log for similar entries as the one before.
            Cheers,
            Stefan


          5. I am getting only one entry for Potential malicious code, I am only running approval workflows:
            Block the namespace: clr-namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: ApprovalTaskProcess 2f2d2ca2-159a-00ee-cf53-62d5d70079d6
            07/29/2026 18:31:48.42 w3wp.exe (0x10EC) 0x1FE0 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> </ns0:… 2f2d2ca2-159a-00ee-cf53-62d5d70079d6

            these are the entries in web config:
            [authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Action” TypeName=”*” Authorized=”True” /]

            [authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.CodeDom” TypeName=”*” Authorized=”True” /]

            I performed iisreset on all servers but no luck.


          6. The entry looks good.
            Did you add it to all web.config files under c:\inetpub?


          7. No only for one web application, this site is hosted on this web application where I am performing testing.
            Shall I add on other web applications as well and do the test?


          8. I modified all three web applications’ config files by running that script and attempted another test, its still failing.::(


          9. Hi Aditya,
            I was talking about adding this section into all web.config files:

            <authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.Office.Workflow.Action” TypeName=”*” Authorized=”True” />

            Cheers,
            Stefan


          10. I made sure that this entry is added in all three config files, but flows are still failing.


          11. OK, please check the ULS log again. Additional entries might be required.


          12. Hi Stefan,
            In my ULS log fine, I see c42q0 events after one 4letu and this one I already included in the config files.

            After that I see a lot of c42q8 events which look like below:
            …ersion=16.0.0.0, Culture=neutral, PublicKeyToken=null”> <ns0:RootWorkflowActivityWithData.WorkflowFields> </ns0:RootWorkflowActivityWithData.WorkflowFields> <ns0:OnWorkflowActivated.CorrelationToken> </ns0:OnWorkflowActivated.CorrelationToken> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceDoubleActivity.Value> </ns0:CoerceDoubleActivity.Value> <ns0:CoerceDateTimeActivity.Value> </ns0:CoerceDateTimeActivity.Value> … e38f2ca2-f582-00ee-cf53-6d5fe87d5aad
            07/30/2026 23:16:46.01* w3wp.exe (0x28D8) 0x2250 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High … <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:CoerceStringActivity.Value> </ns0:CoerceStringActivity.Value> <ns0:SetVariableActivity.Variable> </ns0:SetVariableActivity.Variable> <ns0:SetVariableActivity.Value> </ns0:SetVariableActivity.Value> <ns1:SetFieldActivity.Value> </ns1:SetFieldActivity.Value> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:SetVariableActivity.Variable> … e38f2ca2-f582-00ee-cf53-6d5fe87d5aad
            07/30/2026 23:16:46.01* w3wp.exe (0x28D8) 0x2250 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High … </ns0:SetVariableActivity.Variable> <ns0:SetVariableActivity.Value> day(s) </ns0:SetVariableActivity.Value> <IfElseBranchActivity.Condition> </IfElseBranchActivity.Condition> <ns0:SetVariableActivity.Variable> </ns0:SetVariableActivity.Variable> <ns0:SetVariableActivity…. e38f2ca2-f582-00ee-cf53-6d5fe87d5aad
            07/30/2026 23:16:46.01* w3wp.exe (0x28D8) 0x2250 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High …Value> week(s) </ns0:SetVariableActivity.Value> <ns0:SetVariableActivity.Variable> </ns0:SetVariableActivity.Variable> <ns0:SetVariableActivity.Value> month(s) </ns0:SetVariableActivity.Value> </ns0… e38f2ca2-f582-00ee-cf53-6d5fe87d5aad
            07/30/2026 23:16:46.01* w3wp.exe (0x28D8) 0x2250 SharePoint Foundation Legacy Workflow Infrastructure c42q8 High …:SetVariableActivity>

            Do you think any type needs to be included in the config files for


          13. Hi Stefan,
            My issue is resolved, there was a typo in your message which you posted, it should be Actions:
            Required Entry:

            Cheers,
            Stefan

            S was missing in Actions (Namespace=”Microsoft.Office.Workflow.Action” )

            Thanks for your help and answering all my questions.


          14. OK, Great that the issue is finally resolved 😊


          15. Hi Stefan,

            I guess we are struggling with 2010 workflow issues, after 14 days I am running the same workflow and it failed with below error now:

            Legacy Workflow Infrastructure 4letu High Block the namespace: clr-namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null, type: RootWorkflowActivityWithData b93531a2-d5dd-00ee-cf53-69656291a2fb
            08/14/2026 09:50:37.95 OWSTIMER.EXE (0x10E4) 0x2F1C SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: <ns0:RootWorkflowActivityWithData x:Class=”Microsoft.SharePoint.Workflow.ROOT” x:Name=”ROOT” xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/workflow” xmlns:ns1=”clr-namespace:Microsoft.SharePoint.WorkflowActions.WithKey;Assembly=Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” xmlns:ns2=”clr-namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null”

            Below entry is already there in the config files:
            [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True”]

            could you pls suggest.


          16. Hi Aditya,
            can you please ensure that there are no authorizedType entries in the owstimer.exe.config file?
            If there are any such entries, the entries from web.config will be ignored.
            Cheers,
            Stefan


          17. I just checked, below entry is NOT there in the owstimer.exe.config file:
            [authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True”]


  26. sorry pls see the correction for the last line:
    All we need is to keep our 2010 styles workflows up and running & set below property to true:
    EnablePreParseSecurityCheckForWorkflow = $true

    Reply

  27. Does anyone know what triggers the workflow error? I have no ULS entries found with “c42q0” or “Potentially malicious xoml node” after applying the July CU to SP2016 two weeks ago.

    Reply

  28. Hi Stefan

    I am currently testing Jul CU . We see issues starting SP2010 workflows.
    Issue 1
    The form cannot be displayed in the browser because the use of session cookies has been disabled in the current browser settings. In order to load the form, session cookies must be allowed.
    _layouts/15/IniWrkflIP.aspx

    We do have
    I can get the form to load after changing the setting to false.

    I am not sure if this validate ?
    „The July 2026 security update introduced aggressive token transforms and hardened security parameters—specifically a feature called SessionCookieTransformProtectionEnabled—to block remote code execution vulnerabilities (such as CVE-2026-58644). This hardened security validation prevents legacy InfoPath Forms Services from reading or executing session tokens, tricking the browser engine into believing session cookies are disabled.“

    I have deployed https://gist.github.com/stefangossner/a54b1e01eeee42d3831ec5ea7592a87e . Unable to continue until I change httpOnlyCookies = false .

    Reply

    1. The same here, I changed the value to false and now is working. However this is a security validation and I not like to disable it. Are there any other solution?

      Reply

      1. Hi Jose,
        currently the recommendation is to wait for August 2026 CU which is scheduled to be released next week on August 11th.
        Cheers,
        Stefan

        Reply

        1. Thanks for the response Stefan.

          Reply

  30. Hi Stefan,

    I recently noticed that after July patch, Convert Document action in the Nintex workflow (word to pdf) is not working. it throws the following error even though the word automation service is running. i also restarted the service, but the issue persists.

    “Error Message: The service application required to complete this request is not currently available. Try this operation again later. If the problem persists, contact your administrator.”

    We currently have only the following entry in the web config after July patch through PowerShell script. I’m not sure if we need to add any additional entries. Please suggest

    Thank you for your assistance

    Reply

  31. Hi Stefan,

    I recently noticed that after July patch, Convert Document action in the Nintex workflow (word to pdf) is not working. it throws the following error even though the word automation service is running. i also restarted the service, but the issue persists.

    “Error Message: The service application required to complete this request is not currently available. Try this operation again later. If the problem persists, contact your administrator.”

    We currently have only the following entry in the web config after July patch through PowerShell script. I’m not sure if we need to add any additional entries. Please suggest

    ” ”

    Thank you for your assistance

    Reply

    1. Hi Surya,
      for Nintex workflows, please contact Nintex to get assistance.
      Cheers,
      Stefan

      Reply

  32. Hi Stefan,

    We are currently testing script in the solution you discussed. If we use Kerberos and ADFS authentication, how do we run the script per web application? Is running it on the web app URL (with :667) enough, or should we also run using the web application’s alternate mapping URL?

    Thank you in advance for your help.

    Reply

    1. Hi Andre,
      great question! To be honest I’m not sure right now.
      My suggestion would be to run it and check if the entry in the web.config was added in the files for both IIS sites or only for one.
      Cheers,
      Stefan

      Reply

  33. We got workflows working again by modifying web.config as suggested by Stefan, except workflows running in context of owstimer.exe. These are workflows having a pause-activity, which are then resumed and processed in owstimer.exe.

    After setting EnablePreParseSecurityCheckForWorkflow = $false, these workflows work again.

    Reply

  34. It looks like the August-patch removed one of the web.config lines added.
    My 2010-Workflows did not start after the patch and after checking web.config the “” was missing (the other line was still there).

    Tried to rerun the “Fix-SystemCodeDom.ps1” but that responded with “Modification already exists.”. (correctly I assume since the script does not actually go to the file web.config to check)

    Added the row manually to web.config and after that my workflows started to work again.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.