Win10 update breaks DHCP

Yep just had a call about this and rebooting the PC didn't fix it so had to static set the IP. Wish I had seen this thread first.
 
when did this begin? I actually had a case like this on 12/8 but i use dsupport so i have a fix internet button on my little digital business card on all my clients computers.
 
This issue is inline with my thread here. And though it has subsided a bit, I am still getting calls about the issue here in the US. I have had some that no matter what I did, the only solution was to do a complete N&P. For me, 98% of the problem was that a pushed down update for 3rd party drivers was not only breaking DHCP (No valid IP) but was also completely removing the LAN drivers but not affecting anything Wi-Fi related.

What I have done for recently installed Windows 10 machines (and ones that I could fix) as well as currently servicing machines not affected yet was to turn off the ability to download manufacturers apps. That has helped a lot.

Do that by the following:
  1. Right click Start (Windows icon)
  2. Click System
  3. Click Advanced system settings (left side)
  4. Click Hardware tab
  5. Click Device Installation Settings
  6. Check No
  7. Save, exit and reboot.
The above seems to work fine and have not been able to recreate the issue afterwards. Granted its not a cure-all solution. Many times just running SDI to reinstall the LAN drivers has worked. A point to note is that nearly every instance I have had the customer has had the Windows 10 Anniversary edition installed. Only one issue have I had with the 1607 build.

You can also (on affected machines) use the following through command prompt (run as admin) or make it a .bat file.
  1. netsh int ipv4 reset reset.log
  2. netsh int ipv6 reset reset.log
  3. ipconfig /flushdns
  4. nbtstat -R
  5. nbtstat -RR
  6. netsh int reset resetlog.txt
  7. netsh int ip reset
  8. netsh winsock reset
And here is the .bat file you can make. Copy & Paste into a .txt file and save with the extension: .bat

@echo off
echo Quick fix for broken DCHP!
echo WARNING: My or may not work. Use at your descretion!
pause

netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log
ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset resetlog.txt
netsh int ip reset
netsh winsock reset

echo Type EXIT then reboot the machine!
I hope this can help someone.
 
This has to happen the Saturday that I am here all alone. I'm just glad I saw this thread before the calls started coming in. Not too many calls but saved me a lot of troubleshooting time.
 
The latest Win10 update is breaking DHCP on some machines which of course breaks everything externally. Seems it's just a Brit thing at this point......

http://www.theregister.co.uk/2016/12/09/mysterious_windows_10_networking_bug/
In New Zealand it started last Thursday, but I did find that the DNS was being changed to 192.168.0.1 and the internal gateway was 192.168.1.1. Without making any other changes going into the network properties and setting dns to 8.8.8.8 and magic back on line. Doing a netsh winscok reset didn't make any difference

Then this client didn't know the password for the modem so reset modem and reconfigure change DNS on clients back to obtain automatically and it all worked again.
 
Also finding this problem started for us on Thursday here in NZ.

We found restarting the computer twice sorted this out for some reason. (We did some Voodoo though by holding a Ubuntu boot drive over the unit while rebooting it)
We had four units in today with the issue.
 
I have now fixed total of 27 machines with this issue. And I have another 5 on the bench with a half dozen calls backs I need to do for the same issue. I am totally backed up with work for fixing this issue and that does not include my other clients that require servicing. :mad:
 
Yup, I have a few of these now...I was wondering wth was going on. Thanks for the heads up! I would have wasted a lot of time looking for rootkits...

YAY Microsoft!
 
Had my first brush with this this weekend. Five separate machines, all Win 10 Home, all with "The internet's not working" problem. Various routers and ISPs, so pretty damn sure it's a M$ problem. The fixes described above have helped (thanks, guys) but I'm waiting to see if it's a long-term fix, or whether they crap out again after a day or so (which has happened with at least one of mine, so far)
 
Really?

I've just spent most of the day apologizing for Microsoft. Not fun, and definitely not how I want to make money.

With any luck this fiasco will help push Microsoft away from mandatory cryptic roll-ups and back towards fully documented optional updates with well-separated functions. But I'm not holding my breath waiting for it.

I have to agree with you, with that logic we could just plant viruses to get work from our clients. Could remote in to their routers and break the internet to get calls, definitely not how I want to make money either.


Skickat från min iPhone med Tapatalk
 
I think I'm on call number 48 of these. Trying to explain over the phone can be challenging with some of my customers. Many have just agreed to wait for me to visit them and set manual IP/DNS. Diary is now full for the next week and a half!
 
Huh... I've had several of these over the last week.
I was even at my girlfriends place last night and her daughters had the same issue.

My fix, which has worked on all of them.
Uninstall all wireless network drivers and reboot. It re-installs them on startup and essentially forces a reset of the networking.
 
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.
 
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.

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