Today we are re-releasing the November 2024 SUs for Exchange Server. The original release of these SUs (released on 11/12/2024) introduced an issue with Exchange Server transport rules stopping after...
Updated Jan 28, 2025
Version 11.0
Blog Post
i have also the assembly Problem when Installing Nov SUv2 on Exchange 2019 CU14 and Server 2019.
January Updates are installed. German Windows OS.
https://support.microsoft.com/en-us/topic/file-version-error-when-you-try-to-install-exchange-server-november-2024-su-a650da30-f8fb-469d-a449-47396cab0a15
Workaround 1 and 2 do not work.
Can you help? Is this issue still open Microsoft?
CU15 was released and includes November's SU:
"CU15 contains all the security changes included in the November 2024 SU v2 (re-released package), and also includes a fix for the known time zone issue in the November 2024 SU." (Released: 2025 H1 Cumulative Update for Exchange Server | Microsoft Community Hub)
Would you consider attempting to upgrade to CU15 instead?
Hi, thanks for Feedback. This could help but the process to install a CU does take more time for us... so this is no fast solution for us...
That doesn't help those of us on Exchange 2016.
I understand. However, the op mentioned Exchange 2019 CU14 specifically.
I'm not sure what the status of Nov24SUv2 is for 2016. I believe Microsoft mentioned that not rebooting before the upgrade could cause the issue, but users have posted mixed results.
If the workarounds described at File version error when you try to install Exchange Server November 2024 SU - Microsoft Support still aren't helping, I'd open a support ticket with Microsoft; but, even if they're successful in resolving the issue, that would only bring you up to October at the latest.
This is a little drastic (but would make a future transition easier), but if you have SA for Server 2016 (and CALs), perhaps perform a license upgrade and legacy migration to 2019 CU15 prior to October?
If you don't have SA, I assume Microsoft would suggest you discuss upgrade options with a licensing specialist. I'm not sure if any pricing details for SE have been released yet, but an alternate route (which I am taking) is to upgrade licenses to 2019 now WITH SA for as long a term as you can (I did 3 years and believe I have at least one 3-year SA renewal).
I have already given them feedback on here that rebooting our server doesn't help. We have v1 of the November SU installed and currently have no plans to install v2 unless I specifically hear that they have fixed the problem. I was hoping that the Feb OS CU might fix it, but haven't tested that yet.
What I am really worried about at this point is if they put out a new SU that automatically shows up in Microsoft update that breaks everything again.
We already have plans to migrate to M365 before the Oct deadline, but that is going to take us months to do. Doesn't Exchange 2019 EOL in Oct as well?
