Resolved issues in Windows 10, version 1809 and Windows Server 2019
Find information on recently resolved issues for Windows 10, version 1809 and Windows Server 2019. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). 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 X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Servers might face performance issues with the August 2024 security update This issue affects some enterprise devices when Antivirus is enabled and is scanning the Windows system folder | OS Build 17763.6189 KB5041578 2024-08-13 | Resolved KB5043050 | 2024-09-10 10:00 PT |
| 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. | OS Build 17763.2452 KB5009557 2022-01-11 | Resolved External | 2024-08-20 16:29 PT |
| Devices might boot into BitLocker recovery with the July 2024 security update This issue is more likely to affect devices that have the Device Encryption option enabled | OS Build 17763.6054 KB5040430 2024-07-09 | Resolved KB5041578 | 2024-08-13 10:00 PT |
| Printing jobs using LPD protocol might fail with the July 2024 security update Issue was reported by organizations after installing the Windows July security update | OS Build 17763.6054 KB5040430 2024-07-09 | Resolved KB5041578 | 2024-08-13 10:00 PT |
| CrowdStrike issue impacting Windows endpoints causing an error message Affected systems might restart repeatedly and require recovery operations in order to restore normal use. | N/A | Resolved External | 2024-08-05 16:07 PT |
| The May 2024 security update might fail to install Some IT admins have reported that the update fails to install on devices where Windows is not set to English language | OS Build 17763.5820 KB5037765 2024-05-14 | Resolved KB5039705 | 2024-05-23 16:00 PT |
| VPN connections might fail after installing the April 2024 security update We are investigating user reports, and we will provide more information in the coming days | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved KB5037765 | 2024-05-14 10:00 PT |
| NTLM traffic issue after installing the April 2024 security update Customers have reported NTLM authentication failures and high load on affected domain controllers | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved KB5037765 | 2024-05-14 10:00 PT |
| BitLocker might incorrectly receive a 65000 error in MDMs "Requires Device Encryption" might incorrectly report as an error in some managed environments. | N/A | Resolved | 2024-04-26 16:21 PT |
| Issue with Kerberos requests on domain controllers may cause LSASS memory leaks This issue affects on-premises and cloud-based Active Directory DCs after installing the March 2024 security update | OS Build 17763.5576 KB5035849 2024-03-12 | Resolved KB5037425 | 2024-03-25 11:00 PT |
| Printer names and icons might be changed and HP Smart app automatically installs In most cases, it is possible to use the printer for printing jobs and other features such as copy, scan, or fax. | N/A | Resolved | 2023-12-22 15:53 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 | N/A | Resolved KB5032196 | 2023-11-14 10:00 PT |
Issue details
August 2024
Servers might face performance issues with the August 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5043050 | OS Build 17763.6189 KB5041578 2024-08-13 | Resolved: 2024-09-10, 10:00 PT Opened: 2024-08-21, 16:59 PT |
After installing the August 2024 Windows security update, released August 13, 2024 (KB5041578), you might observe that some Windows Server 2019 devices experience system slowdowns, unresponsiveness, and high CPU usage particularly with Cryptographic Services.
A limited number of organizations reported that the issue was observed when the device was running an Antivirus software which performs scans against the ‘%systemroot%\system32\catroot2’ folder for Windows updates, due to an error with catalog enumeration.
Our investigations so far indicate that this issue is limited to some specific scenarios. If your IT environment is affected, you might observe that your devices:
- Show increased CPU utilization
- Experience increased disk latency/ disk utilization
- Indicate degraded OS or application performance
- Show that the CryptSVC service fails to start
- May boot into a black screen
- Experience slow to boot
- Freeze or hang
Home users of Windows using Home or Pro editions are unlikely to face this issue as this scenario is more commonly used in enterprise environments.
Resolution: This issue was resolved by Windows updates released September 10, 2024 (KB5043050), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released September 10, 2024 (KB5043050) or later, you need not use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before September 10, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.
For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 10 1809 and Windows Server 2019: Windows 10 1809 and Windows Server 2019 KB5041578 240816_21501 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.
Affected platforms:
- Client: None
- Server: Windows Server 2019
Printing jobs using LPD protocol might fail with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041578 | OS Build 17763.6054 KB5040430 2024-07-09 | Resolved: 2024-08-13, 10:00 PT Opened: 2024-08-09, 16:46 PT |
After installing the July 2024 Windows security update, released July 9, 2024 (KB5040430), and later updates, you might encounter issues when trying to print documents using the Line Printer Daemon (LPD) protocol, which is a deprecated protocol.
People using Home or Pro editions of Windows for personal use are unlikely to face this issue as the LDP is a protocol used more often by IT departments to receive a print job on a printer or a server.
Note: The Line Printer Daemon protocol (LPR/LPD) is deprecated. When this feature is eventually removed, clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the Windows Standard Port Monitor.
Resolution: This issue is resolved by the Windows August 2024 security updates released August 13, 2024 (KB5041578), and later updates. We recommend you install the latest update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5041578 | OS Build 17763.6054 KB5040430 2024-07-09 | Resolved: 2024-08-13, 10:00 PT Opened: 2024-07-23, 13:57 PT |
After installing the July 2024 Windows security update, released July 9, 2024 (KB5040430), you might see a BitLocker recovery screen upon booting your device. This screen does not commonly appear after a Windows update. You are more likely to face this issue if you have the Device Encryption option enabled in Settings under Privacy & Security -> Device encryption. Resulting from this issue, you might be prompted to enter the recovery key from your Microsoft account to unlock your drive.
Resolution: This issue was resolved by Windows updates released August 13, 2024 (KB5041578), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released August 13, 2024 (KB5041578) or later, you do not need to use a workaround for this issue. If you are using an update released before August 13, 2024, and have this issue, your device should proceed to start up normally from the BitLocker recovery screen once the recovery key has been entered. You can retrieve the recovery key by logging into the BitLocker recovery screen portal with your Microsoft account. Detailed steps for finding the recovery key are listed here: Finding your BitLocker recovery key in 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 Enterprise 2015 LTSB
- Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008
CrowdStrike issue impacting Windows endpoints causing an error message
| Status | Originating update | History |
|---|---|---|
| Resolved External | N/A | Last updated: 2024-08-05, 16:07 PT Opened: 2024-07-19, 07:30 PT |
Microsoft has identified an issue impacting Windows endpoints which are running the CrowdStrike Falcon agent, developed by CrowdStrike Holdings. Following updates released and delivered by CrowdStrike on July 18, 2024, devices running the Falcon agent may encounter an error message on a blue screen and experience a continual restarting state.
Affected systems might restart repeatedly and require recovery operations in order to restore normal use.
Updated July 25, 2024: Microsoft released further guidance on Windows resiliency: Best practices and the path forward. Read more about how we are working in close cooperation to improve resiliency across the Windows ecosystem and explore best practices you can use to support resiliency in your organization.
Updated July 22, 2024: Microsoft has released a third mitigation option for this issue impacting Windows clients and servers. If devices are unable to recover with the two previous options mentioned below, IT admins can use PXE to remediate. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on prerequisites and configurations to use PXE Recovery.
Updated July 21, 2024: As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. Based on customer feedback, this new release includes a new option for recovery using safe boot, the option to generate ISO or USB, a fix for ADK detection when the Windows Driver Kit is installed, and a fix for the USB disk size check. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on using the signed Microsoft Recovery Tool.
Updated July 20, 2024: Microsoft has released KB5042426, which contains step-by-step guidance for Windows Servers hosted on-premises that are running the CrowdStrike Falcon agent and encountering a 0x50 or 0x7E error message on a blue screen. We will continue to work with CrowdStrike to provide the most up-to-date information available on this issue.
A new USB Recovery Tool is available to help IT admins expedite the repair process. The new tool can be found in the Microsoft Download Center. Read more about the new recovery tool and usage instructions at New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints.
Updated July 19, 2024: A new Knowledge Base article, KB5042421, with additional step-by-step guidance for Windows 11 and Windows 10 clients is now available. We will continue to work with CrowdStrike to provide up-to-date mitigation information as it becomes available.
To mitigate this issue ahead of additional resolution options, you can follow these steps:
- Start Windows into Safe Mode or the Windows Recovery Environment.
- Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
- Locate the file matching “C-00000291*.sys” and delete it.
- Restart the device.
- Recovery of systems requires a Bitlocker key in some cases.
For Windows Virtual Machines running on Azure follow the mitigation steps in Azure status.
Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - CrowdStrike Blog.
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 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
May 2024
The May 2024 security update might fail to install
| Status | Originating update | History |
|---|---|---|
| Resolved KB5039705 | OS Build 17763.5820 KB5037765 2024-05-14 | Resolved: 2024-05-23, 16:00 PT Opened: 2024-05-15, 19:17 PT |
Windows servers attempting to install the May 2024 Windows security update (KB5037765), released May 14, 2024, might face issues during the installation process. The installation might fail with an error code 0x800f0982. This issue is more likely to affect devices that do not have the English (United States) language pack.
In addition to users encountering error code 0x800f0982, we have received reports that devices are failing to install the May 2024 security update with the error code 0x80004005. This error can occur even if the English (United States) language pack is installed.
Some customers also reported install errors for this update on Windows 10, version 1809. Home users of Windows are unlikely to experience this issue since the Home and Pro editions of this Windows version reached end of servicing in 2020. Only Enterprise and IoT LTSC editions are under extended support.
Resolution:
This issue was resolved in the out-of-band (OOB) update KB5039705, which is available via the usual channels. Since this is a cumulative update, you do not need to apply any previous update before installing KB5039705, as it supersedes all previous updates for affected versions. This update does not contain any additional security updates from those available in the 5B update. Installation of this OOB will require a device restart. If your organization uses the affected platforms and hasn’t yet deployed the May 2024 security update yet, we recommend you apply this OOB update instead. To install this update, follow the steps under How to get this update in KB5039705.
Affected platforms:
- Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
- Server: Windows Server, version 1809; Windows Server 2019
April 2024
VPN connections might fail after installing the April 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037765 | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:15 PT |
Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036896) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037765), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
Client: Windows 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2.
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
NTLM traffic issue after installing the April 2024 security update
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037765 | OS Build 17763.5696 KB5036896 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:56 PT |
After installing the April 2024 security update (KB5036896) on domain controllers (DCs), you might notice a significant increase in NTLM authentication traffic. This issue is more likely to affect Active Directory (AD) deployments already servicing a large number of NTLM authentication requests where a small number of Primary Domain Controllers (PDCs) are supporting a large number of read-write Backup Domain Controllers (DCs) and Read Only Domain Controllers (RODCs).
Note: In rare instances, Windows Servers running the Domain Controller (DC) role might experience Local Security Authority Subsystem Service (LSASS) crashes resulting in a reboot.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037765), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
Client: none
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008
March 2024
Issue with Kerberos requests on domain controllers may cause LSASS memory leaks
| Status | Originating update | History |
|---|---|---|
| Resolved KB5037425 | OS Build 17763.5576 KB5035849 2024-03-12 | Resolved: 2024-03-25, 11:00 PT Opened: 2024-03-20, 18:39 PT |
Following installation of the March 2024 security update, released March 12, 2024 (KB5035849), Local Security Authority Subsystem Service (LSASS) may experience a memory leak on domain controllers (DCs). This is observed when on-premises and cloud-based Active Directory Domain Controllers service Kerberos authentication requests.
Extreme memory leaks may cause LSASS to crash, which triggers an unscheduled reboot of underlying domain controllers (DCs).
Note: This issue does not occur on Home devices. It affects only environments in organizations using some Windows Server platforms.
Resolution: This issue was resolved in the out-of-band (OOB) update KB5037425, which is only available via the Microsoft Update Catalog. We strongly recommend you do not apply the March 2024 security update on DCs and install KB5037425 instead. As this is a cumulative update, you do not need to apply any previous update before installing KB5037425. To install this update, search for KB5037425 in the Microsoft Update Catalog. The OOB update can then be manually imported to Windows Server Update Services (WSUS) and Configuration Manager. For guidance, see WSUS and the Microsoft Update Catalog.
If you manage update catalogs in Configuration Manager, please check the section Import updates. If you with you work with software update synchronization in Configuration Manager, review the steps on Import updates from the Microsoft Update Catalog. For more information about the Microsoft Update Catalog, visit Microsoft Update Catalog - FAQs.
Important: This update (KB5037425) is not available from Windows Update and will not install automatically.
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2
December 2023
Printer names and icons might be changed and HP Smart app automatically installs
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2023-12-22, 15:53 PT Opened: 2023-12-04, 18:46 PT |
Some issues related to printer configurations are being observed on Windows devices. Microsoft is investigating this issue and coordinating with partners on a solution.
Symptoms can include the following:
- Some Windows devices are installing the HP Smart app.
- Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
- 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.
Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool – December 2023. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device. To learn more about critical and recommended troubleshooters, see Keep your device running smoothly with recommended troubleshooting.
If you need support to resolve 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
October 2023
BitLocker might incorrectly receive a 65000 error in MDMs
| Status | Originating update | History |
|---|---|---|
| Resolved | N/A | Resolved: 2024-04-26, 16:21 PT Opened: 2023-10-09, 14:51 PT |
Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.
Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.
Resolution: Because this version of Windows 10 is under extended support, this issue will not be addressed in a future update. To learn about the scope of security updates for this version of Windows 10, see the Product Lifecycle FAQ - Extended Security Updates (ESU) program.
Please note, this issue remains limited to a reporting scenario only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues. BitLocker encryption functionality is expected to work correctly, despite the incorrect display of this error message in this issue.
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 Enterprise LTSC 2019
- Server: None
February 2023
Devices with locale set to Croatia might not utilize the expected currency
| Status | Originating update | History |
|---|---|---|
| Resolved KB5032196 | N/A | Resolved: 2023-11-14, 10:00 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.
- Open the "Windows Region" settings. This can be done in one of the following ways:
- Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
- 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,
- In the Region settings, choose one of the 2 locales for Croatia:
- Croatian (Bosnia & Herzegovina)
- Croatian (Croatia)
- In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
- 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.
Resolution: This issue was resolved in updates released November 14, 2023 (KB5032196) and later. We recommend installing the latest security updates for your device.
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
Apps or devices might be unable to create Netlogon secure channel connections
| Status | Originating update | History |
|---|---|---|
| Resolved External | OS Build 17763.2452 KB5009557 2022-01-11 | Last updated: 2024-08-20, 16:29 PT Opened: 2022-02-24, 17:25 PT |
After installing KB5009557 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 has provided the following documentation regarding devices from Riverbed Technology that are configured as RODCs: Information about devices from Riverbed Technology that are configured as RODCs. For further details or resolution guidance applicable to other network devices, contact the developer or manufacturer of the device.
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
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.