Merge pull request #2277 from microsoft/Batre-MSFT-patch-3

Update Emerging-Issues.md

docs/Emerging-Issues.md

@@ -3,12 +3,17 @@ hide:
   - toc
 ---
 
+<!-- Mark words okay for spell check here
+#cspell:words MSIL
+ -->
+
 # Emerging Issues for Exchange On-Premises
 
 This page lists emerging issues for Exchange On-Premises deployments, possible root cause and solution/workaround to fix the issues. The page will be consistently updated with new issues found and reflect current status of the issues mentioned.
 
 |**Updated on**|**Update causing the issue**|**Issue**|**Workaround/Solution**|
 |-|-|-|-|
+| 1/29/2025 | [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) | You may see following error when installing [November 2024 V2 Exchange Security Update](https://support.microsoft.com/topic/description-of-version-2-of-the-security-update-for-microsoft-exchange-server-2019-and-2016-november-27-2024-kb5049233-e807f65d-da39-48a9-9a7e-69612cac8077): <BR><BR> Error 1935. An error occurred during the installation of assembly 'Microsoft.Exchange.Data.Common,version="15.1.2503.00",fileVersion="15.1.2507.44",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL"'. For more information, refer to Microsoft Help and Support. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, component: {B79F9EB4-6D81-48F3-BC2D-3A0A83C30742} | Please follow the workaround provided on [this KB article](https://aka.ms/NovSUKB) |
 | 11/29/2024 | [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) | Time zone exception may be reported in event viewer, after installing the [November Exchange Security Update for Exchange 2016 & Exchange 2019 V2](https://support.microsoft.com/help/5049233) <BR><BR> Event log entries are generated if Exchange Server fails to process calendar information, such as: <BR><BR> w3wp\#MSExchangeOWAAppPool, M.Exchange.Net , M.E.E.ExIanaTimeZoneProvider+Cache.AddTimeZone, M.E.ExchangeSystem.InvalidTimeZoneException <BR>OR<BR>Microsoft.Exchange.ExchangeSystem.InvalidTimeZoneException: Time zone id already exists | Please follow the workaround provided on [this KB article](https://support.microsoft.com/en-us/topic/time-zone-exception-occurs-after-installing-exchange-server-november-2024-su-version-1-or-version-2-851b3005-6d39-49a9-a6b5-5b4bb42a606f) |
 | 11/27/2024 | [November Exchange Security Update for Exchange 2016 & Exchange 2019](https://support.microsoft.com/help/5044062) | Exchange Transport Rules may stop working after applying the [November Exchange Security Update for Exchange 2016 & Exchange 2019](https://support.microsoft.com/help/5044062)  | Please install the re-released [November 2024 Exchange security update](https://techcommunity.microsoft.com/blog/exchange/re-release-of-november-2024-exchange-server-security-update-packages/4341892) |
 | 9/11/2024 |  [August 2024 update for Windows](https://support.microsoft.com/kb/5041578) | After installing the [August 2024 update for Windows](https://support.microsoft.com/kb/5041578) <BR><BR> 1) Microsoft Exchange Transport service may start crashing <BR> 2) Microsoft Filtering Management Service may not start or start with long delay | **Update on 9/11/2024** <BR><BR> Install [Windows Update for September 2024](https://support.microsoft.com/topic/september-10-2024-kb5043050-os-build-17763-6293-66e9809a-1838-4474-a6a7-90d64f042f00) or later <BR><BR> **Old information**<BR> <span style="text-decoration: line-through;">Please follow steps in [this KB](https://learn.microsoft.com/windows/release-health/status-windows-10-1809-and-windows-server-2019#3375msgdesc)</span> |