Windows Server 2012

  • Article

Find information on known issues and the servicing status for Windows Server 2012. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates.

    Known issues

    See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

    SummaryOriginating updateStatusLast updated
    Printer names and icons might be changed and HP Smart app automatically installs
    Devices which do not have access to the Microsoft Store are not expected to be affected by this issue.
    		Investigating
    		2023-12-07
    13:41 PT
    Devices with locale set to Croatia might not utilize the expected currency
    This can affect applications which retrieve the device's currency for purchases or other transactions
    		Confirmed
    		2023-10-31
    10:06 PT
    Certain apps or devices might be unable to create Netlogon secure channel connections
    Scenarios which rely on synthetic RODC machine accounts might fail if they do not have a linked KRBTGT account.
    		 KB5009586
    2022-01-11    		Investigating
    		2022-02-24
    17:41 PT
    Apps that acquire or set Active Directory Forest Trust Information might have issues
    Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, or you might receive an error.
    		KB5009586
    2022-01-11    		Mitigated
    		2022-02-07
    15:36 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

    December 2023

    Printer names and icons might be changed and HP Smart app automatically installs

    StatusOriginating updateHistory
    Investigating
    		Last updated: 2023-12-07, 13:41 PT
    Opened: 2023-12-04, 18:46 PT

    Some issues related to printer configurations are being observed on Windows devices which have access to the Microsoft Store. Microsoft is investigating this issue and coordinating with partners on a solution.

    Symptoms can include the following:

    1. ​Some Windows 10 and Windows 11 devices are installing the HP Smart app.
    2. ​Printers are renamed as HP printers regardless of their manufacturer. Most are being named as the HP LaserJet M101-M106 model. Printer icons might also be changed.
    3. ​Double clicking on a printer displays the on-screen error "No tasks are available for this page".

    Note: Our investigations indicate that this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.

    As the symptoms are related to the automatic installation of the HP Smart app, Windows devices which do not have access to the Microsoft Store are not expected to be affected by this issue.

    Next steps: We are investigating this issue and will provide an update when more information is available. If you need support for this issue, go to https://support.microsoft.com/contactus, and select Windows.

    Affected platforms:

    • ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
    • ​Server: Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    February 2023

    Devices with locale set to Croatia might not utilize the expected currency

    StatusOriginating updateHistory
    Confirmed
    		Last updated: 2023-10-31, 10:06 PT
    Opened: 2023-02-23, 13:22 PT

    The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device's currency for purchases or other transactions. 

    Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.

    Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.

    1. ​Open the "Windows Region" settings. This can be done in one of the following ways:
      1. ​Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
      2. ​On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
    2. ​In the Region settings, choose one of the 2 locales for Croatia:
      1. ​Croatian (Bosnia & Herzegovina)
      2. ​Croatian (Croatia)
    3. ​In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
    4. ​Change the currency symbol from "KN" to Euro, "€"

    Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.

    Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.

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

    Affected platforms:

    • ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    February 2022

    Certain apps or devices might be unable to create Netlogon secure channel connections

    StatusOriginating updateHistory
    Investigating KB5009586
    2022-01-11    		Last updated: 2022-02-24, 17:41 PT
    Opened: 2022-02-24, 17:25 PT

    After installing KB5009586 or any updates released January 11, 2022 and later on your domain controllers, scenarios which rely on Read-only domain controllers (RODCs) or synthetic RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must have a linked and compliant KRBTGT account to successfully establish a secure channel. Affected applications or network appliances, such as Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations after joining a domain.

    Next Steps: Affected apps and network appliances will need an update from their developer or manufacturer to resolve this issue. Microsoft and Riverbed are presently investigating and will provide an update when more information is available.

    Affected platforms:

    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Apps that acquire or set Active Directory Forest Trust Information might have issues

    StatusOriginating updateHistory
    Mitigated KB5009586
    2022-01-11    		Last updated: 2022-02-07, 15:36 PT
    Opened: 2022-02-04, 16:57 PT

    After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API.

    Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.

    For instructions on how to install this update for your operating system, see the KB articles listed below:

    • ​Windows Server 2022: 
    • ​Windows Server 2019: 
    • ​Windows Server 2016: 
    • ​Windows Server 2012 R2: 
    • ​Windows Server 2012:

    Affected platforms:

    • ​Client: None
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; 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.


    Report a problem with Windows updates

    To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.

    Need help with Windows updates?

    Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.

    For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.

    View this site in your language

    This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.