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.


    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
    Microsoft Installer might have issues updating or repairing apps
    Affected apps might fail to open after an update or repair has been attempted.
    KB5007247
    2021-11-09
    Confirmed
    2021-11-18
    12:12 PT
    Authentication might fail on DCs with certain Kerberos delegation scenarios
    Clients and servers using Single Sign On via Kerberos Tickets acquired via S4u2self might be unable to authenticate.
    KB5007247
    2021-11-09
    Resolved
    KB5008603
    2021-11-14
    10:00 PT
    Custom printing properties might not be correctly provided to print server clients
    This issue will not cause printing operations to fail, but clients might print with default settings only
    KB5005613
    2021-09-14
    Resolved
    KB5007247
    2021-11-09
    10:00 PT
    Installation of printers might fail when attempted over some network connections
    This issue has been observed in devices which access printers via a print server using HTTP connections
    KB5005613
    2021-09-14
    Resolved
    KB5006714
    2021-10-12
    10:00 PT
    UI elements and drawing within some apps may not work as expected
    Some apps using GDI+ might have issues with scaling within the app or when used on high DPI or resolution displays.
    KB5006714
    2021-10-12
    Resolved
    KB5007247
    2021-11-09
    10:00 PT
    Connections to printers shared via print server might encounter errors
    This issue is observed when print clients try to connect to a remote printer shared on a print server
    KB5006714
    2021-10-12
    Mitigated
    2021-10-29
    16:01 PT
    Connections to printers shared via print server might encounter errors
    This issue is observed when print clients try to connect to a remote printer shared on a print server
    KB5006714
    2021-10-12
    Mitigated
    2021-10-29
    16:01 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).
    KB4480963
    2019-01-08
    Mitigated
    2020-06-11
    14:06 PT

    Issue details

    November 2021

    Microsoft Installer might have issues updating or repairing apps

    StatusOriginating updateHistory
    Confirmed KB5007247
    2021-11-09
    Last updated: 2021-11-18, 12:12 PT
    Opened: 2021-11-18, 10:34 PT
    After installing KB5007247 or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.

    Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

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

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Authentication might fail on DCs with certain Kerberos delegation scenarios

    StatusOriginating updateHistory
    Resolved KB5008603 KB5007247
    2021-11-09
    Resolved: 2021-11-14, 10:00 PT
    Opened: 2021-11-10, 19:09 PT
    After installing the November security updates, released November 9, 2021 on your Domain Controllers (DC) running a Windows Server versions listed below in affected platforms, you might have authentication failures on servers relating to Kerberos Tickets acquired via S4u2self. The authentication failures are a result of Kerberos Tickets acquired via S4u2self and used as evidence tickets for protocol transition to delegate to backend services which fail signature validation. Kerberos authentication will fail on Kerberos delegation scenarios that rely on the front-end service to retrieve a Kerberos ticket on behalf of a user to access a backend service. Important Kerberos delegation scenarios where a Kerberos client provides the front-end service with an evidence ticket are not impacted. Pure Azure Active Directory environments are not impacted by this issue. 

    End users in your environment might be unable to sign into services or applications using Single Sign On (SSO) using Active Directory on-premises or in a hybrid Azure Active Directory environment. Updates installed on the client Windows devices will not cause or affect this issue.

    Affected environments might be using the following:
    • Azure Active Directory (AAD) Application Proxy Integrated Windows Authentication (IWA) using Kerberos Constrained Delegation (KCD)
    • Web Application Proxy (WAP) Integrated Windows Authentication (IWA) Single Sign On (SSO)
    • Active Directory Federated Services (ADFS)
    • Microsoft SQL Server
    • Internet Information Services (IIS) using Integrated Windows Authentication (IWA)
    • Intermediate devices including Load Balancers performing delegated authentication
    You might receive one or more of the following errors when encountering this issue:
    • Event Viewer might show Microsoft-Windows-Kerberos-Key-Distribution-Center event 18 logged in the System event log
    • Error 0x8009030c with text Web Application Proxy encountered an unexpected is logged in the Azure AD Application Proxy event log in Microsoft-AAD Application Proxy Connector event 12027
    • Network traces contain the following signature similar to the following:
      • 7281 24:44 (644) 10.11.2.12 <app server hostname>.contoso.com KerberosV5 KerberosV5:TGS Request Realm: CONTOSO.COM Sname: http/xxxxx-xxx.contoso.com
      • 7282 7290 (0) <hostname>. CONTOSO.COM <IP address of the application server making the TGS request>
    Resolution: This issue was resolved in the out-of-band update KB5008603 released November 14, 2021. To get the standalone package for KB5008603, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5008603 is not available from Windows Update and will not install automatically.

    Affected platforms:
    • Server: Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    UI elements and drawing within some apps may not work as expected

    StatusOriginating updateHistory
    Resolved KB5007247 KB5006714
    2021-10-12
    Resolved: 2021-11-09, 10:00 PT
    Opened: 2021-11-05, 17:58 PT
    After installing KB5006714 or a later update, certain apps might have unexpected results when rendering some user interface elements or when drawing within the app. You might encounter this issue with apps that use GDI+ and set a zero (0) width pen object on displays with high dots per inch (DPI) or resolution, or if the app is using scaling.

    Resolution: This issue was resolved in KB5007247.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    October 2021

    Custom printing properties might not be correctly provided to print server clients

    StatusOriginating updateHistory
    Resolved KB5007247 KB5005613
    2021-09-14
    Resolved: 2021-11-09, 10:00 PT
    Opened: 2021-10-13, 12:29 PT
    After installing KB5005613 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only.

    This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005613 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected.

    Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings.

    Resolution: This issue has been resolved in KB5007247.

    Affected platforms:
    • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

    Installation of printers might fail when attempted over some network connections

    StatusOriginating updateHistory
    Resolved KB5006714 KB5005613
    2021-09-14
    Resolved: 2021-10-12, 10:00 PT
    Opened: 2021-10-13, 12:34 PT
    After installing KB5005613, devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. Devices which had connected to and installed the printer prior to the installation of KB5005613 are unaffected and operations to that printer will succeed as usual.

    This issue has been observed in devices which access printers via a print server using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download.

    Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Only the automatic download and installation processes are impacted by this issue.

    Resolution: This issue was resolved in  KB5006714.

    Affected platforms:
    • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

    Connections to printers shared via print server might encounter errors

    StatusOriginating updateHistory
    Mitigated KB5006714
    2021-10-12
    Last updated: 2021-10-29, 16:01 PT
    Opened: 2021-10-29, 11:15 PT
    After installation of KB5006714, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
    • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
    • 0x0000007c (ERROR_INVALID_LEVEL)
    • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
    Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
     
    Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
     
    • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed KB5006714.
    Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
    • Default start port: 49152
    • Default end port: 65535
    • Port Range: 16384 ports
    Please refer to these articles for further guidance:
    You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
     
    Next steps: Microsoft is working on a resolution that will allow print clients to establish RPC packet privacy connections to print servers using RPC over SMB. We will provide an update once more information is available.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Connections to printers shared via print server might encounter errors

    StatusOriginating updateHistory
    Mitigated KB5006714
    2021-10-12
    Last updated: 2021-10-29, 16:01 PT
    Opened: 2021-10-29, 11:15 PT
    After installation of KB5006714, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
    • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
    • 0x0000007c (ERROR_INVALID_LEVEL)
    • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
    Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
     
    Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
     
    • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed KB5006714.
    Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
    • Default start port: 49152
    • Default end port: 65535
    • Port Range: 16384 ports
    Please refer to these articles for further guidance:
    You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
     
    Next steps: Microsoft is working on a resolution that will allow print clients to establish RPC packet privacy connections to print servers using RPC over SMB. We will provide an update once more information is available.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    January 2019

    Certain operations performed on a Cluster Shared Volume may fail

    StatusOriginating updateHistory
    Mitigated KB4480963
    2019-01-08
    Last updated: 2020-06-11, 14:06 PT
    Opened: 2019-01-08, 10:00 PT
    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.