Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
SUs are available in a self-extracting auto-elev...
Updated May 08, 2023
Version 22.0
Blog Post
Nino_Bilic
Microsoft
MicrosoftP_R_S This was a "known issue" with January 2023 SU. Only January 2023 SU actually increased that build number (before that, only CU setup would do that, and that caused an issue that we mentioned in this KB article). SUs actually did not change this version number before and then January SU did. Long story short is: unless you are re-running full setup (/recover setup or removal of Exchange) there will be no issues. We are still exploring options on how to address this version change long-term. Right now, you do not need to do anything but yes - we are aware of this and what you are seeing is expected (SUs outside of this one particular SU - Jan 2023 do not change this version number).
SuperCocoLoco Outlook 2010 is out of support (no security updates). Please update ASAP.
Dennisdsmolinski The workaround from Fab will simply keep "working around" until you are ready to remove it once you updated all servers to March 2023 SU. There is no problem with running in this state during the update process. Once all servers are updated to March SU, remove the workaround and that's that.