Please review the “Known issues” section of the KB articles for SharePoint September 2022 CU / PU

With September 2022 CU/PU additional steps might be required to prevent unexpected problems after applying the updates.
The following information is included in the KB articles for SharePoint 2013, 2016, 2019 and Subscription Edition:

Known issues in this update

Important: we recommend to evaluate all SharePoint updates in a test environment against all business critical functions and processes before applying in production as SharePoint fixes cannot be uninstalled.
More details in my blog post about SharePoint Patching Best Practices.

21 Comments


  1. Stefan, do the first two issues mainly apply if you have code based custom solutions deployed in your farm or can they also impact out of the box items as well. Thanks in advance for your response.

    -Daniel

    Reply

    1. The main purpose is to address issues with custom solutions. I do not have sufficient information to confirm whether or not there are scenarios which include only out of the box controls/actions that can lead to the problem.

      Reply

      1. Stefan,

        Microsoft did not describe what they were blocking. Microsoft has a many administrators on edge because of this patch and there is a history of poor communications in these patch. I think it would be appropriate for you to look into this.

        The last time this happened another Microsoft Employee created a PowerShell script to fix this. I am not suggesting that he or you do that but without DETAILS of what is being blocked we as administrators cannot be prepared to fix this potential issue. The solution is not to us to spend more monies to open up a ticket with support, the solution is for Microsoft to provide information so we can be prepared to take action.

        Reply

        1. Hi Gene, I just started a 3 week vacation – so I am not able to look into this right now. If you need clarification I would suggest to open a ticket with Microsoft support.

          Reply

  2. Hello Stefan,

    thank you for the Information provided here.

    As we are involved in many Clients with SharePoint 2019 and their Patching Process I like to know:

    Is it planed to provide the recommended Changes ( Web.Config ) in the Future – May be in October 2022?

    Background …
    Some of our Customer are having many Web-Applications … and with this there are lot’s of Config-Files ( Web.Config ). I remember some security Issues where we need to update a large amount of Config-Files “by hand” … One or two months later a PowerShell-Script was added or included.

    With best regards
    Stefan Schwarz

    Reply

    1. There is currently no plan to provide a PowerShell script.

      Reply

    2. Hi Stefan, about the “by hand” part: it is recommended to add the required information using the SPWebConfigModification class to the web.config to ensure that the info is persisted and automatically applied on all servers in the farm.

      Reply

      1. Will the web.config update be included in the October or November CU?

        Reply

        1. The required updates depend on the 3rd party components you are using. These have to be added by each customers individually.

          Reply

          1. So are you saying that if no third party components are used, all three known issues can be ignored?


  3. Hi Stefan, is this KB5017733 only included in the CU, not in the PU, which is provided by windows updates? Best regards, Michael

    Reply

    1. Hi Michael,
      this known issue applies as well to the PU and the CU.
      Cheers,
      Stefan

      Reply

  4. Hello Stefan,

    I dont seem to find the CU September patch for SharePoint 2019 Enterprise. Was this patch released?

    Thank you Stefan

    Reply

  5. After September sharepoint 2016 patch installation we got below error from sharepoint designer workflows 2010
    (-1, -1) Compilation failed. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)))
    all the OOB workflows are failed on start

    Reply

    1. Hi Venkat,
      has the configuration wizard been run after installing the fix?
      If yes, I would recommend to open a ticket with Microsoft support to get this analyzed.
      Cheers,
      Stefan

      Reply

  6. Hi!

    So if I understand this correctly these issue only affect custom solution, e.g. workflows developed in Visual stuidio? I only use SharePoint Designer out-of-the-box functionality in my SharePoint farm so shouldnt be affected right? Im a bit inexperienced as an administrator so any “issue” makes me cautious.

    Thanks in advanced!

    Reply

    1. That is correct. But as always: SharePoint fixes should be evaluated in a test environment before applying in production against business critical functionality as it is impossible to uninstall them.

      Cheers,
      Stefan

      Reply

      1. Alright, thank you for quick response! 🙂

        Reply

  7. Hi, Have installed the patch in a SP2019 with SP2010-Workflows.

    All of sudden, my workflows are not able to retrieve information from UserProfile (Manager + Job Title)

    I don’t really see the straight forward solution in the workaround from MS:

    Some SharePoint 2010 workflow scenarios may be blocked. For more information, see SharePoint 2010 workflows may be blocked by enhanced security policy (KB5017760).

    Reply

Leave a Reply

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