Windows 10: Cumulative Update KB4034658 for Win 10 Ver1607 won't complete download

As my updates to Win 10 Ver 1703 failed a number of times for various reasons I thought it best to turn back the clock with a Macrium backup, and then watch the update process more carefully as it proceeded. Last night I got to the Windows Update settings page, which showed several to be downloaded, one of which is the Cumulative Update for Ver 1607. which failed for error 0x800700002, and Feature Update for error 0xc1900107, which I have seen before. And it also says "We can't install others as other updates are in progress..." and suggest a restart. I've been through this drill before with no total completion of updates. Feel like I am going in a circle. My desktop did the 1703 update without a hitch or bobble so I am not rushed to get the laptop 'fixed'. I would be happy to format the HD and install my original Win 10 from my ISO and proceed from there as long as I had some assurance that that would work. Your suggestions and direction will be most welcome. The simplest way to fix the thing would be the best. My thanks in advance. PS: I just restarted and got back to the Update page and it says the Cumulative update is available and it is attempting to download it. Sorry for the length, but the story is long.

:)

 

2017-08 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4034658)

2017-08 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4034658)

I am experiencing issue with download of 2017-08 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4034658). It either doesn't download or gets stuck

 

help me

2017-08 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4034658) - erro 0x80073701

 

Only those that are already using your computer's configuration know for sure whether you can upgrade smoothly with a clean install as they have already upgraded.

Two of my computers failed to upgrade from 1607 to 1703 and the first one took me a very long time to troubleshoot. It was within a week or two after a clean install. Immediately after the clean install drivers, applications, and files were reinstalled. Then two to three weeks later Microsoft started offering the first upgrades from 1607 to 1703.

So when you use the phrase will it work after a clean install it depends. Since you can immediately install 1703 without an upgrade it is extremely likely to go smoothly provided that you check to see that the computer meets all of the minimum requirements. And since you already have 1607 and are not upgrading from 7 or 8.1 by default it should work.

Knowing that you can perform a clean install you may want to try a couple of methods as you know that you have a backup plan.

If the Windows upgrade failure did not display the reason for the failure (my first failure to upgrade didn't but my 2nd failure to upgrade displayed the problem) it will take time and effort to figure out the underlying problem. You then can make a decision whether to try that method or proceed to the clean install.

Open file explorer > this PC > local C: drive > in the menu bar modify the view section so you can view hidden files > search for each of these logs:

setuperr.log
setupact.log
Setupmem.dmp $Windows.~bt\Sources\Rollback\setupmem.dmp
setupapi.dev.log $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
BlueBox.log
$Windows.~bt\Sources\Rollback*.evtx

The above logs are generated spontaneously. There is no manual method to produce them. So some will be found and others were never generated..

The most frequently used logs to troubleshoot are:
setuperr.log
setupact.log
but the others if they are found are likely to improve the troubleshooting process.

These are factors that prevented the upgrade of both of my HP computers:
1) how many languages had you installed in addition to English?
2) had you download any extra fonts?
3) have you used the HP UEFI diagnostics to check the hardware?

HP computers have a very nice feature: HP UEFI diagnostics.
At any time you can check the HP hardware.
Most computer manufacturers do not have these UEFI diagnostics to test CPU, GPU, RAM, Drivers, Keyboards, Audio, etc.
The above three items by surprise are not installed on the free space on the C drive.
Instead they are installed on the partition.
So there is a higher incidence of failure to upgrade on HP computers as the 1703 upgrade needs a certain amount of free space in the partition. If the free space is not there the upgrade fails. On the first computer there was no error message and I was left to discover the problem by troubleshooting the logs. On the second computer there was a clear error message. So with practice on the first computer I know how to troubleshoot the second computer.

In addition when I had had my upgrade problem in March I had contacted Microsoft and HP. Both entities had methods to fix the problem. They were different approaches but the same concept. So it was helpful to know that there were other options.

So the most effective and efficient method is to perform the clean install (delete partitions, format, make an unallocated drive, install the new operating system)

In September there is supposed to be an update to windows 10 version 1703 so you could wait another month to have the latest windows 10 iso version and build before upgrading.

 

Many thanks for your thoughts and valuable info, and the upcoming 1703 update tip. I'm going to save your instructions and wait until the Sept update for 1703 appears and then begin in earnest following your suggestions. I just like to mess with these things as doing so keeps the mind working and provides a challenge. I'm far from my youth and I just noticed that the computer is 8 years old and far from its youth, at least in terms of today's technology, so a replacement may be called for soon. Most or all of what it is used for can be done on my iPad or phone, but I just like the big screen laptop.
Again, many thanks.