The product group released the January 2025 Cumulative Update for SharePoint Server Subscription Edition.
Monthly SharePoint Server Subscription edition updates are released as a single unified “uber” package containing both the language independent and language dependent fixes. Language independent and language dependent fixes will no longer be released separately. This is similar to the full server packages released for SharePoint 2013.
The KB article for January 2025 CU will be available at the following location in a couple of hours:
- KB 5002676 – January 2025 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for January 2025 CU is available through the following link:
- Download January 2025 Update for SharePoint Server Subscription Edition
This is also a security update!
It is irrelevant which language you pick on the drop down in download center. It will always download the same package.
After installing the fix you need to run the SharePoint 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 Server Subscription Edition January 2025 CU Build Number: 16.0.17928.20356
Important: To minimize the installation time for SharePoint Server Subscription Edition Fixes, please follow the guidance in the following article: Solving the extended install time for SPSE CUs
Related Links:
- Technet: 24H1 Feature Update for SharePoint Server Subscription Edition
- Technet: Updated Product Servicing Policy for SharePoint Server Subscription Edition
- Technet: FAQs for SharePoint Server Subscription Edition product servicing policy
- 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.
- Blog: Solving the extended install time for SPSE CUs
Permalink
Hi Stefan, January 2025 CU doesn’t contain a fix for the trending issue regarding “Date columns showing 30.12.1899”, right? If so, when could we except a fix for that? Many thanks for your outstanding blog. Must have for any “Sharepointer”.
Kind regards, Reto
Permalink
Hi Reto,
that is correct. The fix for the date issue is currently planned to be included in February 2025 CU.
Cheers,
Stefan
Permalink
Hi Stefan,
I have sharepoint server subscription edition updated version (Configuration database version: 16.0.17928.20290)
I have installed Swedish language pack on all servers in a farm. Whenever we are opening the site in swedish (1053) language, we are unable open site contents, site information, Site permissions, site usage, change a look.
Its working and opening when its in english language. Could you please help me to know the route cause for this issue.
Cheers,
Ganesh P.
Permalink
Hi Ganesh,
did you install the most recent CU again after installing the language pack? The language pack you download is the RTM version.
To get it to the same patch level as your farm you have to reapply the most recent CU again after installing it.
Cheers,
Stefan
Permalink
Hi Stefan,
I haven’t installed most recent CU after installing the language pack. I will install it again and confim here please.
Thanks In Advance !
Permalink
Hi Stefan,
As i told, i have installed the Swedish language (1053) pack first. Post language pack installation, applied most recent CU which help me to fix the issue.
Thanks !
Cheers,
Ganesh P.
Permalink
Perfect! Thanks for the update!
Permalink
Hi Stefan,
After installing the January CU we discovered that deploying BCS solutions fails, with the error: DotNetAssembly/WebService system type is not supported.
Do you know if there are any known BCS deploy issues with the latest CU please?
I haven’t done BCS deploy in the last couple of month, so I am unsure if the error is related to the January CU or not.
Also thanks for all the great work with the blog!
Cheers,
Linus
Permalink
Hi Linus,
this is not something new in January CU. These system types were disabled by a security fix released with September 2024 CU.
To further use BDC you need to rearchitecture them by using one of the other save system types.
E.g. you can implementing the logic you used in the DotNetAssembly in an external wcf service and leverage this with the “Wcf” system type.
Cheers,
Stefan
Permalink
Thanks Stefan, we had missed that change back in September.
Cheers,
Linus
Permalink
Hi Stefan,
The links to KB 5002676 and January 2025 CU are both downloading the same package. Is that corrrect?
Cheers
Mark
Permalink
Hi Mark,
KB 5002676 includes a link to the same fix package if that is what you mean.
For convenience reasons I add the direct link to my blog posts.
Cheers,
Stefan
Permalink
Hi Stefan,
After installing the January CU we could see Client ID Client Secret, generation option is “hidden” from _layouts/15/AppRegNew.aspx page. is that a new update?. Could you please share more details.
Permalink
there is a typo, after Dec CU, KB5002658 and not Jan
Permalink
That seems to be an intentional design. Client secret and ID were hidden from the form, however if you click on „Submit“ they are shown (and better note them down, since they are gone on browsing away). That’s the only time we can have them and we can use those values. Now they are auto-generated by the system instead of being able to provide values for them.
Permalink
Hello Stephen.
I’m facing an issue affecting a SharePoint SE farm where I’ve installed the December 2024 and January 2025 cumulative updates.
Every time we try to access a plain site collection, we got an error message
The given assembly name or codebase, ‘C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Project.Server.PWA\v4.0_16.0.0.0__71e9bce111e9429c\Microsoft.Office.Project.Server.PWA.dll’, was invalid.
This prevents SharePoint from proceeding and displaying the site.
Are you aware of any problem like this? What would you suggest?
Thank you.