KB3213986

[Trouble]

Today (Update Tuesday I guess).
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3213986)
Resulting in a build number bump

PC and Mobile.

 

[Saltgrass]

Mine has been sitting on Downloading 95% Looks like it is going through the SoftwareDistribution folder and doing something with the packages.

Maybe this is a change from a prior process.

 

[Norton]

Keep us posted with the update. Thanks!

 

[Trouble]

Maybe this is a change from a prior process.

IDK, I really didn't monitor either of my updates, I just fired them up and let them run.
I know that the download for 64 bit systems is almost a gig

So it's indeed a sizeable update.
The 32 bit version is just over half a gig.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

SOURCE: https://support.microsoft.com/en-us/help/4009938/windows-10-update-kb3213986

So evidently it does look about for the needed versus un-needed bits.

 

[Norton]

Trouble Thanks for the info "I know that the download for 64 bit systems is almost a gig"

 

[Grizzly]

got mine installed today on my machines. went through without a hickup....

 

[Norton]

Same here.

 

[gtspeck]

No problems so far.

 

[Bif]

Yuppers, downloaded and installed the sizable offering...No issues with installation and/or functionality.............. Yet..

 

[Lynne Bartlett]

I'm experiencing the same problems as Saltgrass ("Downloading updates 95%" for the last 8+ hours).

Disk Utilisation is at 95% and CPU at 29%.

Broadband Speedtest shows 30MB/s on other machines on my home network, but 18MB/s on this machine.

System Details

1. Windows 10 Pro - Free upgrade from Windows 7 Pro.
2. Intel Core i5-2320 @ 3 GHz
3. 8 GB RAM
4. 64-bit

Any advice? Should I leave it for another few hours or cancel and try agin.

If the latter - what is the best way to do that: just reboot?

Thanks!

Lynne

 

[Lynne Bartlett]

Sorted. Not sure how much of the following had a material effect:

After 10 hours or so, Windows update returned to pre-update status. I ran the update again - same response.

I shut it down (rather than rebooted) and when I came back 30 minutes later, the machine was still running and the hard-drive busy but the screens black. So - with great fear and trepidation - I unplugged the power and plugged it in again. It booted up fine - and a dialog appeared to say that Windows was configuring/preparing itself.

I ran Windows Update again and this time the update was successful. So all's well that ends well.

Anyone able to shed light on this? What do you think "fixed" it?

Lynne

 

[davehc]

Your experience, Lynne, is similar to mine on two occasions. I have scheduled updates selected, so that it does not update during the day when I may be using the computer(s). But, I have also had to turn off the computer when the update stops, for no obvious reason. I have a vague idea as to what this could be, If you observe whilst it is downloading, that it fills he available cache in the middle of the operation and, of course, this is cleared with the shutdown.
I should add that I had two needed restarts with this latest update.

 

[Trouble]

It sounds to me like, someone at Microsoft might want to take another look at how "updates" are done (or in a lot of cases...... not done).
Leaving a users computer with a blank screen, black screen, some with a blinking cursor, some with a movable mouse arrow, some not. Some with spinning circles of dots endlessly and nothing apparently happening.
No status / progress indicator, no informational or error messages, nothing.
I'm not sure that, literally .... "pulling the plug" is a sound technical diagnostic tool, nor a prescription for the continued good health of your computer, but.......
Good on ya.
For having the courage to exercise a little outside the box thinking.

I always suggest having patience and giving it some time to complete whatever it might be doing covertly, but a computer that just sits for hours with no indication of what might be going on is, pretty worthless to every one.

I always say.....
IF you can't make it better.... make it worse and then start from there.

 

[Gonzi]

The download of this KB is fine but after the reboot, the computer crashes during the startup. The only way to run again the PC is to rollback to the restauration point before the installation. 3 installs, 3 crashes, 3 rollbacks, so much time lost... Now I just want to exclude that KB or to block any reboot.

 

[Trouble]

The download of this KB is fine but after the reboot, the computer crashes during the startup.

Is there any information during the crash?
An error message, or a BSOD? Did the crash generate any dump files which may contain some information regarding what might have cause the crash?

 

[Gonzi]

Hi Trouble, thanks for your answer
No message at all, the computer freezes when Windows is loading, like this :

After my 2nd crash, I looked at the logfile SrtTrail.txt in C:\Windows\System32\LogFiles\Srt. This file genrated by the repair process didn't diagnose any problem. Only the last operation (restoration) was marked as unsuccessful, however the computer was loading fine after that.
After the 3rd crash I choose directly to rollback to the last restoration point, then the SrtTrail.txt file is shorter, it shows that the 15 tests returned an error code 0x0, nothing more, so it has no interest to be uploaded.

 

[Saltgrass]

You might check the link and look at the possible log files available. This is for an upgrade and not an update but some of the files might be usable.. Check the dates and times to see if they were written during a failed update attempt.

https://technet.microsoft.com/itpro...upgrade-errors?OCID=WIP_r_20_Body_UpgradeTips

Another thing is you might try running the command below. When I was checking a log for someone else I realized the DISM process has undergone a slight change. If the process fails at 4.5%, let us know. Use an administrative command prompt window.

Dism /online /Cleanup-Image /RestoreHealth

 

[richard6]

I was having problems getting the 1607 upgrade to finish installing, getting stuck with the little rotating circle. The problem appears to have been caused by my wireless keyboard/mouse. When I pulled out the USB transceiver, the installation immediately resumed and completed. After the installation completed I was able to re-insert the transceiver and all was well.

 

[Norton]

Thanks for the update, Interesting to know, I've never had a problem with my wireless MS mouse.