-->
Updates failing to install for me was pretty rare on xp, vista, 7 and 8. I started having failed updates more often starting with 10 th1. New cumulative updates for 1607 from May 2019 onward fail to install 100% on non-LTSB editions of Windows 10 v1607 (Home, Professional, Education & Enterprise), RanCorX2. 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. Dec 09, 2019 But, as per the reports, many Windows users have been facing this trouble where they are unable to install the update. What happens is that the operating system attempts to update version 1607 but it fails. When users go to the update history, this is what they see, “Feature Update To Windows 10, Version 1607 Failed To Install On”.
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
When installing Cumulative Update for Windows 10 Version 1607 (KB4015438), the update process appears to freeze or stop By LK 2020-09-10T05:47:56-07:00 Modified: September 10, 2020 March 25th, 2017 Categories: Windows Tags: Windows 10, Windows 10 Anniversary Update (Version 1607 - Build 14393), Windows Update 0 Comments. Feature Update to Windows 10 Version 1607 Failed to Install Windows has rolled out a new Anniversary Update, version 1607, to its Windows 10 operating system, offering many new features.
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. | ||
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. | ||
WSL, the Windows Subsystem for Linux, is a free, optional feature of Windows 10 that allows Linux programs to run on Windows. It provides you with a Windows version of the bash shell and a compatibility layer that permits many Linux programs to run natively on your Windows machine.
System requirements
Before installing WSL, make sure your computer meets the minimum system requirements to run WSL:
- You must be running Windows 10 version 1607 (the Anniversary update) or above.
- WSL only runs on 64-bit versions of Windows 10. 32-bit versions are not supported.
To check that the computer meet the requirements, follow these steps:
- Open your Settings. You can do this by clicking the gear icon on the Start menu, or by opening the Power User Tasks menu and choosing Settings.
- In the Settings window, choose System.
- On the left side of the System window, choose About.
- On the right side of the window, system information is displayed. Make sure the Version is at least 1607, and the System type is a 64-bit operating system.
If the Version number is less than 1607, you need to perform a Windows Update before installing WSL.
If the System type is not a 64-bit operating system, you cannot run WSL.
Installing WSL
To install WSL, follow these steps.
NoteVersions of Windows previous to the Fall Creators Update required slightly different instructions. The instructions on this page are current as of May 2019.
- Open a new PowerShell window as Administrator. To do this, open your Start menu, scroll down to W, and expand the Windows PowerShell folder. Right-click Windows PowerShell, choose More, then Run as administrator.
- At the PowerShell prompt, run the following command:
- Some necessary software downloads, and the WSL subsystem will be enabled after you reboot. Linux itself is not installed yet, however (until you choose a Linux distribution, in step 5.)
- When the download is complete, PowerShell ask if you're ready to reboot the computer. Before rebooting, make sure any documents are saved, and any open applications are closed. Type Y, or if you're going to reboot later, type N instead.
- After your computer reboots, log in to Windows and open a new Command prompt (or PowerShell). At the prompt, run:
- Bash will inform you that no distribution is installed, and give you a URL for downloading one from the Windows Store:
- In a web browser, navigate to the URL https://aka.ms/wslstore to download a WSL-integrated Linux distribution. As of this writing, choices are Ubuntu, OpenSUSE, SUSE Enterprise Server, Debian, and Kali. If you're not sure what to pick, we recommend Ubuntu.
- Click the distribution of your choice, then click Get.
- When the installation is complete, click Launch. You will see this message:
It may silently wait for you to press a key after it's done, so you might want to press Backspace every 15 seconds or so, to check if it's finished.
This error is a known bug that has occurred in some versions of Windows 10. If you get this error, you can fix it by repeating steps 1 and 2. Then, continue to step 10.
Failed To Install Windows 10 Version 1607 Update
- Ubuntu is now installed, and WSL is enabled. You can open the WSL Ubuntu command prompt by clicking the Launch button in the Windows Store or in the Start menu by choosing Ubuntu. You can also open a command prompt (or PowerShell) and run bash.
Getting started with your Linux subsystem
The first time you run your WSL distribution, you will be asked to create a user account. It can be different than your Windows username. You will be asked to set a password.
Congratulations! Linux is running. You're now at the bash prompt, and you can run Linux commands and programs.
Update your Linux software
Now is a great time to perform a software update. Follow the instructions below to update your software with the apt command.
Like Ubuntu, WSL uses the APT (advanced packaging tool) to manage software packages. The apt command allows you to search for, download, and install software, all from the command line. It automatically manages your software dependencies for you. That way, if one program depends on a certain version of another program, both will be installed, and kept up-to-date.
Any apt commands that make changes to your system must run as root. If you're logged in as your regular user (as you usually should be), run a program as root by prefixing it with sudo ('superuser do'). It requires you enter your password, and your program is run as root.
Updates download, but nothing is installed or upgraded yet. Gothic 2 nacht des raben free download. To upgrade all available packages, run:
Windows 10 1607 Update Standalone
TipSudo will not ask you for your password this time, unless more than five minutes have elapsed since the last sudo command.
The size of the upgrades will be calculated, and you will be prompted to continue. Type y and press Enter. The upgrades download and install, which might take a while, depending on the speed of your computer and Internet connection.
When the upgrade is complete, you will be returned to the bash prompt. Your Linux system is now up-to-date.
At any time, you can exit bash using the exit command.
The Windows and WSL filesystems
WSL has its own filesystem. This Linux filesystem is installed to your Windows filesystem at the following location:
For instance, if your Windows username is Owner and Windows is installed on your C: drive, your WSL filesystem is located at:
It's good to know that this is where it's located, but you shouldn't move or make any changes to the files it contains.
When you're using WSL, you might be wondering how you can access your Windows files. Your C: drive is located at:
The name mnt stands for 'mount,' which is where your Windows drives are mounted within WSL. For instance, your D: drive would be /mnt/d/, etc.
Creating links to Windows folders
For convenience, it's a good idea to create symbolic links to your Windows home folder. A symbolic link is similar to a shortcut in Windows: it's a file that points to another file or directory. When you refer to the symbolic link, the system will dereference the link, and behave as if you had specified the actual 'target' file or directory.
Using symbolic links can save you a lot of typing, and remembering of obscure directory names.
To create a symbolic link in Linux, use the ln command. The syntax for creating a symbolic link is ln -s targetnamelinkname.
For instance, to create a symbolic link in your WSL home folder called winhome that refers to C:UsersOwner, follow these steps.
First, change the working directory to your home directory, which is located at /home/username/. You can do this with the cd command:
In bash, '~' (a tilde) is an alias for your home directory, so you can also type:
Next, use ln -s to create the symbolic link. For instance, if your Windows home folder is C:UsersOwner, the command would be:
Now there's a symbolic link called winhome in your WSL home directory, which acts like a shortcut to your Windows home directory. So, you can change to your Windows home directory using:
Or, to change to your Windows desktop folder:
More information about Linux commands
Enjoy your new Linux subsystem! Make sure to visit our overview of Linux commands for more information about tools and programs you can use.
