Windows 10 periodically checks for updates so you don’t have to. When an update is available, it’s automatically downloaded and installed, keeping your device up to date with the latest features.
Check Manually For Windows 10 Updates
To check for updates manually, select the Start button, and then go to Settings > Update & security > Windows Update, and select Check for updates. If Windows Update says your device is up to date, you have all the updates that are currently available.
If issue still persists I would suggest you to reset Windows Update components and for that try to run the fixit provided in the following article. If you had already tried the same fixit before I would request you to run the fixit again.
Registry disclaimer: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
Are you getting error 0x80070bc2 during the installation of Windows uypdate KB4074588 ?
In the search box on the taskbar, type cmd.
Right-click Command Prompt in the search results and select Run as administrator. (Select Yes, when prompted by the User Account Control.)
In the Administrator: Command Prompt window, type the following command and press Enter:
SC config trustedinstaller start=auto
Restart the PC.
In some cases, a second restart may be required. If you look under Settings > Update & Security and you see the message Status: Awaiting restart, restart the PC a second time to complete the installation.
When you create a user account, you can choose between two types of accounts either a local account for that PC or a Microsoft account, which works on all the Windows 10 PCs you use. Microsoft recommend using a Microsoft account.
If you don’t want to use password each time you log-in, you can use local user account. To create new local account follow the below steps:
Press Windows + R key and type netplwiz and hit enter.
When you create a user account, you can choose between two types of accounts: a local account for that PC or a Microsoft account, which works on all the Windows 8.1 and Windows RT 8.1 PCs you use. We recommend using a Microsoft account..
Click or tap on Add.
Click or tap on Sign in without Microsoft account.
Click on Local account and enter the details (don’t give any password).
Click OK and sign out from the current account and sign into new created account.
This update should apply via Windows Update – If it does not, or you need to install this manually here is the direct download link.
Improvements and fixes
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
Addressed issue where some UWP and Centennial apps show a gray icon and display the error message “This app can’t open” on launch.
Addressed reliability issue that causes the AppReadiness service to stop working.
Addressed issue where applications that use the Silverlight map stack stop working.
Addressed issue where VSync prevents devices from entering Panel Self Refresh mode, which can lead to reduced battery life.
Addressed issue where user customizations (like pinned tiles) made to an enforced partial Start layout are lost when upgrading to Windows 10 1703.
Addressed issue where the Universal CRT caused the linker (link.exe) to stop working for large projects.
Addressed issue that prevents Windows Error Reporting from saving error reports in a temporary folder that is recreated with incorrect permissions. Instead, the temporary folder is inadvertently deleted.
Addressed issue where the MSMQ performance counter (MSMQ Queue) may not populate queue instances when the server hosts a clustered MSMQ role.
Addressed issue with the token broker where it was leaking a token that caused sessions to remain allocated after logoff.
Addressed issue where Personal Identity Verification (PIV) smart card PINs are not cached on a per-application basis. This caused users to see the PIN prompt multiple times in a short time period; normally, the PIN prompt only displays once.
Addressed issue where using the Cipher.exe /u tool to update Data Recovery Agent (DRA) encryption keys fails unless user certification encryption already exists on the machine.
Addressed issue where using AppLocker to block a Modern app fails. This issue occurs only with Modern apps that come pre-installed with Windows.
Addressed issue with form submissions in Internet Explorer.
Addressed issue with the rendering of a graphics element in Internet Explorer.
Addressed issue that prevents an element from receiving focus in Internet Explorer.
Addressed issue with the docking and undocking of Internet Explorer windows.
Addressed issue caused by a pop-up window in Internet Explorer.
Addressed issue where a Vendor API deleted data unexpectedly.
Addressed issue where using the Robocopy utility to copy a SharePoint document library, which is mounted as a drive letter, fails to copy files. However, in this scenario, Robocopy will copy folders successfully.
Addressed issue where MDM USB restrictions did not disable the USB port as expected.
Addressed issue where creating an iSCSI session on a new OS installation may result in the “Initiator instance does not exist” error when attempting to connect to a target.
Addressed issue where connecting to RDS applications published using Azure App Proxy fails. The error message is, “Your computer can’t connect to the Remote Desktop Gateway server. Contact your network administrator for assistance”. The error can occur when the RDP cookie size limit is exceeded. This update increased the size of the RDP cookie limit.
Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
Addressed issue that affects the download of some games from the Windows Store during the pre-order phase. Download fails with the error code 0x80070005, and the device attempts to restart the download from the beginning.
Addressed issue where the ServerSecurityDescriptor registry value does not migrate when you upgrade to Windows 10 1703. As a result, users might not be able to add a printer using the Citrix Print Manager service. Additionally, they might not be able to print to a client redirected printer, a Citrix universal print driver, or a network printer driver using the Citrix universal print driver.
Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Microsoft Edge, Windows Authentication, Windows TPM, Device Guard, Windows Wireless Networking, Windows Storage and Filesystems, Microsoft Windows DNS, Microsoft Scripting Engine, Windows Server, Windows Subsystem for Linux, Microsoft JET Database Engine, and the Windows SMB Server.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.
Known issues in this update
Installing KB4034674 may change Czech and Arabic languages to English for Microsoft Edge and other applications.
Microsoft is working on a resolution and will provide an update in an upcoming release.
Systems with support enabled for USB Type-C Connector System Software Interface (UCSI) may experience a blue screen or stop responding with a black screen when a system shutdown is initiated.
If available, disable UCSI in the computer system’s BIOS. This will also disable UCSI features in the Windows operating system.
Microsoft is working on a resolution and will provide an update in an upcoming release.
Microsoft is aware of a publishing issue with the October 10th, 2017 monthly security update for Windows 10 version 1703 (KB4041676) for WSUS\SCCM managed devices where Windows devices may fail to boot after installing this update
Customers that download updates directly from Windows Update (Home and consumer devices) or Windows Update for Business are not impacted.
We have corrected this publishing issue. For users who encountered issues please refer to the following article:
d) Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Type the following commands in the Command Prompt for this. Press the ENTER key after you type each command.
Method 3: Scan and restore the operating system files health.
a. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
b. Type the following commands. Press Enter after each command.
On a Windows 10 machine (version 1607) if you are unable to install update KB3200970 please try the following :-
1. Check windows update for KB3197954
2. Uninstall this update as this is the one that seems to cause the error – Reason: Checking the CBS.log file (located in c:\windows\logs\CBS) showed that Package 7 of KB3197954 was not installed.
3. Copy the following file on to a notepad and save the file as “Repair.Bat”
net stop wuauserv
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
ren catroot2 catroot2old
net start cryptsvc
4. Run this Repair.Bat as Administrator
5. Check if the c:\windows\system32\catroot2 has been renamed to c:\windows\system32\catroot2old
6. Copy “Catroot2” file folder from c:\windows\system32 from a working PC where the updates have been installed successfully.
7. Upon completing all the above reboot the PC.
8. Post Restart, Check for updates.
9. The updates should now download and install successfully.
The above information was found on a Microsoft forum and resolved the issue for one of our customers.
WER stands for Windows Error Reporting (WER). Windows Error Reporting collects and offers to send post-error debug information (a memory dump), using the Internet, to the developer of an application that crashes or stops responding on a user’s desktop.
Windows Error Reporting: Windows Error Reporting in Windows is a feature that allows Microsoft to track and address errors relating to the operating system, Windows features, and applications. Windows Error Reporting gives users the opportunity to send data about errors to Microsoft and to receive information about solutions. Solution information can include instructions for working around a problem, or a link to the Windows Update Web site or another Web site for updated drivers, patches, or Microsoft Knowledge Base articles. Microsoft developers can use Windows Error Reporting as a problem-solving tool to address customer problems in a timely manner and to improve the quality of Microsoft products.
Problem Reports and Solutions: The Problem Reports and Solutions feature in Control Panel helps users track problem reports and any solution information they have received from Microsoft. Problem Reports and Solutions only helps the user store information. All Internet communication related to problem reports and solutions is handled by Windows Error Reporting, although the display of solution information in Problem Reports and Solutions uses a Web browser control.
Ask each time a problem occurs: Windows Error Reporting always prompts for consent before sending an error report.