Windows 8.1 and Windows Server 2012 R2

Find information on known issues for Windows 8.1 and Windows Server 2012 R2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Windows 10, version 2004 is now available Windows 10, version 2004 is now available
Find out how to get the update >
What’s new for IT pros What’s new for IT pros
Explore the latest features and and servicing innovations in Windows 10 >
Wondering how to deploy feature updates remotely? Wondering how to deploy feature updates remotely?
Get tips and best practices >

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
Outlook closes unexpectedly or you might receive an error when attempting to open
An example of an error you might receive is, "Outlook couldn't start last time."

See details >
July 14, 2020
KB4565541
Resolved
July 15, 2020
03:43 PM PT
Japanese IME doesn't show the new Japanese Era name as a text input option
With previous dictionary updates installed, the Japanese IME doesn't show the new Japanese Era name as an input option.

See details >
April 25, 2019
KB4493443
Resolved
July 14, 2020
10:19 AM PT
TLS connections might fail or timeout
Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption.

See details >
October 08, 2019
KB4520005
Resolved External
July 14, 2020
10:19 AM PT
Certain operations performed on a Cluster Shared Volume may fail
Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

See details >
January 08, 2019
KB4480963
Mitigated
June 11, 2020
02:06 PM PT
You might encounter issues with KB4502496
You might encounter issues trying to install or after installing KB4502496

See details >
February 11, 2020
KB4502496
Mitigated
February 15, 2020
01:22 AM PT

Issue details

July 2020

DetailsOriginating updateStatusHistory
Outlook closes unexpectedly or you might receive an error when attempting to open
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.

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
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.

Back to top
July 14, 2020
KB4565541
Resolved
Resolved:
July 15, 2020
03:43 PM PT

Opened:
July 15, 2020
03:22 PM PT

February 2020

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

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
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.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4502496 and select the Uninstall button.
  4. Restart your device.
 
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.

Back to top
February 11, 2020
KB4502496
Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT

November 2019

DetailsOriginating updateStatusHistory
TLS connections might fail or timeout
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:
  • "The request was aborted: Could not create SSL/TLS secure Channel"
  • SCHANNEL event 36887 is logged in the System event log with the description, "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.​"
Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

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.

Back to top
October 08, 2019
KB4520005
Resolved External
Last updated:
July 14, 2020
10:19 AM PT

Opened:
November 05, 2019
03:36 PM PT

May 2019

DetailsOriginating updateStatusHistory
Japanese IME doesn't show the new Japanese Era name as a text input option
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.

Affected platforms:
  • Client: Windows 8.1
  • Server: Windows Server 2012 R2; Windows Server 2012
Workaround:
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.
  • Update for Japanese Microsoft IME Standard Dictionary (15.0.2013)
  • Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.2013)
  • Update for Japanese Microsoft IME Standard Dictionary (15.0.1215)
  • Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1215)
  • Update for Japanese Microsoft IME Standard Dictionary (15.0.1080)
  • Update for Japanese Microsoft IME Standard Extended Dictionary (15.0.1080)

Back to top
April 25, 2019
KB4493443
Resolved
Resolved:
July 14, 2020
10:19 AM PT

Opened:
May 15, 2019
05:53 PM PT

January 2019

DetailsOriginating updateStatusHistory
Certain operations performed on a Cluster Shared Volume may fail
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.

Affected platforms:
  • Client: Windows 8.1; Windows 7 SP1
  • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Workaround: Do one of the following:
  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top
January 08, 2019
KB4480963
Mitigated
Last updated:
June 11, 2020
02:06 PM PT

Opened:
January 08, 2019
10:00 AM PT