Windows 10 1607 patch KB 3206632 solves the ‘dropped internet connection’ bug

Topic

New Reply

In general, yesterday’s cumulative update to Win10 Anniversary Update – build 14393.576 – is behaving itself. As far as I can see, it solves that myst
[See the full post at: Windows 10 1607 patch KB 3206632 solves the ‘dropped internet connection’ bug]

Reply | Quote

Replies

Since installing KB3206632 yesterday I’ve had no problems. My version has been incrementally increased to 14393.576. It seems that the Windows 10 CDPSvc fix has done the trick.

I’m now hoping that Microsoft leave the Current Branch for Business untouched for the next few months.

Today Microsoft Office 2016 has updated itself to 7571.2075 and again, no problems.

Article from El Reg on the same:

http://www.theregister.co.uk/2016/12/14/microsoft_windows_10_dhcp/

Reply | Quote

Alas, you can bet version 1607 (which is what I assume you mean by “Current Branch for Business”) will be updated next month. Count on it.

Reply | Quote

Just one question? Why would anyone want the mess that Windows 10 has on their computer UNLESS they are a tester?

Reply | Quote

Reply | Quote

I hate to admit this, but 10’s a really good OS. The general improvements they’ve made, the small stuff, the small tweaks – it’s all really solid. The problem of course is that a) control over updating is basically removed and out of the hands of the Power User/SysAdmin, and b) because of that, when Updates inevitably break things, those Power Users/SysAdmin are left running around like chickens with their heads cut off, running damage control on MS’ behalf (when it should be MS doing it).

I like 10, I just hate accepting the terms & conditions (and concessions) required to use it.

Reply | Quote

CBB 1607 was updated this month:

https://technet.microsoft.com/en-us/windows/release-info

Reply | Quote

They have a PC circa 1980 which only supports 4 colors.

Reply | Quote

Right. As I understand it, the CBB 1607 and the CB 1607 are basically the same thing. KB 3206632 updates both.

Reply | Quote

I agree with you – but also note that I don’t like the data gathering.

Basically all of my objections are still in place, with a few minor modifications.

http://www.infoworld.com/article/2972298/microsoft-windows/10-reasons-you-shouldnt-upgrade-to-windows-10.html

Reply | Quote

Woody, you’re to be commended for striving to separate the truth from the chaff.

That’s rare (if not nonexistent) amongst todays online writers, who’d rather be paid to make things up than to report on reality.

-Noel

Reply | Quote

I’ve been having trouble, myself, discovering enough “good” in Windows 10 to offset these major things:

1. Regular disruption, even on the Current Branch for Business, of the OS. This requires a lot of rework every time they put out an in-place upgrade – and the “Creator” edition is just around the corner so prepare to do it AGAIN.

2. Loss of control. Clearly Microsoft no longer wants us tweaking/augmenting/controlling our own systems. “Windows as a Service” is the antithesis of everything that made Windows tolerable and even desirable in the past.

There has always been a lot of benefit to “keeping current”, even if it’s largely intangible. Today we have operating systems that will just run as long as the power is applied – that wasn’t always the case. But we’re FINALLY here. Even Vista, after a few years, was ultimately stable.

So why does Microsoft insist, NOW, after all the effort that went into solidifying the OS, on regularly disrupting it (daily/weekly to reboot for updates, several times a year to replace the whole system)? That just doesn’t make sense.

-Noel

Reply | Quote

Weekly reboot for updates is a bit of a stretch, but DAILY?

Reply | Quote

“See any other “Microsoft broke DHCP with a recent Windows update” drivel? We don’t know how the bug originated, but it most certainly didn’t result from a “recent Windows update.” Please post a link in the comments. Fake news. Mumble mumble.”

All three articles you linked say that the exact cause is unclear.

Reply | Quote

Hmm, LTSB (Win 10 ENT LTSB & Win 2016) should be updated at the same level. There is a delay in publishing the recommendation for LTSB as it appears.

Reply | Quote

Ars Technica (not Peter Bright) – “Microsoft has quietly fixed a software update it released last week, which effectively prevented Windows 10 users from connecting to the Internet or joining a local network.”

Wrong.

ZDNet (not Mary Jo) – “Microsoft has issued a patch to resolve problems caused by a Windows update last week”

Wrong.

Bogdan hedged his hed (“Internet Connection Issues Caused by Botched Update”), which is wrong, but this part is accurate – “At this point, it’s still not clear which update caused some computers to be unable to connect to the Internet, but there were users claiming that a previous cumulative update, KB3201845, was the source of the bug.”

Reply | Quote

Yeah, you nailed it pretty much right on the head.
I’m more angered by the lack of update control, but the non-trackable telemetry and the force-feeding of Start menu apps and garbage are both other fairly big turn-offs for me. I like the OS, I just wish it was possible to run it un-connected (like 7).

I tried to like 8/8.1, but ultimately found out that for everything I could fix or work around, I was basically making it like 7 – so why bother? 10 is in the same boat, although 10’s boat has a few holes, a torn sail, and a broken oar.

Reply | Quote

I was affected by the TiWorker.exe high CPU looping and never ending on few computers (not all). The Setup Event Log logs this behaviour where KB3206632 keeps changing state, but never reaches the Installed state. This creates a potential issue with overheating the CPU after few hours, very much like the old issue with svchost.exe high CPU in Windows 7 lasting many hours.
The solution is to download the full package from the catalog and install, allowing enough time for TiWorker.exe to complete the post install cleanup tasks, which take about 10-15 minutes, depending on the CPU and Disk performance. The completion of the post install tasks can be monitored in Task Manager, Event Log or C:WindowsLogsCBScbs.log. The best practice is to perform the required restart only after all the post install tasks are completed, i.e. TiWorker.exe gets quiet for few minutes in Task Manager.

Reply | Quote

Are you saying that you have seen the TiWorking.exe process sometimes continuing doing stuff in the background (e.g. clean up) even after the GUI may have already indicated all patches finished installing (asking for a reboot if needed)?

Reply | Quote

So if we don’t know what caused the dropped Internet connection issue, how do we know that 3206632 fixed it?

Reply | Quote

There have been issues with TiWorker.exe and high CPU usage going back several years.

Reply | Quote

The number of reports has fallen off drastically.

Reply | Quote

Overall, or for Windows 10?

I understand Windows 8/8.1 systems had the issue as well…so a Windows 10 only patch wouldn’t help them.

Reply | Quote

This is not an issue, this is normal and desirable behaviour.

Reply | Quote

The symptoms reported have been around for many, many years. A small number of people have reported the problem – and it’s had many different sources.

But there was a big upswing in reports a week ago, from those running Win10 1607. The patch only solves the problem for them.

Reply | Quote

lots of machines on our w10 1000 +/- computer network choking on what appears to be KB3206632. Partially installs then IP errors occur, and computer can no longer obtain valid IP address to be on network. Can shutdown, reboot etc. multiple times and it does not install. One did finish today after 5 restarts and we were able to see that it was the update that was holding IP up. No idea why it decided to install on that 5th or 6th restart. Our current strategy is to reimage but as the numbers increase we can’t keep doing this. Not yet able to determine why some will install KB3206632 when rebooted and others will never finish installing it.

Reply | Quote

Oy. Have you reported this to Susan, patchmanagement.org?

Reply | Quote

no

Reply | Quote

I’ll send it to Susan for you, if you like, but you’d be much better off subscribing to patchmanagement.org and submitting it yourself.

Lots of people there who know this stuff far better than I. (Including abbodi and ch100 and several others you see around here.)

Reply | Quote

thx

Reply | Quote

I second Noel’s post. In just the short time I’ve been reading (today!) after the InfoWorld article, I’ve been thinking “if only I’d found this source earlier, I’d have been spared all those looks/complaints/diatribes about my language from my spouse, & it certainly would have cut down the support burden from my Mother-in-Law who believes she has (in me) a shortcut to Redmond…”

Kudos, sincerely!

Reply | Quote

No, this is not preferable. Coupled with the autocratic update & installation logic in [at least] Windows 10 this is absolutely unacceptable. Microsoft need to understand that this (my/our) machine IS NOT theirs. It is ours. Foisting a (sometimes) tens-of-minutes disruption on the owner of the platform speaks of a hubris which defies justification, especially given the number and severity of errors introduced by the update logic alone. In no way can it be considered “regular behaviour.”

Reply | Quote

This is Woody trying to be modest.
Woody is also a contributor to patchmanagement.org and his blog and InfoWorld.com articles are quoted often over there.

Reply | Quote

@SteveK I replied to this here https://www.askwoody.com/2016/patch-tuesday-for-win7-and-8-1-brings-order-but-its-still-too-early-to-install/#comment-111434

Reply | Quote

We manually installed KB3206632 (64-bit) using a flash drive. It required several reboots to take. Still looking at no network. Showing actual IP and not 169 address. Network connection Details match working matching good computer other than IP addresses.

Ping 127.0.0.1 Reply ok
Ping machine IP Reply ok
Ping anything else – General Error
Ipconfig /flushdns
” /registerdns
” /release
” /renew
netsh commands don’t solve it
Multiple reboots don’t solve it
Changing all firewalls to off doesn’t solve it.
Using Windows Defender as AV
removing and replacing drivers doesn’t solve it.

Some computers can be resolved by up to 4 to 6 reboots. Some also require netsh commands mixed in with reboots.
If network cable is removed icon goes from yellow “no internet” to red X. Other machines on VLan having no problems. This computer is our worst case on this issue.

Reply | Quote

Susan is asking me for your email address. It’s listed (but hidden) with your post. OK if I send it to her?

Reply | Quote

yes it is Ok

– we are checking the routers right now to see if this most troublesome machine has been blocked by the router before we manually forced the KB on it.

Reply | Quote

A quick update:

Microsoft* have now declared 1607 (14393.576) as LTSB in addition to it being CBB.

They don’t normally update it to LTSB status unless it’s ready… although how they can know this after so short amount of time I don’t know.

* https://technet.microsoft.com/en-us/windows/release-info.aspx

They’ve also updated* their main ‘Update History’ site.

* https://support.microsoft.com/en-us/help/4000825/windows-10-update-history

Reply | Quote

Good catch! I wonder when they promoted 1607 to LTSB?

Microsoft’s very convinced that 14393.576 is a solid build. I think they’re right.

Reply | Quote

Looks like they are getting ready for Creators Edition. Setting the base to fall back to.

Reply | Quote

Not for Enterprise users.
There are at least 2 major bugs in the server – 1. VAMT not working yet https://blogs.technet.microsoft.com/askcore/2016/10/19/windows-server-2016-volume-activation-tips/
2. WSUS client not working on Server 2016 and Windows 10.
In relation to the last one, the updates take too long to install and in many cases they never complete unless installed manually.

Reply | Quote

Ouch!

Reply | Quote

… and number 3, although not a big one: the 3.99TB bug surfacing now and then in Disk Cleanup

Reply | Quote

Some Windows 10 computers automatically update KB3206632 while other Windows 10 computers (presumably also set for auto updating) must
manually download KB3206632 and install it. Why is that?

Reply | Quote

I love the response to update Windows 10. HoHo. Since I can’t get an internet connection how would one do that. Bev

Reply | Quote

“I tried to like 8/8.1, but ultimately found out that for everything I could fix or work around, I was basically making it like 7 – so why bother?”

With 8.1, you’ll get a few more years of security patches than you will with 7. That’s a big benefit of using 8.1.

Reply | Quote

It is a problem, but as far as I understand, the Internet connection can be easily resolved and made stable long enough by taking simple steps which have been documented. I have not been affected, so I may be biased in my post.
How do you get to this site and post if you don’t have an internet connection? With a tablet or phone?

Reply | Quote

Use a different operating system then. Microsoft will not “understand” individual requests when there are literally hundreds of millions of other users out there.

Reply | Quote

@Steve K
Any positive outcome to your issues in relation to installing KB3206632?

Reply | Quote

I took ch100 saying preferable as in its preferable to let TrustedInstaller.exe/ TiWorker.exe complete its post patching functions before rebooting. Not as in preferable to let MS control things. I would love to have full patching control back; it’s why I don’t have any Win10 in production yet.

Reply | Quote

do we know that 3206632 fixed it? Did not on mine so did the following with admin command prompt
ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns
nbtstat -rr
netsh int ip reset all
netsh int ipv4 reset
netsh int ipv6 reset
netsh winsock reset <Enter

Reply | Quote

I got to this site by using one of the 1000 computers that does work in our Enterprise.

The machines that are failing do not all respond to KB3206632 as a fix. We are still trying to find a sequence that works each time. It seems that the KB hangs itself trying to install sometimes.

Reply | Quote

the two already this morning responded to

netsh winsock reset catalog

netsh int ipv4 reset reset.log

reboot

At that point the update finished installing and the TCP/IP worked.

Reply | Quote

I made a batch file with the text below in it to run as admin from a flash drive, and so far 5 of 5 today that had the IP problem all recovered. Windows 10 Enterprise.

netsh winsock reset catalog

netsh int ipv4 reset reset.log

shutdown.exe /r /t 00

Reply | Quote

I want to pass along that McAfee security may sometimes be the internet connection problem or part of it. McAfee has a support page on it. The similar Microsoft Win10 internet connection issue most recently involves a corrective KB3216755, bringing the 1607 build from 14393.693 up to 14393.726 along with numerous other issues. The MS Catalog has one for x64 and another for 32-bit. However without downloading this KB I first tried and was successful with a System Restore back to 1-27-2017 (soon after the January Win10 updates were done on this Dell). The rollback solely affected McAfee (according to System Restore). To my dismay I therefore cannot allow McAfee to update for a while. Many many thanks to this Ask Woody site for all the help through many trials I have personally experienced along with many others over the past couple of years. So glad the Windows updaters especially on my Win7 system seem to be working better after a year or two of agony. It seems Microsoft is making progress and I just hope their quality and tactics continue to rebound.

Reply | Quote