The product group released the July 2024 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for July 2024 CU will be available at the following Location in a couple of hours:
- KB 5002615 – July 2024 Update for SharePoint Server 2019 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002538 from April 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for July 2024 CU are available through the following links:
- Download July 2024 Update for SharePoint Server 2019 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002538 from April 2024 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2019 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint 2019 July 2024 CU Build Number:
Language independent fix: 16.0.10412.20001
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching Best Practices
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hello,
the command Copy-SPSideBySideFiles takes hours.
My previous CU installed is May 2024.
Is it normal ?
Thanks
Permalink
Hi Alexandre,
no this should be quite fast.
It only copies the js/css/html files from the layouts directory into a version directory.
Is this the first time that you are enabling sidebyside functionality?
Because after you enabled it there is usually no need to use this command except when installing/updating 3rd party components. PSConfig will take care of this.
Cheers,
Stefan
Permalink
Hi Stefan,
thanks for your reply, I will remove it from our script since we already executed it in the past.
Have a nice day
Permalink
Hello Stefan,
I am trying to reach the Download pages for SP2019 Updates …
The link to the Download-Center … Security Update …
http://www.microsoft.com/download/details.aspx?familyid=a981cd4e-a4a7-4b75-85c3-6708c75ec97e
Also the Link to the Download-Center … Language Pack April …
https://www.microsoft.com/download/details.aspx?familyid=43e1b8bd-31bf-4b1b-85f5-4557ff412e9f
… are going to the following message:
Thank you and with best regards
Stefan Schwarz
Permalink
Same with SP SE
Permalink
I get that message as well for the 2016 updates. Seems to be a general issue for at least the last 6hrs.
Permalink
Issue is still in place:
$set_redirect(‘https://www.microsoft.com/library/errorpages/smarterror.aspx?correlationId=$(cvToken)’)
Internal Server Error.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Request Correlation ID: CASMicrosoftCV6519b0a9.0.1
$set_redirect(‘https://www.microsoft.com/library/errorpages/smarterror.aspx?correlationId=$(cvToken)’)
Permalink
There is a currently an outage which is being worked on.
It should be back online soon hopefully.
Permalink
Good Morning.
Issue is fixed … Download is working again.
Thank you and best regards
Stefan
Permalink
Download links not working:
Internal Server Error.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Permalink
Hello!
We noticed this change in our web.config after CU was updated:
SafeControl Assembly=”Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.ApplicationPages” TypeName=”SPThemes” Safe=”True” AllowRemoteDesigner=”False” SafeAgainstScript=”False”
->
SafeControl Assembly=”Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.ApplicationPages” TypeName=”SPThemes” Safe=”False” AllowRemoteDesigner=”False” SafeAgainstScript=”False”
So this safe control is no longer considered safe? It broke some of our functionalities but we were able to restore the situation. Folks, remember to make those web.config backups before updating 🙂
Permalink
Hi Taavi,
this is a known issue which is currently being investigated.
Cheers,
Stefan
Permalink
I how now documented the issue here:
https://blog.stefan-gossner.com/2024/07/22/trending-issue-certain-powershell-operations-failing-after-installing-july-2024-cu-for-sharepoint-2016-2019/
Permalink
Hello!
We noticed this change in our web.config after CU was updated:
SafeControl Assembly=”Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.ApplicationPages” TypeName=”SPThemes” Safe=”True” AllowRemoteDesigner=”False” SafeAgainstScript=”False”
->
SafeControl Assembly=”Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.ApplicationPages” TypeName=”SPThemes” Safe=”False” AllowRemoteDesigner=”False” SafeAgainstScript=”False”
So this safe control is no longer considered safe? It broke some of our functionalities but we were able to restore the situation. Folks, remember to make those web.config backups before updating 🙂
Permalink
July CU update keep failing with error “The update cannot be installed due to a previous update was installed through a modified installation source.” Please advice.
Permalink
Hi Sumanta,
I have never seens this error before. Please open a ticket with Microsoft Support to get this analyzed.
Cheers,
Stefan
Permalink
Hi Stefan,
Post a successful update with this CU we seem to have a regression issue where the Site Contents page is once again empty unless you switch to classic view. Subsites tab displays fine in modern view.
I checked one of our web config files and ours is also set to false as mentioned by Taavi.
Permalink
Hi Allison,
if you ran the configuration wizard after installing the fix I would suggest to open a case with Microsoft support to get this analyzed.
Cheers,
Stefan
Permalink
Hi Stefan,
Since the installation I have more and more users complaining about issue with OOS, they can’t access Office documents with this feature, in ULS OOS say Access Denied but the user has the good permission.
By deleting the user from the site collection it seems to fix it.
Are you aware about this kind of issue with the CU of July ?
Thanks