SharePoint security fixes released with October 2022 PU and offered through Microsoft Update

Below are the security fixes for the SharePoint OnPrem versions released this month.

SharePoint Foundation security fixes also have to be applied on SharePoint Server installations.
SharePoint Server security fixes also have to be applied on Project Server installations.

SharePoint 2013 Suite:

SharePoint Server 2016:

SharePoint Server 2019:

SharePoint Server Subscription Edition:

Office Online Server:

  • None
See the Security Update Guide below for more details about the relevant fixes:

More information:

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.


  1. We are having Workflow issues, SPD and Nintex after install of KB5002284


  2. October update seems to have a problem upgrading Subscription Settings database.
    Looks like it goes ok in the psconfig upgrade log but Central Admin complains it needs upgrade.
    Issue noticed in both SP2013 and SP2016.
    Anyone else with the same issue?


    1. Hi Andreas. I can confirm the problem with SP2019 too.


      1. Hi,
        Make sure your farm account has db_owner on the database, then it should work.
        That was my issue anyways.


    2. The config wizard gui was failing for me with permission errors to the SubscriptionSettings database. Running the command line completed without error: PSCONFIG.EXE -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent -install -cmd upgrade -inplace b2b -force -wait


  3. May not be directly related to this patch, but we are having issues running “install-spapplicationcontent” now it fails with an exception of trying to access “c:\windows\system32\%systemdrive%\inetpub\wwwroot\web.config” which (‘c:\inetpub\wwwroot\web.config’ doesn’t exist.

    It’s like it’s failing to resolve the environment variable or something?


    1. Hi Kevin,
      This looks weird as %systemdrive% should be “C:”. And this does not make any sense in the middle of a path.
      I would suggest to open a support case with Microsoft on this.


      1. I found the issue. The previous admin extended the Default Web Site (iis default port 80 site) and this has systemdrive in its path to the wwwroot. The path in the web application iis settings was all wrong because it couldn’t parse the environment variable while creating its definition. Removing the sharepoint extension and deleting the web app definition without deleting the iis site (as iis site id 1 default web site is required to exist) resolved it.


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.