Win10 update breaks DHCP

[AlohaTech]

Wish I would have seen this earlier, I spent all kinds of time on this one before finding a solution. So far I have only seen this problem on one computer. The fix that I used that finally worked was:
Open command prompt as Admin
netsh winsock reset catalog
netsh int ipv4 reset reset.log
Restart PC

 

[ComputerRepairTech]

How hard would it have been to include a description in your post what this actually does?

Just shutdown but if you do it like that I believe it will do a full shut down instead of a hybrid shutdown.

 

[MudRock]

We started with removing the drivers, then resetting the network but easiest solution I've found for all the one we run across is a simple:

shutdown -s -t 0

Worked every time so far.

Doesn't work in any of the scenarios I've had so far.

 

[freedomit]

I just experience this on my home media PC running Win 10, shutdown and back on same issue but restart cleared it

 

[KrustyTech]

i have had a few of these and

netsh winsock reset catalog
netsh int ipv4 reset reset.log

seems to do the job. I just hope after charging customers that it's a permanent fix as I hate the comebacks !!

 

[Philippe]

3 more today. You gotta love this kind of present
Thank you MS
>netsh winsock reset catalog
>netsh int ipv4 reset reset.log
=> the way to go

 

[NOLA IT Pro]

This may fix the DHCP problem.

https://support.microsoft.com/en-us/help/4004227
"Addressed a service crash in CDPSVC that in some situations could lead to the machine not being able to acquire an IP address. "


This reddit thread has good information on Windows 10 updates.

https://www.reddit.com/r/Windows10/comments/5i57fr/december_windows_10_cumulative_updates_kb3206632/

 

[Diggs]

Everyone see the update go through their Win10 machines to fix this right?

https://www.extremetech.com/computi...Extremetech)&utm_content=FeedBurner+user+view

All better (until next time....)

 

[cypress]

i have had a few of these and

netsh winsock reset catalog
netsh int ipv4 reset reset.log

seems to do the job. I just hope after charging customers that it's a permanent fix as I hate the comebacks !!

Just had a client call me with this issue and this worked. Found the update as well.

 

[Galdorf]

Easy fix download KB3206632 and install
or restart, select the Start button from the taskbar, click the Power button and choose Restart (not Shut down)
and check windows update to install KB3206632.

It is really annoying had it happen to my machine at work i suspected a bad windows update getting to the point you can't trust updates at least for a few weeks.

 

[ohio_grad_06]

And yet they are now going to ram updates down your throat like it or not

 

[Mick]

Small word of caution. I manually installed this update on a clients new-ish HP DTop, (it is hefty - nearly a gigsworth) and it took a good hour to complete. Does seem to have worked, though.

 

[HFultzjr]

Small word of caution. I manually installed this update on a clients new-ish HP DTop, (it is hefty - nearly a gigsworth) and it took a good hour to complete. Does seem to have worked, though.

Customers are really starting to get peeved at these large Updates/Upgrades. Not everyone has or can get a decent connection in my area. A lot are 1.5-3 MB service.

 

[Diggs]

Easy fix download KB3206632 and install

My personal machine (Asus laptop) is choking on this update every night. I'm glad it's not a client's machine 'cause so far I can't get it to go.

Ran full Windows Update Diagnostics download
Ran full DISM repair on the image.
Keep getting "Error 0x80073701" on the update.

Still no go. Hmmm......

 

[HFultzjr]

My personal machine (Asus laptop) is choking on this update every night. I'm glad it's not a client's machine 'cause so far I can't get it to go.

Ran full Windows Update Diagnostics download
Ran full DISM repair on the image.
Keep getting "Error 0x80073701" on the update.

Still no go. Hmmm......

I feel your pain!
Sucks, doesn't it?

 

[YeOldeStonecat]

I've had many of these in the past 2 weeks.....
I simply have the client run the CMD prompt as admin, IPCONFIG /RELEASE and then IPCONFIG /RENEW
Boom! They're online, valid IP, good to go. No need to reboot or rebuild network components.

I know usually you just need IPCONFIG /renew and it already implies /release ahead of time...but on a rig or two it didn't work with just /renew, and it does every time for me when you do /release and then /renew. And the problem hasn't come back.

This seems to happen after the rig gets the bum update....it will fall offline, or not get a valid IP on its next reboot.

Also, I found a GUI way to netsh reset in Win10....if you bring up Network Settings, click on Status on the left side, scroll down a bit, you'll see a link for Network Reset in the clickable links in the center towards the bottom of that screen. Although I haven't needed that to fix this Win10 lack of valid IP issue.

 

[Mick]

I've had many of these in the past 2 weeks.....
I simply have the client run the CMD prompt as admin, IPCONFIG /RELEASE and then IPCONFIG /RENEW
Boom! They're online, valid IP, good to go. No need to reboot or rebuild network components.

I know usually you just need IPCONFIG /renew and it already implies /release ahead of time...but on a rig or two it didn't work with just /renew, and it does every time for me when you do /release and then /renew. And the problem hasn't come back.

Well, that's the trouble. First one of these I got (before I even knew about this problem) , that's exactly what I did*. Lasted about two days before it conked out again. Appreciate the reset tip, though - didn't know that one!

* Although, thinking about it, I may not have run the CMD prompt as admin. Most domestic machines, the user is an admin, so you wouldn't normally need to specify.

 

[fincoder]

found a GUI way to netsh reset in Win10....if you bring up Network Settings, click on Status on the left side, scroll down a bit, you'll see a link for Network Reset in the clickable links in the center towards the bottom of that screen

Thanks for this. I just tried and it's searchable too, so now we can just type (or have the customer type) "network reset" in search.

Someone still needs to confirm that it fixes the issue though...

 

[YeOldeStonecat]

Thanks for this. I just tried and it's searchable too, so now we can just type (or have the customer type) "network reset" in search.

Someone still needs to confirm that it fixes the issue though...

I haven't used that to fix the issue of this post...what has worked for me for the DHCP issue that this post talks about is simply do the ipconfig /release and then /renew at an elevated command prompt (not a regular prompt). The DHCP issue doesn't return after that. Has happened to my laptop (that I'm typing from right now), my wifes laptops (she called me with both...separate days of the week after this bum update went out, different networks..home and work), as well as many clients. I just walked them through the CMD prompt stuff over the phone.

The GUI method of doing the netsh reset I've used for those occasional "wireless NIC falls asleep" issue that I've seen on computers that were upgraded from Win7 to Win10. Multiple times a day, the wireless NIC appears to disconnect/fall asleep...and then the icon in the systray spins for a while...and then reconnects. So the end user experiences frequently short disconnects throughout the day....almost like the wireless NIC falls is quickly disabled and then re enabled all on its own. I have not seen this issue on clean Win10 installs, nor rigs that upgrated from 7 to 10 and then had all the appropriate updated Win10 drivers installed (like my laptop here...I frequently run Lenovo System Update so I'm always updated with drivers 'n BIOS).

 

[trevm999]

I know usually you just need IPCONFIG /renew and it already implies /release ahead of time...but on a rig or two it didn't work with just /renew, and it does every time for me when you do /release and then /renew. And the problem hasn't come back.

This is what I did before the other commands were posted in this thread, and the problem did come back... at least on the one computer I did it on.

The GUI method of doing the netsh reset I've used for those occasional "wireless NIC falls asleep" issue that I've seen on computers that were upgraded from Win7 to Win10. Multiple times a day, the wireless NIC appears to disconnect/fall asleep...and then the icon in the systray spins for a while...and then reconnects. So the end user experiences frequently short disconnects throughout the day....almost like the wireless NIC falls is quickly disabled and then re enabled all on its own. I have not seen this issue on clean Win10 installs, nor rigs that upgrated from 7 to 10 and then had all the appropriate updated Win10 drivers installed (like my laptop here...I frequently run Lenovo System Update so I'm always updated with drivers 'n BIOS).

I've seen this on Windows 7, my solution was to change the advanced windows power settings.