Windows 10, version 1607 and Windows Server 2016

Windows 10, version 1607 and Windows Server 2016
  • Article
  • 12 minutes to check out

Find info on recognized concerns for Windows 10, variation 1607 and Windows Server2016 Trying to find a particular problem? Press CTRL + F (or Command + F if you are utilizing a Mac) and enter your search term( s). Desire the most recent Windows release health updates? Follow @WindowsUpdate on Twitter.


    Known problems

    This table provides a summary of present active concerns and those problems that have actually been fixed in the last 30 days.

    Summary Originating upgrade Status Last upgraded
    Copying files/shortcuts utilizing Group Policy Preferences may not work as anticipated
    Files or faster ways may not copy or copy as zero-byte files when utilizing Group Policy Preferences on customer gadgets.
    OS Build 14393.5356
    KB5017305
    2022-09-13
    Confirmed 2022-09-22
    16: 49 PT
    Update may stop working to set up and you may get a 0x800 f0922 mistake
    Security upgrade for Secure Boot DBX may stop working to set up.
    OS Build 14393.5285
    KB5012170
    2022-08-09
    Investigating 2022-09-20
    10: 06 PT
    Possible problems triggered by brand-new Daylight Savings Time in Chile
    Chilean federal government revealed a Daylight Saving Time (DST) modification for 2022.
    N/A Mitigated 2022-09-06
    14: 02 PT
    Certain apps or gadgets may be not able to produce Netlogon protected channel connections
    Scenarios which depend on artificial RODC maker accounts may stop working if they do not have actually a connected KRBTGT account.
    OS Build 14393.4886
    KB5009546
    2022-01-11
    Investigating 2022-02-24
    17: 41 PT
    Apps that get or set Active Directory Forest Trust Information may have concerns
    Apps utilizing Microsoft.NET to get or set Forest Trust Information may stop working, close, or you may get a mistake.
    OS Build 14393.4886
    KB5009546
    2022-01-11
    Mitigated 2022-02-07
    15: 36 PT
    Windows 10 Enterprise may not trigger through KMS
    Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 may have problems triggering utilizing brand-new CSVLK.
    OS Build 14393.4402
    KB5003197
    2021-05-11
    Confirmed 2021-12-01
    18: 10 PT
    Windows Presentation Foundation (WPF) apps may close, or you might get a mistake
    Microsoft and third-party applications which utilize the.Net UI structure called WPF may have problems.
    OS Build 14393.4225
    KB4601318
    2021-02-09
    Mitigated 2021-02-11
    20: 41 PT
    Cluster service might stop working if the minimum password length is set to higher than 14
    The cluster service might stop working to begin if “Minimum Password Length” is set up with higher than 14 characters.
    OS Build 14393.2639
    KB4467684
    2018-11-27
    Mitigated 2019-04-25
    14: 00 PT

    Issue information

    September 2022

    Copying files/shortcuts utilizing Group Policy Preferences may not work as anticipated

    Status Originating upgrade History
    Confirmed OS Build 14393.5356
    KB5017305
    2022-09-13
    Last upgraded: 2022-09-22, 16: 49 PT
    Opened: 2022-09-22, 15: 23 PT

    After setting up KB5017305, file copies utilizing Group Policy Preferences may stop working or may produce empty faster ways or files utilizing 0 (no) bytes. Understood afflicted Group Policy Objects belong to files and faster ways in User Configuration -> Preferences -> Windows Settings in Group Policy Editor.

    Workaround: To alleviate this concern, you can do ONE of the following:

    • Uncheck the “Run in logged-on user’s security context (user policy choice)”. Note: This may not alleviate the concern for products utilizing a wildcard
      .
    • Within the impacted Group Policy, modification “Action” from “Replace” to “Update”.
    • If a wildcard
      is utilized in the place or location, erasing the tracking “” (backslash, without quotes) from the location may enable the copy to be effective.

    Next actions: We are dealing with a resolution and will offer an upgrade in an approaching release.

    Affected platforms:

    • Client: Windows 11, variation 22 H2; Windows 11, variation 21 H2; Windows 10, variation 21 H2; Windows 10, variation 21 H1; Windows 10, variation 20 H2; 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

    Possible problems triggered by brand-new Daylight Savings Time in Chile

    Status Originating upgrade History
    Mitigated N/A Last upgraded: 2022-09-06, 14: 02 PT
    Opened: 2022-09-02, 13: 17 PT

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

    Symptoms if the workaround is not utilized on gadgets in between September 4, 2022 and September 11, 2022:

    • Time displayed in Windows and apps will not be appropriate.
    • Apps and cloud services which utilize date and time for important functions, such as Microsoft Teams and Microsoft Outlook, alerts and scheduling of conferences may be 60 minutes off.
    • Automation utilizing date and time, such as Scheduled jobs, may not perform at the anticipated time.
    • Timestamp on deals, files, and logs will be 60 minutes off.
    • Operations that depend on time-dependent procedures such as Kerberos may trigger authentication failures when trying to logon or gain access to resources.
    • Windows gadgets and apps beyond Chile may likewise be impacted if they are linking to servers or gadgets in Chile or if they are setting up or going to conferences happening in Chile from another place or time zone. Windows gadgets beyond Chile ought to not utilize the workaround, as it would alter their regional time on the gadget.

    Workaround: You can alleviate this concern on gadgets in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

    • Select the Windows logo design secret, type “Date and time”, and choose Date and time settings From the Date & time settings page, toggle Adjust for daytime conserving time instantly to Off
    • Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the choice for “Automatically change clock for Daylight Saving Time”.

    To alleviate this concern 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 actions listed below to re-enable automated DST modifications and make sure precise time changing with future DST shifts. This can be done by doing either of the following:

    • Select the Windows logo design secret, type “Date and time”, and choose Date and time settings From the Date & time settings page, toggle Adjust for daytime conserving time immediately to On
    • Go to Control Panel > Clock and Region > Date and Time > Change time zone and check the choice for “Automatically change clock for Daylight Saving Time”.

    Important: We advise utilizing ONLY the above workaround to reduce the problem with time developed by the brand-new Daylight Savings Time in Chile. We do NOT advise utilizing any other workaround, as they can develop irregular outcomes and may develop severe problems if not done properly.

    Next actions: We are dealing with a resolution and will offer an upgrade in an approaching release. Note: Microsoft strategies to launch an upgrade to support this modification; nevertheless, there may be inadequate time to correctly develop, test, and release such an upgrade prior to the modification enters into result. Please utilize the workaround above.

    Affected platforms:

    • Client: Windows 11, variation 21 H2; Windows 10, variation 21 H2; Windows 10, variation 21 H1; Windows 10, variation 20 H2; 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 may stop working to set up and you may get a 0x800 f0922 mistake

    Status Originating upgrade History
    Investigating OS Build 14393.5285
    KB5012170
    2022-08-09
    Last upgraded: 2022-09-20, 10: 06 PT
    Opened: 2022-08-12, 17: 08 PT

    When trying to set up KB5012170, it may stop working to set up, and you may get a mistake 0x800 f0922

    Note: This concern just impacts the Security upgrade for Secure Boot DBX ( KB5012170) and does not impact the current cumulative security updates, regular monthly rollups, or security just updates launched on August 9, 2022.

    Workaround: This concern can be reduced on some gadgets by upgrading the UEFI bios to the current variation prior to trying to set up KB5012170

    Next actions: We are currently examining and will offer an upgrade in an approaching release.

    Affected platforms:

    • Client: Windows 11, variation 21 H2; Windows 10, variation 21 H2; Windows 10, variation 21 H1; Windows 10, variation 20 H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
    • Server: Windows Server 2022; Windows Server, variation 20 H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

    February 2022

    Certain apps or gadgets may be not able to produce Netlogon safe and secure channel connections

    Status Originating upgrade History
    Investigating OS Build 14393.4886
    KB5009546
    2022-01-11
    Last upgraded: 2022-02-24, 17: 41 PT
    Opened: 2022-02-24, 17: 25 PT

    After setting up KB5009546 or any updates launched January 11, 2022 and in the future your domain controllers, situations which count on Read-only domain controllers (RODCs) or artificial RODC maker accounts may stop working to develop a Netlogon safe and secure channel. RODC accounts should have a connected and certified KRBTGT account to effectively develop a safe channel. Impacted applications or network home appliances, such as Riverbed SteelHead WAN Optimizers, may have concerns signing up with domains or constraints after signing up with a domain.

    Next Steps: Affected apps and network home appliances will require an upgrade from their designer or producer to fix this problem. Microsoft and Riverbed are currently examining and will supply an upgrade when more details is offered.

    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 get or set Active Directory Forest Trust Information may have concerns

    Status Originating upgrade History
    Mitigated OS Build 14393.4886
    KB5009546
    2022-01-11
    Last upgraded: 2022-02-07, 15: 36 PT
    Opened: 2022-02-04, 16: 57 PT

    After setting up updates launched January 11, 2022 or later on, apps utilizing Microsoft.NET Framework to obtain or set Active Directory Forest Trust Information may stop working, close, or you may get a mistake from the app or Windows. You may likewise get a gain access to infraction (0xc0000 005) mistake. Note for designers: Affected apps utilize the System.DirectoryServices API

    Like this post? Please share to your friends:
    Leave a Reply

    ;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: