From time to time, Microsoft delivers a relatively big Windows 10 update called “Cumulative Update” to your computer. Most recent one was 2017-07 Cumulative Update for Windows 10 Version 1703 for x64 (or x86)-based Systems (KB4032188). KB means Knowledge Base used by Microsoft.

Whilst I did not have problem installing this big update for my 32bit (x86 based system) Desktop computer, my ASUS Notebook with x64 based Windows 10 system had an issue of downloading the update. It got stuck at 19% and did not proceed any further. I left it for a day but did not complete downloading the update.
This happened after I checked Windows 10 update manually and started downloading the big update. Although KB number is different, Screen Shot was like the following image.

Once your download gets stuck, it appears there is no way to complete the update and it will affect future updates as well.

To solve this, I did the following;
1. Search for 2017-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4032188)
2. Then it shows Microsoft Knowledge based:
3. It shows a relevant update for downloading: 2017-07 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4032188) Windows 10 Updates 8/1/2017 n/a 848.2 MB
4. As you can see, it’s a quite big file “848.2MB”.
5. Download the file to my local computer.
6. Applied the update manually.
7. However, it did not update the system straight away but saying “updating Windows cache” and again got stuck.
8. All I had to do was shutdown the computer completely and started again – again applied the update – then succeeded.

For you reference, the contents of this big update are as follows;

KB4032188 (OS Build 15063.502)

Addressed issue that causes a Microsoft Installer (MSI) application to fail for standard (non-admin) users when installed on a per user basis.
Addressed issue to enable support in the DevDetail Configuration Service Provider (CSP) to return the UBR number in the D part of the SwV node.
Addressed issue where NTFS sparse files were unexpectedly truncated (NTFS sparse files are used by Data Deduplication—deduplicated files may be unexpectedly corrupted as a result). Also updated chkdsk to detect which files are corrupted.
Addressed issue where the IME pad was not launching correctly in the Microsoft Edge browser for certain markets.
Addressed issue to allow Win32 applications to work with various Bluetooth LE devices including head tracking devices.
Addressed issue in the Mobile Device Manager Enterprise feature to allow headsets to work correctly.
Addressed issue where device drivers are not loading.
Addressed a reliability issue when playing specific types of spatial sound content.
Addressed issue with a dropped key on Microsoft Surface Keyboard and Microsoft Surface Ergo Keyboard, and addressed Wacom active pen connection failures.
Addressed issue to improve stability for USB type C during device arrival and removal during system power changes.
Addressed USB host controller issue where the host controller no longer responds to the attached peripherals.
Addressed MP4 compatibility issue while playing content from a social media site in Microsoft Edge.
Addressed issue with audio headsets connected to a PC through Xbox 360 controllers.
Addressed a reliability issue with launching a Settings app while another application is using the camera device concurrently.
Addressed issue with notifications (SMS, Calendar) for an activity tracker.
Addressed issue with video playback artifacts during transitions from portrait to landscape on mobile devices.
Addressed issue with Skype calls becoming unresponsive after about 20 minutes when using Bluetooth headsets with Hands-Free Profile (HFP) connections with negotiated mSBC codec (Wideband Speech).
Addressed issue where a service using a Managed Service Account (MSA) fails to connect to the domain after an automatic password update.
Addressed issue where, in some cases, a drive that utilizes on-drive hardware encryption would not automatically unlock at system startup.
Addressed issue where “cipher.exe /u” fails on client machines that are deployed with InTune, Windows Information Protection (WIP), and an updated Data Recovery Agent (DRA) certificate. Cipher.exe will fail with one of the following errors: “The request is not supported” or “The system cannot find the file specified”.
Addressed issue where a memory leak occurs in a nonpaged pool with the “NDnd” memory tag when you have a network bridge set up.
Addressed issue where you cannot add Work and School accounts in Windows Store, and you may get an error that reads, *We encountered an error; please try signing in again later.”
Addressed issue issue where if a Surface Hub enters Sleep mode and then resumes, it may require the user to sign in to Skype again.
Addressed issue where some Windows Forms (WinForms) applications that use DataGridView, Menu controls, or call a constructor for a Screen object experienced performance regressions in .NET 4.7. This was caused by additional Garbage Collections. In some cases, there was an empty UI because of a lack of GDI+ handles.
Addressed issue where Magnifier Lens users cannot click on buttons or select web content in Microsoft Edge or Cortana results.
Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.

Reply to a comment by soul (19/11/17)

Thanks for your comment.  Much appreciated.  Sorry, I cannot post a reply comment as it shows my login id.  Microsoft is now releasing “Major Update” twice a year which may cause all sorts of issues.  (your printer and other devices stop working etc.)  It’s not a bad idea to take full backup before the updating.  Harry

Your comments are welcome (subject to moderation).  Nickname is allowed for comment posting, however, you must provide a valid e-mail address (will not to be displayed).  If you fill out Website box, website address will be linked on your name appeared on the comment.  As regard to the treatment of your e-mail address, please refer to ACE PRIVACY POLICY.