Problem With Windows 10 Updates After Installin Windows 10 Anniversary Update 1607 - Hoses On Download

Hello,  I updated to version 1607.  Then trying to install the updates needed after the upgrade.  Starts downloading and hoses up at 52%.   Reboot, try again, this time maybe 77%.   Reboot, try again and this time 62%.    Ran the the WindowsUpdateDiagnostic. The error was Service Registration Is Missing or Corrupt.   Ran the FixWindowsupdate Commands..... see script at end of this question.  Rebooted, same problem.   The removal of the SoftwareDistribution folder and the catroot2 folder fails.

These commands fail because files are in use by other processes.  I have not been able to "unbusy" these files so the folders can be deleted.

     rd %systemroot%\SoftwareDistribution /s

     rd %systemroot%\system32\catroot2 /s

Now here is the strange part.  I have updated over 40 PCs to version 1607 with no problems using windows update aftward.  However the last 3 done this weekend are the only ones to hose up on the download.   Now let me add some other info......  all 3 of these PCs are at a 2nd site across town.  I physically went there and installed the 1607 upgrade.  Then remotely have been working on the follow-on updates.  They hose up.

V1607 at our primary site installs and the updates work fine.  Did 3 PCs last week with no problems.  The 2nd site has 100mb/sec cable fibre LAN download and upload speed.   Primary site is subnet, 2nd site is subnet.  2nd site has 2 domain controllers/dns servers.  1st site has 5 domain controllers/dns servers.   I am almost wondering if it might be a DNS problem.   Have check download and upload speeds and getting in excess ofn 100mb/sec.  This is all one domain.

Very puzzled.  Need assistance.  Please advise.  Thanks.

The script we run as administrator:

net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc

Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

rd %systemroot%\SoftwareDistribution.bak /s

rd %systemroot%\system32\catroot2.bak /s

rd %systemroot%\SoftwareDistribution /s

rd %systemroot%\system32\catroot2 /s




cd /d %windir%\system32


regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
 regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll


netsh winsock reset

net start bits

net start wuauserv

net start appidsvc

net start cryptsvc

Who is Participating?

Improve company productivity with a Business Account.Sign Up

Hector2016Connect With a Mentor Systems Administrator and Solutions ArchitectCommented:
According to the Microsoft thread mentioned there are many administrators struggling with this issue.

It is clear to me that WSUS alone can't solve the Windows Update clients affected and is unavoidable to manually install the lasted Cumulative Update on that computers.

To do so you must download the right version of the KB3189866:

Then manually install and reboot.

On the Microsoft Forum someone has created a Powershell Script to automate this task as a start-up script:

$hotfixId= 'kb3189866'
$id=Get-HotFix -id $hotfixId -ErrorAction SilentlyContinue | Select -ExpandProperty HotFixId
if( $id -eq $hotfixId) {
echo "already exist"
$SB={ Start-Process -FilePath 'c:\windows\system32\wusa.exe' -ArgumentList "\\dati\Software\kb_fixes\win10_1607\AMD64-all-windows10.0-kb3189866-x64.msu /quiet /norestart" -Wait -PassThru }
Invoke-Command -ScriptBlock $SB

Open in new window

If you decide to use this script, you will have to modify the script to adapt it to your LAN. The downloaded files must be copied to a shared folder with read and execute permissions for everyone. Also, you will need to create two GPO, one for each platform (x86 or x64) and use a WMI filter to apply the x86 MSU package to x86 computers only and x64 version to x64 computers exclusively.

After that, all issues should be fixed for Windows 10 1607.
If you have any other issue please let us know.
A known bug of 1607, only with wsus.
Tomorrow night comes the solution: The next cumulative update. Needs to be installed scripted.
DonConnect With a Mentor Network AdministratorCommented:
Do you have window firewall service disabled ??
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Hector2016Systems Administrator and Solutions ArchitectCommented:
The kb3176938 solved the issue on my computers. I had to download the CAB files from these locations:

    Windows 10 Build 14393.105 32-bit

    Windows 10 Build 14393.105 64-bit

Then install the right version on each computer with this method:

How to Install Cumulative Update KB3176938 CAB Files on Windows 10?

1. Download the CAB files x86/x64 depending upon the OS architecture.
2. Rename file to KBnumber.сab (here should be
3. Copy to folder C:\
4. Run command-prompt as admin (Right click on Windows icon and choose option). Check the image above.
5. Enter the command "Start /w Pkgmgr /ip /m:c:\KB3176938.сab /quiet" (Without quotes)

This installs the KB3176938 CAB File in stealth or quiet mode without any UI prompt. Your devices will restart once the installation is over. Else you may need to restart your PC.
Hector, MS themselves say, it is not resolved, yet. MS themselves say, it is about cumulative updates - the other updates are not affected. So detecting the next CU might prove that MS is right and your problem is still not solved - we will have to wait just until tomorrow night.
Hector2016Systems Administrator and Solutions ArchitectCommented:
The author of the question didn't specify if the issue is with Cumulative Updates or with all Updates, so I can assume that the whole Windows Update Client is not working like was in my case. That is why I post my comment, to show a way to solve that problem today, not tomorrow. It is up to the author of this question to decide if my solution is useful or not.
Hector2016Systems Administrator and Solutions ArchitectCommented:
You also need to decline Update KB3176934 in WSUS.
Look, after you install a cumulative update, the others install without problems. That has been the case since the launch of 1607. So installing the CU manually, will indeed allow to install all other updates 2-date but it will not solve the problem, that the next CU will crash windows update again. At least that is what Microsoft says.
rstuemkeAuthor Commented:
Windows firewall is active.  Not using WSUS

Ran this.... from the above link...

REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DODownloadMode /t REG_DWORD /d 100 /f

Booted and started Windows Update again......  sat at 50%
Yes... it is not resolved. The link I gave you has comments in it from Microsoft themselves. Again: look for Steve Henry's comment in my link. It says
...A fix is scheduled for September's Patch Tuesday (9/13)
rstuemkeAuthor Commented:
Thanks everyone..... will update after the 13th and see what happens......
rstuemkeAuthor Commented:
But..... here is the strange thing...... like I said I have installed 1607 and the culmulative update on over 40 PCs.  Only these 3 at our 2nd site are giving me problems downloading.  Don't you this that is strange.  never had any problems before these 3 PCs.   Can still do updates at our 1st site.   Would like some comments about that part of the problem.  Thanks.
The service becomes unstable (this is discussed, read it). It does not mean that it may not function from time to time, so most probably, your other machines are kind of lucky.
rstuemkeAuthor Commented:
Thanks.......  was concerned that it may be a networking problem at 2nd site.   But nothing else is having a problem......
Hector2016Systems Administrator and Solutions ArchitectCommented:
Hello everyone.
I would like to know if this Is a solved problem today.
Not really. The latest patch has added even more havoc (cannot download, cannot install, suddenly windows says it's installed and so on... all over
But if it has fixed the problem will only be answered on the next patch day (as I said before).
Fine and dandy, but...

I was after this already 2 days ago and what happens is:
-on many machines, that update (downloaded from the same sources that you mention) does not even install. It simply stalls and never finishes. When you restart the computer, you can see "installation failed" in the update history. Some would succeed on 2nd try, some not. There have been various reports on about this. Something is very screwy here and this patch is not recommendable to install, wait for a new revision. I had problems on 6 out of 8 machines where I tried to install it.
Hector2016Systems Administrator and Solutions ArchitectCommented:
I have tested both kb3176938 and kb3189866 on two affected computers, and always the Windows Update Client gets repaired. The difference is the version of the build.

kb3176938 --> Windows 10.0.14393.105 and Windows Update is fixed.
kb3189866 --> Windows 10.0.14393.187 and Windows Update is fixed too.

See the change on my test computer Win10anni:

This picture was taken before the kb3189866 manually installed:
Windows 10 version before kb3189866
And this other was taken after the update:
Windows 10 version after kb3189866
As you can see the other Windows 10 test computer W10-Test is already fixed with the kb3176938.
Have a look at
It tells us why the update you recommend (kb3189866 ) has been pulled from their servers:
We encountered a network transmission issue that affected update 3189866, published on September 13, 2016. The quickest way to address this issue was to reissue the update to all Content Delivery Networks. This new update package, KB3193494, includes the same set of fixes as KB3189866. We apologize for any inconvenience this may have caused.
So although there is this new CU KB3193494, we still have to wait for the next CU of october's patchday to say for sure if it has finally been resolved.

By the way: server 2016 has the same problem. For it, you need to manually install KB3192366 (search it here: )
Hector2016Systems Administrator and Solutions ArchitectCommented:
I am happy to know that Microsoft has solved the issue with WSUS deploying KB3193494, but I had solved this issue many days ago by manually installing Kb3189866.
rstuemkeAuthor Commented:
Actually, part of the problem was a setting on the firewall.  That helped a bit.  Finally downloaded the KB fix manually and was able to install it that way.   Thank you for your help, appreciate the time you gave with assistance.
Hector2016Systems Administrator and Solutions ArchitectCommented:
Nice to help you.
Don't forget to close the question and assign the points.
Hector, who suggested that the solution was to install the next cumulative update scripted?
Hector2016Systems Administrator and Solutions ArchitectCommented:
Distributed points.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.