Windows 8.1 and Windows Server 2012 R2

Microsoft Outlook might close unexpectedly or you might receive an error when attempting to open the app. An example of an error you might receive is, "Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?" You might also see an event in the Event Viewer, as listed in the article linked below.

Workaround: As an alternative, on your Windows 10 device you can use the Office365 on the web (OWA), also known as webmail. Outlook mobile is also unaffected. There is no workaround for this issue for the Outlook app on Windows 10 until the resolution is deployed to your device. We do not recommend using the command to revert to an earlier version.

Resolution: This Outlook issue has been resolved and will be deployed automatically to your device. This issue was not related to any update for Windows and no update for Windows is needed. We expect this issue to be completely resolved for all affected users by July 15, 2020 at 3:30 PM PST (10:30 PM UTC). You may also need to attempt to open Outlook a few times before it will be fully refreshed and open as expected. For more information, please see the support article, Active Investigation into Outlook Crashing on Launch and this twitter thread.

You might encounter issues trying to install or after installing KB4502496.

Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.

 

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:

Resolution: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489.

If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.

If you see any of the previous dictionary updates listed below, uninstall it from Programs and features > Uninstall or change a program. New words that were in previous dictionary updates are also in this update.

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Workaround: Do one of the following:

Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.