Windows 10, version 1809 and Windows Server 2019

Find information on known issues for Windows 10, version 1809 and Windows Server 2019. 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.

Current status as of May 11, 2021:
As of May 11, 2021, all editions of Windows 10, version 1809 and Windows Server 2019 have reached end of servicing, except LTSC editions. Devices running these editions will no longer receive monthly security and quality updates containing protections from the latest security threats.

As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For information about servicing timelines and lifecycle, see the Windows 10 release information and Lifecycle FAQ - Windows.

    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
    Copying files/shortcuts using Group Policy Preferences might not work as expected
    Files or shortcuts might not copy or copy as zero-byte files when using Group Policy Preferences on client devices.
    OS Build 17763.3406
    KB5017315
    2022-09-13
    Confirmed
    2022-09-22
    16:49 PT
    The September 2022 preview release is listed in Windows Server Update Services
    Preview updates are generally made available from the Microsoft Update Catalog and Windows Updates.
    N/A

    Confirmed
    2022-09-22
    14:31 PT
    Possible issues caused by new Daylight Savings Time in Chile
    Chilean government announced a Daylight Saving Time (DST) change for 2022.
    N/A

    Resolved
    KB5017379
    2022-09-20
    10:00 PT
    Update 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
    Investigating
    2022-09-20
    10:06 PT
    Devices with some Asian language packs installed may receive an error
    Devices with Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
    OS Build 17763.437
    KB4493509
    2019-04-09
    Resolved
    2022-09-13
    16:52 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.
    OS Build 17763.2452
    KB5009557
    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.
    OS Build 17763.2452
    KB5009557
    2022-01-11
    Mitigated
    2022-02-07
    15:36 PT
    Windows 10 Enterprise might not activate via KMS
    Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might have issues activating using new CSVLK.
    OS Build 17763.1911
    KB5001384
    2021-04-22
    Confirmed
    2021-12-01
    18:10 PT

    Issue details

    September 2022

    Copying files/shortcuts using Group Policy Preferences might not work as expected

    StatusOriginating updateHistory
    ConfirmedOS Build 17763.3406
    KB5017315
    2022-09-13
    Last updated: 2022-09-22, 16:49 PT
    Opened: 2022-09-22, 15:23 PT

    After installing KB5017315, file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings in Group Policy Editor.

    Workaround: To mitigate this issue, you can do ONE of the following:

    • ​Uncheck the "Run in logged-on user's security context (user policy option)". Note: This might not mitigate the issue for items using a wildcard (*).
    • ​Within the affected Group Policy, change "Action" from "Replace" to "Update".
    • ​If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotes) from the destination might allow the copy to be successful.

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

    Affected platforms:

    • ​Client: Windows 11, 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
    • ​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

    The September 2022 preview release is listed in Windows Server Update Services

    StatusOriginating updateHistory
    ConfirmedN/A

    Last updated: 2022-09-22, 14:31 PT
    Opened: 2022-09-22, 10:51 PT

    IT administrators who utilize Windows Server Update Services (WSUS) might notice that the Windows September 2022 preview update, known as the 'C' release, is listed among the updates available from WSUS. This listing is an error. Preview updates are generally available for manual importing via the Microsoft Update Catalog and Windows Updates.

    This issue might also affect the installation of the September 2022 Cumulative Update Preview for .NET Framework, which is also generally available via Windows Update and Microsoft Update Catalog. For more information on .NET Framework September 2022 Cumulative Update Preview updates, see the KB articles listed on the .NET blog for the September 2022 Cumulative Update Preview.

    Home users of Windows are unlikely to experience this issue. WSUS is commonly utilized by technology administrators to deploy Microsoft product updates in managed environments. 

    Workaround: The Windows September 2022 preview release was made available via Microsoft Update Catalog. We recommend IT administrators to use this release channel moving forward.

    Please note: In environments where WSUS is configured to auto-approve updates and also auto-decline superseded content, the Windows September 2022 Security update may subsequently be auto-declined and auto-expired from the client view. If this occurs, see the guidance for reinstating declined updates. Then run an update synchronization within Microsoft Endpoint Configuration Manager, or update management environments. Environments configured to only take security updates should not reflect these symptoms.

    Next steps: The Windows September 2022 preview release is being removed from WSUS and we are working on a resolution to support customers who had imported updates via WSUS inadvertently. We estimate a solution will be available in the coming days.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 11, version 21H1; Windows 10, version 20H2; Windows 10, version 1809
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809

    Possible issues caused by new Daylight Savings Time in Chile

    StatusOriginating updateHistory
    Resolved KB5017379N/A

    Resolved: 2022-09-20, 10:00 PT
    Opened: 2022-09-02, 13:17 PT

    Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

    Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

    • ​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 Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

    Workaround: This issue is now resolved in KB5017379 but you should undo the workaround, if it is still being used.

    You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

    • ​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”.

    To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:

    • ​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 On.
    • ​Go to Control Panel Clock and Region Date and Time Change time zone and check 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 Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly.

    Resolution: This issue was resolved in KB5017379. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017379 will not change the "Automatically adjust clock for Daylight Saving Time" setting.

    Affected platforms:

    • ​Client: 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

    August 2022

    Update might fail to install and you might receive a 0x800f0922 error

    StatusOriginating updateHistory
    InvestigatingOS Build 17763.3280
    KB5012170
    2022-08-09
    Last updated: 2022-09-20, 10:06 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 released on August 9, 2022.

    Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

    Next steps: We are presently investigating 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 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

    February 2022

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

    StatusOriginating updateHistory
    InvestigatingOS Build 17763.2452
    KB5009557
    2022-01-11
    Last updated: 2022-02-24, 17:41 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 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
    MitigatedOS Build 17763.2452
    KB5009557
    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

    December 2021

    Windows 10 Enterprise might not activate via KMS

    StatusOriginating updateHistory
    ConfirmedOS Build 17763.1911
    KB5001384
    2021-04-22
    Last updated: 2021-12-01, 18:10 PT
    Opened: 2021-12-01, 17:44 PT

    After installing updates released April 22, 2021 or later on an affected version of Windows Server when used as Key Management Services (KMS) host, client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note: This does not affect activation of any other version or edition of Windows.

    Client devices attempting to activate that are affected by this issue might receive the error, "Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information." Event Log entries related to activation is another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs, then Application. If you see only event ID 12288 (without a corresponding event ID 12289), this means that the KMS client was not able to reach the KMS host, the KMS host did not respond, or the client did not receive the response. For more information on these event ID, see Useful KMS client events - Event ID 12288 and Event ID 12289.

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

    Affected platforms:

    • ​Client: Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016

    May 2019

    Devices with some Asian language packs installed may receive an error

    StatusOriginating updateHistory
    ResolvedOS Build 17763.437
    KB4493509
    2019-04-09
    Resolved: 2022-09-13, 16:52 PT
    Opened: 2019-05-02, 16:36 PT

    After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

    Workaround:

    1. ​Uninstall and reinstall any recently added language packs. For instructions, see "Manage the input and display language settings in Windows 10".
    2. ​​Click Check for Updates and install the April 2019 Cumulative Update or later. For instructions, see "Update Windows 10".

    Note: If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server.

    Resolution: This issue is resolved by updates released June 11, 2019, and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) prior to installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows:

    1. ​Install the latest prerequisite SSU, currently KB5005112
    2. ​Install optional components or language packs
    3. ​Install latest cumulative update

    Note: Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it. 

    Affected platforms:

    • ​Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
    • ​Server: Windows Server, version 1809; Windows Server 2019