Windows Server 2012

Find information on known issues for Windows Server 2012. 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
    Windows Servers domain controllers might restart unexpectedly
    After installing updates released January 11, 2022, DCs might restart unexpectedly.
    KB5009586
    2022-01-11
    Resolved
    KB5010797
    2022-01-17
    14:00 PT
    Virtual machines (VMs) in Hyper-V might fail to start
    VMs hosted on devices using UEFI and Hyper-V might fail to start.
    KB5009586
    2022-01-11
    Resolved
    KB5010797
    2022-01-17
    14:00 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).
    KB4480975
    2019-01-08
    Mitigated
    2020-06-11
    14:06 PT

    Issue details

    January 2022

    Windows Servers domain controllers might restart unexpectedly

    StatusOriginating updateHistory
    Resolved KB5010797 KB5009586
    2022-01-11
    Resolved: 2022-01-17, 14:00 PT
    Opened: 2022-01-13, 14:14 PT
    After installing KB5009586 on domain controllers (DCs), affected versions of Windows Servers might restart unexpectedly. Note: On Windows Server 2016 and later, you are more likely to be affected when DCs are using Shadow Principals in Enhanced Security Admin Environment (ESAE) or environments with Privileged Identity Management (PIM).

    Resolution: This issue was resolved in the out-of-band update KB5010797. To get the standalone package for KB5010797, 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 KB5010797 is not available from Windows Update and will not install automatically.

    Affected platforms:
    • Client: None
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    Virtual machines (VMs) in Hyper-V might fail to start

    StatusOriginating updateHistory
    Resolved KB5010797 KB5009586
    2022-01-11
    Resolved: 2022-01-17, 14:00 PT
    Opened: 2022-01-13, 11:18 PT
    After installing KB5009586 on devices using UEFI, virtual machines (VMs) in Hyper-V might fail to start.

    Resolution: This issue was resolved in the out-of-band update KB5010797. To get the standalone package for KB5010797, 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 KB5010797 is not available from Windows Update and will not install automatically.

    Affected platforms:
    • Client: Windows 8.1
    • Server: Windows Server 2012 R2; Windows Server 2012

    January 2019

    Certain operations performed on a Cluster Shared Volume may fail

    StatusOriginating updateHistory
    Mitigated KB4480975
    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.