Microsoft released four builds of Windows 10 cumulative updates -1809(17763.316)/1803 (17134.590)/1709 (16299.967)/1703 (15063.1631)/1607 (14393.2791)/1507(10240.18132)on February 13th, 2019. These updates are now available for all Windows users to free download and install on their PC now. If you are looking for access to download the latest update of Windows 10 1809/1803/1709/1703/1607/1507, here below you'll find direct download links for new Windows 10 cumulative updates.
- Install the Windows SDK to target Windows 10, versions 1607 and 1703. If your development targets systems that run Windows 10, version 1607 or Windows 10, version 1703, you should install Visual Studio 2015, and then also download and install the version of the Windows SDK for the targeted version of Windows 10, as identified in the following.
- Feature update to Windows 10, version 1607. Desktop with a message telling me that it's failed to install. I really don't want to go through a whole windows.
Mar 15, 2018 This update includes diagnostic improvements for determining the applicability of updates in Windows 10 Version 1703, Version 1607, Version 1511, and Version 1507. The files and resources in this update make sure that feature updates are installed seamlessly to improve the reliability and security of Windows 10. If you install KB 3206632, the Dec. 13 cumulative update for Windows 10 1607 that was released yesterday, and bring your build number up to 14393.576, that bug disappears. That’s the good news.
If you fail to install new updates of KB4487044/KB4487017/KB4486996/KB4487020/KB4487026/KB4487018 in your PC, relax and we have found effective methods for you to fix this issue without losing any data.
Backup system and data before downloading new Windows 10 updates
In order to avoid data loss issue or any system error while installing Windows 10 1809(17763.316)/1803 (17134.590)/1709 (16299.967)/1703 (15063.1631)/1607 (14393.2791)/1507(10240.18132) on your PC, it's highly necessary to create a system image and data backups in advance.
Professional Windows backup recovery software - EaseUS Todo Backup is a highly recommended system backup software for you to free backup Windows 10 with simple clicks.
1. Free download and install EaseUS Todo Backup in PC. Connect an external storage device to the computer.
2. Launch EaseUS Todo Backup and click 'File Backup' 'Disk/partition Backup' or 'System Backup'.
3. Choose data and specify the external hard drive as the backup destination, click Proceed to start backup data.
After backing up the Windows system and important personal data, you can now directly download and install Windows 10 with KB4487044/KB4487017/KB4486996/KB4487020/KB4487026/KB4487018 on your PC now. No data loss error will occur.
Free download and install the latest Windows 10 1809/1803/1709/1703/1607/1507 ISO
So how to get direct access to download and install the latest Windows 10 update 17763.316/17134.590/16299.967/15063.1631/14393.2791/10240.18132?
You can either choose to go to Microsoft and get Windows 10 or you can select any updates provided here in the below that you want to free download and install on your PC now:
Get Windows 10 1809 (17763.316):
Download Windows 10 17763.316 (KB4487044) x64
Download Windows 10 17763.316 (KB4487044) x86
Get Windows 10 1803 (17134.590):
Get Windows 10 1709 (16299.967)：
Get Windows 10 1703 (15063.1631):
Get Windows 10 1607 (14393.2791):
Get Windows 10 1507 (10240.18132):
Now you can directly install the latest Windows 10 updates on your PC and enjoy new features without any obstacles.
Can't complete Windows 10 update installing process? Relax, we have solutions for you.
Fix Windows 10 17763.316/17134.590/16299.967/15063.1631/14393.2791/10240.18132 failed to install error
If you are having Windows 10 update stuck error with latest OS builds or you failed to install Windows 10 1809/1803/1709/1703/1607/1507, just relax and you may follow below-offered methods to fix these problems with ease.
Method 1. Troubleshoot Windows 10 failed to install error
You can follow the below steps to directly run Troubleshoot to fix Windows update KB4487044/KB4487017/KB4486996/KB4487020/KB4487026/KB4487018 fail to install error:
- Type: troubleshooting in the search > Go to System and Security > Tap Fix problems with Windows Update.
- Tick Advanced > Enable and check Apply repairs automatically.
- Tap: Run as administrator (you may have to enter your passcode first) > Then click Next to finish the process.
Method 2. Reset Windows Components if Windows 10 17763.316/17134.590/16299.967/15063.1631/14393.2791/10240.18132 update failed
1. Press Windows + X and choose Command Prompt (Admin).
2. Stop BITS, Cryptographic, MSI Installer and the Windows Update Services.
Then type the below commands at the Command Prompt and hit Enter after you type each command:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
3. Rename the SoftwareDistribution and Cartoot2 folder. Then type the following command in the Command Prompt and press Enter after each type:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
4. Type Exit at the Command Prompt and restart PC.
After this, you may retry to install Windows 10 new updates in your PC with new features.
Method 3. Fix file system error and clean install Windows 10 update with KB4487044/KB4487017/KB4486996/KB4487020/KB4487026/KB4487018
File System error check will find and fix all system errors and Windows update problems for you.
- Press Windows + X and click on Command Prompt (Admin).
- Type: cd and hit Enter.
- Type: sfc /scannow and hit Enter.
- Wait patiently to let the check file system process complete, then Windows 10 updates fail to install issue will be repaired.
After this, you can then click the above-offered Windows 10 update links to clean install them on your PC.
-->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 |
| Domain controllers in your enterprise might encounter Kerberos authentication issues Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020. | OS Build 14393.4046 KB4586830 2020-11-10 | Resolved KB4594441 | 2020-11-19 10:00 PT |
| When installing incorrectly formatted third-party drivers, you might receive an error You might receive, “Windows can’t verify the publisher of this driver software” or other errors. | OS Build 14393.3986 KB4580346 2020-10-13 | Resolved | 2020-10-20 10:06 PT |
| Unable to access Security Options section in Group Policy Management Console You might receive an error 'MMC has detected an error in a snap-in.' or “MMC cannot initialize the snap-in”. | OS Build 14393.3930 KB4577015 2020-09-08 | Resolved KB4580346 | 2020-10-13 10:00 PT |
| Outlook closes unexpectedly or you might receive an error when attempting to open An example of an error you might receive is, 'Outlook couldn't start last time.' | OS Build 14393.3808 KB4565511 2020-07-14 | Resolved | 2020-07-15 15:43 PT |
| TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. | OS Build 14393.3274 KB4519998 2019-10-08 | Resolved External | 2020-07-14 10:19 PT |
| Print spooler might error or close unexpectedly when attempting to print Certain printers might be unable to print after taking updates released June 9, 2020. | OS Build 14393.3750 KB4561616 2020-06-09 | Resolved KB4567517 | 2020-06-18 10:00 PT |
Issue details
November 2020
Domain controllers in your enterprise might encounter Kerberos authentication issues | ||
| Status | Originating update | History |
| Resolved KB4594441 | OS Build 14393.4046 KB4586830 2020-11-10 | Resolved: 2020-11-19, 10:00 PT Opened: 2020-11-14, 01:39 PT |
After installing KB4586830 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting:
Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments. Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB4594441. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594441, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4594441 is not available from Windows Update and will not install automatically. | ||
October 2020
When installing incorrectly formatted third-party drivers, you might receive an error | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.3986 KB4580346 2020-10-13 | Resolved: 2020-10-20, 10:06 PT Opened: 2020-10-13, 09:37 PT |
When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when one or more of the following is present in a driver package:
Affected platforms:
Next steps: If this happens you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue. | ||
September 2020
Unable to access Security Options section in Group Policy Management Console | ||
| Status | Originating update | History |
| Resolved KB4580346 | OS Build 14393.3930 KB4577015 2020-09-08 | Resolved: 2020-10-13, 10:00 PT Opened: 2020-09-23, 06:37 PT |
Accessing the Security Options data view in the Group Policy Management Editor (gpedit.msc) or Local Security Policy Editor (secpol.msc) might fail with the error 'MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC' or “MMC cannot initialize the snap-in”. This occurs from the MMC window, when the console tree is expanded in the following sequence: select Computer Configuration, then Policies, then Windows Settings, then Security Settings, then Local Policies, then Security Options. The resulting error dialog provides options to continue using the Management Console to view other nodes normally. Note: This issue does not affect the application of the Security Options or any other Group Policy Objects (GPOs) to devices in your environment. Affected platforms:
Resolution: This issue was resolved in KB4580346. | ||
July 2020
Outlook closes unexpectedly or you might receive an error when attempting to open | ||
| Status | Originating update | History |
| Resolved | OS Build 14393.3808 KB4565511 2020-07-14 | Resolved: 2020-07-15, 03:43 PT Opened: 2020-07-15, 03:22 PT |
Microsoft Outlook might close unexpectedly or you might receive an error when attempting to open the app. An example of an error you might receive is, 'Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?' You might also see an event in the Event Viewer, as listed in the article linked below. Affected platforms:
Workaround: As an alternative, on your Windows 10 device you can use the Office365 on the web (OWA), also known as webmail. Outlook mobile is also unaffected. There is no workaround for this issue for the Outlook app on Windows 10 until the resolution is deployed to your device. We do not recommend using the command to revert to an earlier version. Resolution: This Outlook issue has been resolved and will be deployed automatically to your device. This issue was not related to any update for Windows and no update for Windows is needed. We expect this issue to be completely resolved for all affected users by July 15, 2020 at 3:30 PM PST (10:30 PM UTC). You may also need to attempt to open Outlook a few times before it will be fully refreshed and open as expected. For more information, please see the support article, Active Investigation into Outlook Crashing on Launch and this twitter thread. | ||
June 2020
Print spooler might error or close unexpectedly when attempting to print | ||
| Status | Originating update | History |
| Resolved KB4567517 | OS Build 14393.3750 KB4561616 2020-06-09 | Resolved: 2020-06-18, 10:00 PT Opened: 2020-06-12, 04:06 PT |
After installing KB4561616, certain printers may be unable to print. Print spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF. Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB4567517. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4567517, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4567517 is not available from Windows Update and will not install automatically. | ||
Download Windows 10 1607 Installer
November 2019
TLS connections might fail or timeout | ||
| Status | Originating update | History |
| Resolved External | OS Build 14393.3274 KB4519998 2019-10-08 | Last updated: 2020-07-14, 10:19 PT Opened: 2019-11-05, 03:36 PT |
Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
Affected platforms:
Resolution: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489. | ||