Slashdot Mirror
New Bug In Windows 10 Anniversary Update Brings Wi-Fi Disconnects (infoworld.com)
Some Windows 10 PCs are now experiencing sudden drops in their Wi-Fi connections, with the Network Diagnostics tool reporting "Wi-Fi doesn't have a valid IP configuration." An anonymous reader quotes InfoWorld's Woody Leonhard:
I've heard from many people who blame the Wi-Fi disconnect on Friday's KB 3201845, the patch (which still isn't documented on the Win10 update history site) that brings version 1607 up to build 14393.479. It's unlikely that the new patch brought on the bug because the large influx of complaints started on December 7 -- two days before the patch...
Speculation at this point says the disconnect results when a machine performs a fast startup, setting the machine's IP address to 169.x.x.x. It's an old problem, but somehow it's come back in spades in the past two days. I have no idea what triggered the sudden outbreak, as there were no Win10 1607 patches issued on December 6, 7 or 8.
Microsoft acknowledged the problem Thursday, recommending customers try restarting their PCs (or performing a clean start). Woody writes that it looks like Microsoft's latest Windows 10 patch "didn't cause the bug. But the patch didn't fix it, either."
Speculation at this point says the disconnect results when a machine performs a fast startup, setting the machine's IP address to 169.x.x.x. It's an old problem, but somehow it's come back in spades in the past two days. I have no idea what triggered the sudden outbreak, as there were no Win10 1607 patches issued on December 6, 7 or 8.
Microsoft acknowledged the problem Thursday, recommending customers try restarting their PCs (or performing a clean start). Woody writes that it looks like Microsoft's latest Windows 10 patch "didn't cause the bug. But the patch didn't fix it, either."
Wifi disconnects after OS updates. My god, they really are copying macOS updates, right down to WiFI bugs.
I have this problem as well. Running DHCP on the router I use. When I do an IP config I see a MS assigned address. Doing an IPCONFIG /RENEW gets a new IP address without the reboot.
Forced Windows updates must bring constant excitement to business people at travel. You never know, if the machine works after connecting it to network. And nobody in IT is there to help them.
I had the same problem on Wednesday with a wired connection. A reboot fixed it (after a lot of head scratching).
wot no sig
Hold the shift key down when you reboot, and keep it down until the login screen.
Source: I own an ISP.
...Steve
Hello,
This issue has been going on for more than two days. Reports of it date almost a month:
https://www.reddit.com/r/sysad...
https://community.spiceworks.c...
Although reports of it in Microsoft's support forum are more recent:
https://answers.microsoft.com/...
https://answers.microsoft.com/...
https://answers.microsoft.com/...
The December 9th patch - https://support.microsoft.com/... - might contain some kind of fix or workaround, although I don't see anything mentioned on the page which maps to the issue.
Microsoft is keeping customers up to date with a page on its support forum. Here's Microsoft's short link to the page: https://aka.ms/netcom
Regards,
Aryeh Goretsky
Dexter is a good dog.
...my keyboard wasn't working. I had to unplug it and re-plug it back in. Annoying. I haven't tried out the WiFi issue yet, because I wire my network connections everywhere possible.
The keyboard not working is a strange issue, though. I don't need a "fast reboot" option - with my system drive speed, I boot in 6 seconds from power button on to desktop on a cold boot. I don't need sleep mode, hibernation... I just need proper memory management for longer up times.
I've been on the Windows 10 Insider program for quite a while, and keep one work machine on a stable build and the other in the Fast ring. For a lot of our production machines, we're going to go with the next spin of Long Term Servicing Branch for just this reason. I'm not happy that you have to give up all feature updates for years in order to get an OS they're not going to be changing behavior on every month.
Having seen both the stable and super-new builds running similar application loads, it's obvious that Microsoft is skimping on code quality in both, sacrificing it for fast feature releases. However, very few "breaking" bugs make it into their stable (CBB) builds. I'm not happy that the home consumers have to deal with these though...they have no choice. And when it's something like breaking wireless, that's a big deal -- most users are at least on laptops now if not tablets.
On balance I think they made the right decision for the overall market on patching. Unpatched Windows home machines are just asking for ransomware or a botnet takeover, and consumers have no clue how to manage their machines. For business, I think they made an OK compromise, but wish they would make the updates not be all-or-nothing. The user population I support runs hundreds of applications from sources we don't control, and right now on Windows 7 we get a few security updates a year that break them, some in ways we can't fix without getting the vendor to make a change. In the old pick-and-choose model, we would figure out which monthly updates didn't break the application set and apply them, then wait for a time we could apply the "bad" ones when an application drops off the radar or gets fixed.
When your OS vendor tosses their Q&A and basically uses their user base for testing out their shitty product.
Still very happy with Win7, and there's ZERO need to upgrade at this point.
Chas - The one, the only.
THANK GOD!!!
The Register has the scoop on it.
Some users report typing:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
Has repaired their TCP/IP stack.
Unrelated, I just woke up after I rebuilt a computer last night. I am greeted with a Windows 10 setup screen. I also have an older saved Windows 8.1 acronis image for same cpu and motherboard. I was just wondering if I should bite the bullet and go Windows 10 as I work in IT and need to know it ...
However this story scared me and got me wondering if that is really a good idea? What do you all think? Hmm
http://saveie6.com/
"Microsoft acknowledged the problem Thursday, recommending customers try restarting their PCs"
Almost 25 fuckin' years after releasing Win 3.1, and their trouble shooting advice is still "have you tried restarting it?"
On the other hand, I have a Linux server that just passed 1015 days uptime with no restarts or reboots. It hosts about 50 websites and runs 24/7 with constant activity. Windows couldn't even dream of that kind of service.
Just cruising through this digital world at 33 1/3 rpm...
The issue is not ipv4. It's the corrupted windsock catalog. Ipv6 is impacted as well. The solution is to reset it with nutshell from an elevated command prompt or PowerShell:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
Or use an older more reliable OS until MS hires a QA team again and stop relying on Joe Six packs as their QA team
http://saveie6.com/
You loved last year's gift of privacy invasion so much I didn't know how to top that. Then I thought of disconnecting your WiFi so you would lose access to the single most essential activity on your computer. I hope you enjoy it!
Or just don't run Windows 10.
Thankfully I have a copy of acronis with an older 8.1image with updates disabled to just download. I install them manually a month or so later.
I really did want to keep 10 and if works fine for a few weeks and I always run into a problem every other month or so. So damn frustrating. I NEED to learn 10 for work as we will migrate soon but shit too many problems??
http://saveie6.com/
Type cmd.exe into Cortana
Run program /release. Press enter /renew. Press enter
Type ipconfig
Type ipconfig
Press red close x in corner
Wifi fixed
i thought once I was found, but it was only a dream.
This.
If one computer aggravates, scoot your chair over to the other one.
It little behooves the best of us to comment on the rest of us.
As a long time Linux user I am glad that the Windows peasants are finally getting this feature that we have been enjoying for years.
(yeah I know, its the fault of the device manufacturers)