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, use Get Help in Windows or go to support.microsoft.com. Follow @WindowsUpdate X (formerly Twitter) for Windows release health updates.
Resolved issues
Summary | Originating update | Status | Date resolved |
---|---|---|---|
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 |
You might receive an error with apphelp.dll from apps using DirectX After installing KB5019980 or later updates, devices with older Intel graphics drivers might encounter issues. | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved KB5029247 | 2023-08-08 10:00 PT |
KB5012170 might fail to install and you might receive a 0x800f0922 error Security update for Secure Boot DBX might fail to install. | OS Build 17763.3280 KB5012170 2022-08-09 | Resolved KB5023702 | 2023-03-14 10:00 PT |
Domain join processes may fail with error "0xaac (2732)" This might be encountered when an account was created by a different identity than the one used to join the domain | OS Build 17763.3532 KB5018419 2022-10-11 | Resolved KB5023702 | 2023-03-14 10:00 PT |
Application shortcuts might not work from the Start menu or other locations Errors might be observed when trying to run exe files. Changes to Microsoft Defender can help. | N/A | Resolved | 2023-01-18 19:28 PT |
Database connections using Microsoft ODBC SQL Server driver might fail. Apps using ODBC connections might fail to connect to databases. | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved KB5022286 | 2023-01-10 10:00 PT |
Software Defined Networking (SDN) managed by SCVMM might have issues with new VMs SCVMM might have issues creating new VMs or creating new NICs for existing VMs. | OS Build 17763.30000 KB5021237 2022-12-13 | Resolved KB5022554 | 2022-12-20 14:00 PT |
Direct Access might be unable to reconnect after your device has connectivity issues This issue might happen after losing network connectivity or transitioning between Wi-Fi networks. | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved KB5021237 | 2022-12-13 10:00 PT |
Possible memory leak in Local Security Authority Subsystem Service (LSASS,exe) LSASS might use more memory over time and the DC might become unresponsive and restart. | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved KB5021237 | 2022-12-13 10:00 PT |
Sign in failures and other issues related to Kerberos authentication After installing updates released November 2022, you might have Kerberos authentication issues. | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved | 2022-11-18 16:22 PT |
Possible issues caused by Daylight Savings Time change in Jordan Jordanian government announced a Daylight Saving Time (DST) change for winter 2022. | N/A | Resolved KB5019966 | 2022-11-08 10:00 PT |
Issue details
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
You might receive an error with apphelp.dll from apps using DirectX
Status | Originating update | History | Resolved KB5029247 | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved: 2023-08-08, 10:00 PT Opened: 2023-02-08, 15:49 PT |
---|
After installing KB5019966 or later updates, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 26.20.100.7463 up to 30.0.101.1190. This issue might happen intermittently and affects a small number of enterprise apps which use DirectX or Direct3D to render part or all of their content. Windows devices using updated Intel graphics drivers with a version later than 30.0.101.1190 are not affected by this issue and already have the Intel resolution for this issue installed.
Home users of Windows are unlikely to experience this issue, as the few affected apps are more commonly used in enterprise environments.
Workaround: To mitigate this issue, you can install an Intel graphics driver with a later version than 30.0.101.1190. It is recommended to check your Windows device manufacturer's support for the latest version of the Intel graphics driver for your device. If they do not offer a driver later than 30.0.101.1190, you can check List of Drivers for Intel Graphics for information on how to download and install the latest Intel graphics driver available from Intel directly.
Resolution: This issue was resolved in KB5029247.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022
January 2023
Application shortcuts might not work from the Start menu or other locations
Status | Originating update | History | Resolved | N/A | Resolved: 2023-01-18, 19:28 PT Opened: 2023-01-13, 13:40 PT |
---|
After installing security intelligence update build 1.381.2140.0 for Microsoft Defender, application shortcuts in the Start menu, pinned to the taskbar, and on the Desktop might be missing or deleted. Additionally, errors might be observed when trying to run executable (.exe) files which have dependencies on shortcut files. Affected devices have the Atack Surface Reduction (ASR) rule "Block Win32 API calls from Office macro" enabled. After installing security intelligence build 1.381.2140.0, detections resulted in the deletion of certain Windows shortcut (.lnk) files that matched the incorrect detection pattern.
Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.
Workaround: Changes to Microsoft Defender can mitigate this issue. The Atack Surface Reduction (ASR) rules in Microsoft Defender are used to regulate software behavior as part of security measures. Changing ASR rules to Audit Mode can help prevent this issue. This can be done through the following options:
- Using Intune: Enable attack surface reduction rules | Defender for Endpoint: Microsoft Endpoint Manager
- Using Group Policy: Enable attack surface reduction rules | Defender for Endpoint: Group Policy
Microsoft Office applications can be launched through the Microsoft 365 app launcher. More details on the Microsoft 365 app launcher can be found in Meet the Microsoft 365 app launcher
Next steps: This issue is resolved in security intelligence update build 1.381.2164.0. Installing security intelligence update build 1.381.2164.0 or later should prevent the issue, but it will not restore previously deleted shortcuts. You will need to recreate or restore these shortcuts through other methods. For additional information and help recovering missing shortcuts, see Recovering from Attack Surface Reduction rule shortcut deletions (updated on January 17, 2023 to include additional guidance and scripts to help with recovery).
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB
- Server: None
December 2022
Database connections using Microsoft ODBC SQL Server driver might fail.
Status | Originating update | History | Resolved KB5022286 | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved: 2023-01-10, 10:00 PT Opened: 2022-12-05, 15:45 PT |
---|
After installing KB5019966, apps which use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as "The EMS System encountered a problem" with "Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream" or "Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server". Note for developers: Apps affected by this issue might fail to fetch data, for example when using the SQLFetch function. This issue might occur when calling SQLBindCol function before SQLFetch or calling SQLGetData function after SQLFetch and when a value of 0 (zero) is given for the ‘BufferLength’ argument for fixed datatypes larger than 4 bytes (such as SQL_C_FLOAT).
If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt (select Start then type command prompt and select it) and type the following command:
tasklist /m sqlsrv32.dll
Workaround: To mitigate this issue, you can do one of the following:
- If your app is already using or able to use Data Source Name (DSN) to select ODBC connections, install Microsoft ODBC Driver 17 for SQL Server and select it for use with your app using DSN. Note: We recommend the latest version of Microsoft ODBC Driver 17 for SQL Server, as it is more compatible with apps currently using the legacy Microsoft ODBC SQL Server Driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.
- If your app is unable to use DSN, the app will need to be modified to allow for DSN or to use a newer ODBC driver than Microsoft ODBC SQL Server Driver (sqlsrv32.dll).
Resolution: This issue was resolved in KB5022286. If you have implemented the above workaround, it is recommended to continue using the configuration in the workaround.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- 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
Software Defined Networking (SDN) managed by SCVMM might have issues with new VMs
Status | Originating update | History | Resolved KB5022554 | OS Build 17763.30000 KB5021237 2022-12-13 | Resolved: 2022-12-20, 14:00 PT Opened: 2022-12-13, 09:48 PT |
---|
After installing KB5021237 on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021237, only new Network Adapters created after installation of KB5021237 are affected.
When experiencing this issue, you might receive one of the following errors:
- When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection"
- Software defined networking (SDN) software load balancer service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error"
- SDN RAS Gateway service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error"
Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands:
$lang = (Get-WinSystemLocale).Name
C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\$lang\VfpExt.mfl
C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof
A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this KB article.
Resolution: This issue was resolved in out-of-band (OOB) updates released December 20, 2022 for installation on all Hyper-V hosts in your environment which are using Software Defined Networking (SDN) and managed by System Center Virtual Machine Manager (SCVMM). You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue.
To get the standalone package for these out-of-band (OOB) updates, search for the KB number 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. Note The below updates are not available from Windows Update and will not install automatically.
Cumulative updates:
Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released December 13, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019
November 2022
Direct Access might be unable to reconnect after your device has connectivity issues
Status | Originating update | History | Resolved KB5021237 | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved: 2022-12-13, 10:00 PT Opened: 2022-11-13, 14:49 PT |
---|
After installing KB5019966 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).
Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected.
Workaround: You can mitigate this issue by restarting your Windows device.
Resolution: This issue was resolved in KB5021237.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2019
Possible memory leak in Local Security Authority Subsystem Service (LSASS,exe)
Status | Originating update | History | Resolved KB5021237 | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved: 2022-12-13, 10:00 PT Opened: 2022-11-23, 17:54 PT |
---|
After installing KB5019966 or later updates on Domain Controllers (DCs), you might experience a memory leak with Local Security Authority Subsystem Service (LSASS,exe). Depending on the workload of your DCs and the amount of time since the last restart of the server, LSASS might continually increase memory usage with the up time of your server and the server might become unresponsive or automatically restart. Note: The out-of-band updates for DCs released November 17, 2022 and November 18, 2022 might be affected by this issue.
Workaround: To mitigate this issue, open Command Prompt as Administrator and use the following command to set the registry key KrbtgtFullPacSignature to 0:
reg add "HKLM\System\CurrentControlSet\services\KDC" -v "KrbtgtFullPacSignature" -d 0 -t REG_DWORD
Note: Once this known issue is resolved, you should set KrbtgtFullPacSignature to a higher setting depending on what your environment will allow. It is recommended to enable Enforcement mode as soon as your environment is ready. For more information on this registry key, please see KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967.
Resolution: This issue was resolved in KB5021237. If you used the above workaround, please see KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967 for further information on how to configure KrbtgtFullPacSignature.
Affected platforms:
- Client: None
- Server: Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Sign in failures and other issues related to Kerberos authentication
Status | Originating update | History | Resolved | OS Build 17763.3650 KB5019966 2022-11-08 | Resolved: 2022-11-18, 16:22 PT Opened: 2022-11-13, 15:16 PT |
---|
Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1.
After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:
- Domain user sign in might fail. This also might affect Active Directory Federation Services (AD FS) authentication.
- Group Managed Service Accounts (gMSA) used for services such as Internet Information Services (IIS Web Server) might fail to authenticate.
- Remote Desktop connections using domain users might fail to connect.
- You might be unable to access shared folders on workstations and file shares on servers.
- Printing that requires domain user authentication might fail.
When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1":
While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.
Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.
Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.
Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.
To get the standalone package for these out-of-band updates, search for the KB number 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. Note The below updates are not available from Windows Update and will not install automatically.
Cumulative updates:
Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
Standalone Updates:
- Windows Server 2012 R2: KB5021653
- Windows Server 2012: KB5021652
- Windows Server 2008 R2 SP1: KB5021651 (released November 18, 2022)
- Windows Server 2008 SP2: KB5021657
Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- 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
October 2022
Domain join processes may fail with error "0xaac (2732)"
Status | Originating update | History | Resolved KB5023702 | OS Build 17763.3532 KB5018419 2022-10-11 | Resolved: 2023-03-14, 10:00 PT Opened: 2022-10-27, 15:53 PT |
---|
Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy."
This issue originates with the October 2022 security updates ( KB5018419) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior.
Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain.
Home users of Windows are unlikely to experience this issue.
Resolution: This issue was resolved in updates released March 14, 2023 ( KB5023702) or later. Please see KB5020276 to understand the newly re-designed behavior. We have added information about a new Allowlist policy for trusted computer account creators to this KB.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; 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; Windows 8.1; Windows 7 SP1
- Server: Windows Server 2022; Windows Server, version 20H2; 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
Possible issues caused by Daylight Savings Time change in Jordan
Status | Originating update | History | Resolved KB5019966 | N/A | Resolved: 2022-11-08, 10:00 PT Opened: 2022-10-21, 14:34 PT |
---|
On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone.
The impact of this change is as follows:
- Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone.
- The Jordan time zone will permanently shift to the UTC + 3 time zone.
Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later:
- Time shown in Windows and apps will not be correct.
- Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.
- Automation using date and time, such as Scheduled tasks, might not run at the expected time.
- Timestamp on transactions, files, and logs will be 60 minutes off.
- Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.
- Windows devices and apps outside of Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device.
Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows:
- Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off.
- Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.
Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly.
Resolution: This issue was resolved in KB5019966.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- 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
August 2022
KB5012170 might fail to install and you might receive a 0x800f0922 error
Status | Originating update | History | Resolved KB5023702 | OS Build 17763.3280 KB5012170 2022-08-09 | Resolved: 2023-03-14, 10:00 PT Opened: 2022-08-12, 17:08 PT |
---|
When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.
Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates.
Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.
Resolution: This issue was resolved in KB5023702 or later updates.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
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.