Is somewhere available Windows 10 1607 ISO to download? Page 1 of 3 1 2 3 Last. Jump to page: pirix. Windows 10 New 14 Jul 2017 #1. In attempting to install Windows 10 Creators Update, I formatted my hard drive and lost my latest version of Windows 10. Where can I download Windows 10 1607!!.Post moved by the moderator to the appropriate forum category. Here are a couple ways you can manually get the Windows 10 Anniversary Update. Go to Settings Updates & Security Windows Update. In Windows Update simply click Check for Updates. The Anniversary Update will appear as, Feature update to Windows 10, version 1607. Click update and the update will begin downloading and installing. The 'Blue Light' reduction feature was first introduced in Windows 10 build 15002. It was renamed to 'Night Light' in build 15019. Night Light - Turn On or Off in Windows 10. It sounds like you don't have the latest Windows 10 Insider build installed to have this feature available yet. Windows 10 Build Number - Find.
-->Find information on known issues for Windows 10, version 1607 and Windows Server 2016. 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.
| Windows 10, version 21H1 is now available Find out how to get the update > | IT tools for Windows 10, version 21H1 Explore the latest tools and resources to support your rollout > |
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Printing and scanning might fail when these devices use smart-card authentication Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication. | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
| Windows Presentation Foundation (WPF) apps might close, or you may receive an error Microsoft and third-party applications which use the .Net UI framework called WPF might have issues. | OS Build 14393.4225 KB4601318 2021-02-09 | Mitigated | 2021-02-11 20:41 PT |
| Cluster service may fail if the minimum password length is set to greater than 14 The cluster service may fail to start if “Minimum Password Length” is configured with greater than 14 characters. | OS Build 14393.2639 KB4467684 2018-11-27 | Mitigated | 2019-04-25 14:00 PT |
Issue details
July 2021
Printing and scanning might fail when these devices use smart-card authentication | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved: 2021-08-03, 10:36 PT Opened: 2021-07-23, 14:36 PT |
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. Affected platforms:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. | ||
February 2021
Windows Presentation Foundation (WPF) apps might close, or you may receive an error | ||
| Status | Originating update | History |
| Mitigated | OS Build 14393.4225 KB4601318 2021-02-09 | Last updated: 2021-02-11, 20:41 PT Opened: 2021-02-11, 17:49 PT |
After installing KB4601318, Windows Presentation Foundation (WPF) apps might close, or you may receive an error similar to: Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef) at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr) at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean) at System.Windows.Interop.HwndMouseInputProvider.Dispose() This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps. Affected platforms:
Workaround: To mitigate this issue when using Microsoft Visual Studio, update to the latest version. This issue is resolved starting with the following releases: Developers can mitigate this issue in their own apps by setting two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”. The switches are named Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix; both should be set to “true”. The first switch avoids the crash, but re-introduces the issue addressed in this update. The second switch is currently ignored, but will be recognized in a future .NET update that addresses the issue for the null-reference crash; it restores the behavior originally intended to be addressed in this update. For example, using the app.config file method to apply the workaround at application scope: <AppContextSwitchOverrides value='Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true ' /> Next steps: We are working on a resolution and will provide an update in an upcoming release. | ||
November 2018
Cluster service may fail if the minimum password length is set to greater than 14 | ||
| Status | Originating update | History |
| Mitigated | OS Build 14393.2639 KB4467684 2018-11-27 | Last updated: 2019-04-25, 14:00 PT Opened: 2018-11-27, 10:00 PT |
After installing KB4467684, the cluster service may fail to start with the error '2245 (NERR_PasswordTooShort)' if the Group Policy 'Minimum Password Length' is configured with greater than 14 characters. Affected platforms:
Workaround: Set the domain default 'Minimum Password Length' policy to less than or equal to 14 characters. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. | ||
-->
See a list of known issues that have been resolved for Windows 10, version 1607 and Windows Server 2016 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Printing and scanning might fail when these devices use smart-card authentication Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication. | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
| Apps might have issues accessing event logs on remote devices Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later. | OS Build 14393.10001 KB5003638 2021-06-08 | Resolved KB5003638 | 2021-06-08 10:00 PT |
| Security updates released May 11, 2021 might not offer in managed environments Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices are affected. | OS Build 14393.4402 KB5003197 2021-05-11 | Resolved | 2021-05-11 19:01 PT |
| Unexpected results when printing from some apps or to some printers Issues might include missing or solid color graphics, misalignment/formatting issues, or printing of blank pages/labels. | OS Build 14393.4283 KB5000803 2021-03-09 | Resolved KB5001633 | 2021-03-18 19:00 PT |
| Installation of Cumulative Update from Windows Update might not progress Installation issues when attempting to install updates from Windows Update. | OS Build 14393.4222 KB4601392 2021-02-09 | Resolved KB5001078 | 2021-02-12 19:00 PT |
Issue details
July 2021
Printing and scanning might fail when these devices use smart-card authentication | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.4530 KB5004238 2021-07-13 | Resolved: 2021-08-03, 10:36 PT Opened: 2021-07-23, 14:36 PT |
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. Affected platforms:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. | ||
Windows 10 1607 End Of Life
June 2021
Apps might have issues accessing event logs on remote devices | ||
| Status | Originating update | History |
| Resolved KB5003638 | OS Build 14393.10001 KB5003638 2021-06-08 | Resolved: 2021-06-08, 10:00 PT Opened: 2021-06-07, 16:10 PT |
After installing KB5003638 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected. Affected platforms:
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003638 installed. | ||
May 2021
Security updates released May 11, 2021 might not offer in managed environments | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.4402 KB5003197 2021-05-11 | Resolved: 2021-05-11, 19:01 PT Opened: 2021-05-11, 14:58 PT |
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003197 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates. Affected platforms:
Resolution: This issue is now resolved on the service-side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions. | ||
March 2021
Unexpected results when printing from some apps or to some printers | ||
| Status | Originating update | History |
| Resolved KB5001633 | OS Build 14393.4283 KB5000803 2021-03-09 | Resolved: 2021-03-18, 19:00 PT Opened: 2021-03-18, 17:25 PT |
After installing updates released March 9, 2021 or March 15, 2021, you might get unexpected results when printing from some apps. Issues might include:
Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB5001633. It is a cumulative update, so you do not need to apply any previous update before installing it. You will need to Check for updates to install KB5001633 and might need to also select Download and Install. For instructions on how to Check for updates, please see Update Windows 10. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5001633 is cumulative and addresses both the issue above and the issue addressed in the March 15, 2021 out-of-band release for the APC_INDEX_MISMATCH error with a blue screen. | ||
February 2021
Installation of Cumulative Update from Windows Update might not progress | ||
| Status | Originating update | History |
| Resolved KB5001078 | OS Build 14393.4222 KB4601392 2021-02-09 | Resolved: 2021-02-12, 19:00 PT Opened: 2021-02-11, 17:50 PT |
After installing KB4601392, installation of Cumulative Update from Windows Update might not progress past 24%. Affected platforms:
Workaround: To mitigate this issue on devices that have already installed KB4601392 and are not making progress installing a Cumulative Update, restart your device then follow only steps 1, 2 and 4a from Reset Windows Update components manually and then restart your device again. KB5001078 should now install from Windows Update when you select 'check for updates' or you can wait for it to install automatically. You should then be able to install the latest Cumulative Update from Windows Update. Resolution: This issue was resolved in KB5001078. Note Devices that have already installed KB4601392 might need to follow the workaround above before KB5001078 will be offered and installed by Windows Update to resolve the issue. KB4601392 has been removed and will no longer be offered to devices. | ||