Trending Issue: /_layouts/15/viewlsts.aspx shows as blank page in SP2019 after installing September PU

We received a couple of cases from customers who reported that navigating to the “Site Contents” page shows up as a blank page.
In this situation you will find an entry similar to the following:

w3wp.exe (0x1xxx) SharePoint Foundation Web Controls cfpx8 Unexpected Error encountered when creating uri from baseUrl /_layouts/15/next/odspnext/.

This error will occur if the language dependent and language independent patch level is different for the specific language.

Reasons this can happen:

  • Only the September 2021 security fix (KB 5002018) was installed but not the language dependent fix (KB 5002019) which does not include new security fixes.
  • A language pack was installed after September 2021 CU was installed without reapplying the language dependent fix.
  • The configuration wizard was not executed after applying the language dependent fixes

To resolve the issue ensure to apply the language dependent fix from September 2021 CU and run the SharePoint configuration wizard.


  1. Thanks a lot, it worked. You saved us.

    At the customer farm the update (KB 5002018) was installed automatically because they accidentally did not exclude the SharePoint updates from the WSUS.


  2. woow.. it works!
    thanks Stefan


  3. I install Fresh Sharepoint 2019 with Nov 2022 update and i am getting the same error. Any advice stefan on it p


    1. Hi Sachin,
      did you install both patches? Language independent and dependent (5002294, 5002295)?
      And did you run the config wizard after installing these two patches?


  4. My farm has January Patches. When i tried to join a new Web Front End , I am getting a blank site. Do i need to install (5002294, 5002295) . I thought the most recent patches will cover it.


  5. I’m having the same issue but I always make sure that both sts and wssloc updates are installed. I verified this and confirmed that I have not missed any. I just installed the June 2023 updates and the issue is still present.


    1. Hi Guillermo,
      if the issue is not caused by an inconsistent patch level, my recommendation would be to open a support case with Microsoft to get your specific issue investigated.


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.