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.
setting the machine's IP address to 169.x.x.x
No no and more no, don't ever do that!
The local link IP range is 169.254.0.0/16, aka 169.254.x.x
If anyone is using IPs outside of 169.254.0.0/16 but within 169.0.0.0/8 like is stated, you are trampling on other peoples IP addresses!
You don't want to be Linksys do you? No, no one wants to be Linksys, so stop that.
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!!!
Standard M$ textbook answers... 1- Reboot, 2- Reinstall Windows.
I really feel for their users..... really I do. Poor poor them. *Continues using apt-apt update*
Try and explain to a typical Social Media / Netflix user how to do ipconfig /renew and get back to us on that...
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...
My computer is used for retail. The last time there was an updat it too about 4 hours to get my system back. I've shut down and turned back on and nothing. I can't believe this is happening on a Saturday in December.
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!
I have experienced Wi-Fi connection drops as well using Windows 10 and was thinking that something wrong with the router but I guess it may not be the issue.
It has dropped WiFi since Windows 8
Why would a business person not be subject to domain control and WSUS even on a mobile PC?
They're just trying to keep up with Google. More than once, I've given a sales person a locally installed demonstrator for some web app that was working when they left the office, and then the demo was undermined when they connected their laptop to the Internet while out of the office and Chrome self-updated and broke something.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
At my work the Linux techs have a joke thatall you need to train a Windows tech is the "five R's of troubleshooting Windows"
1. Restart the application
2. Reboot the server
3. Reinstall the application
4. Rekick the server
5. Redhat
N/T
In the maths, "TOTAL" = 100% -- not 90%.
It little behooves the best of us to comment on the rest of us.
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.
I disabled cortana because she's a nazi sympathizer.
The headline is not only misleading it is downright incorrect!
Welcome to Slashdot!
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)
You do realize that not every business is large enough to justify such a system right?
You know I can see the reasoning by hind Window's current choice to take the users control away in terms of updates and why the want to force you to do so... but I'm sorry, how many critical bugs like this must we suffer until we can have our control back? How many times are we going to suffer the corporate whims of the Microsoft corporation before enough is enough?
I noticed just recently that my Windows 10 machine wasn't connecting to either the wired or wireless networks when I moved between home and office. IP addresses were defaulting to Microsoft's 169.254.0.0/16 range, as happens on Windows when DHCP attempt fails. Doing ipconfig /release and then ipconfig /renew would restore operation.
The problem seems to stem from "fast startup" being enabled under Control Panel -> Power Options -> Choose what the power buttons do. With this feature enabled, performing a shutdown doesn't really shutdown the computer, it basically just hibernates. I'm not terribly surprised that acquiring an IP address, hibernating the machine, then waking from hibernation on a different network might cause a networking issue, but for whatever reason this wasn't causing any problem until just recently.
THat will only work ... until the lease is up again.
A more permanent fix is to type
netsh winsock reset catalog
netsh int ipv4 reset reset.log
http://saveie6.com/
This happened to me twice this week. I had to do a battery pull from my laptop to get it to work right. A shutdown still did a fast boot so it didn't work Also an electrical contractor on a job site came in earlier this week to say his wifi didn't work. I had to do a battery pull for him too after wasting 20 minutes resetting the wifi, etc.
Scott
... vulnerabilities have been found during this period. Have fun! Of course it might be theoretically possible that none of the websites that you host allow any form of code execution and your entire user space is up to date but that's just crazy - boasting about your uptime while keeping your kernel unsecured.
Last night my WIN10 updated. Don't have wifi problems, but a host of other. PulseSecure VPN client won't work now, I can't even uninstall it. Add remove programs from control panel does not open. I click on it and nothing happens. After booting a explorer window appears saying a drive is inaccessible; don't know what that's about, I don't have any usb dongle or sd card inserted. MS is trying so hard with Cortana AI, instead it should focus on not ruining basic things.
I dont quite understand the problem, ive been on windows 10 since about when it came out, i like it better than 7 and damn sure better than windows 8. i dont worry about the telemetry.. so what they see i like porn.. hopefully they will prioritize it! either way, i abuse my system, have had the same install over 3 processors 4 motherboards and 2 GPU's. I add/remove programs alot.. i RARELY have a problem that a simple reboot doesnt fix. and as of right now i have atleast a 7 day uptime, which was almost unheard of when i was running windows 7. they have done better with windows 10 than with the rest of windows os's over the years. the fact that there is no picking and choosing updates per package kindof sucks but other than that it works as expected from a microsoft product. the main thing that pisses me off is when it erases the boot sector infavor of its loader over grub, found a way around that. windows on sda linux on sdb.. tell bios boot from sdb. havent had an issue in almost a year because of it
I probably ran into this at a client site on Friday, but I blamed it on the ancient WiFi router that they'd reconfigured to use as a switch. Ancient as in "hardware predates WPA2 and the plastic has faded to grey," wasn't handing out DHCP, and had nothing connected on the WAN side.
One cheap 5-port switch and a reboot after removing a couple of unrelated pieces of junkware that I noticed and the PC and printer were back up.
fencepost
just a little off
I thought this was just on HP laptops but it seems to be widespread. First my daughters, well before December 7th, then mine. Opening a command window and using 'ipconfig /renew' works for me. Everyone here knows that but maybe some guests might not.
Solution is more than a cold boot. Deleting all the remembered network connections and renewing connections (Yes, you have to re enter the wifi codes) solves the problem.
It looks like an update changed the expected data format in the registry for remembered wifi connections. Old data doesn't read correctly into the driver for a reliable connection.
NRRPT/RCT
I have noticed wifi dropping per say; upon startup I've noticed I have to manually connect to my home WiFi, even with auto connect selected
"They're just trying to keep up with Google."
Google has become an abusive company, and Microsoft wanted to add Google's abuses to Microsoft's long list?
Explanation of Google's former motto, Don't be evil.
I've done all of the Windows OS, as part of my job. I'm retired, now.
I've never had any issues with a single version of the desktop after 3.1.
1.0 was a bad joke.
3.0 had a fatal flaw in that File Manager refreshed the entire folder structure on the drive (called "directory" back then") when opening different folders.
They fixed that with 3.1 so that File Manager just re-swept the current folder.
That was when I rolled it out at Mobil Oil Corporation.
I never had issues with Windows ME, Vista, or 8 because I banned them from the workplace and never had them at home.
I liked 95, 98 (ran that one into the ground) LOVED XP and still use it. There's a registry hack that makes XP think it's a legacy OS embedded into ATM machines so it still gets security updates to this day.
I like, and still run, Windows 7, 8.1 (not 8 SP1).
I like 10 except for that goddam auto-restart. Any information on how to stop that and still get updates would be greatly appreciated.
For servers, there's a legacy app still running on a Windows NT Dell box where I retired. The backup tape died long ago and the USB ports are 1.0, so we do over-the-wire backup to another server via batch copy.
All the servers up to, and including 2008 were nice; no problems at all. I never rode a 2010 or higher.
I had to pre-approve updates because every now and then Microsoft would give me one for something I didn't have.
--
Interestingly, and pre-Windows servers, Novell (up to 3.2) would bail and "server down" was a common phrase. The users were used to it and it was just a way of life.
The Novell 4.1 I had was not Y2K compliant and that's when I switched to Windows servers.
--
So, all-in-all, I've had good luck with Windows.
It little behooves the best of us to comment on the rest of us.
The update left my wife's laptop with limited netwrok access: she was connected to the network, but had no internet connectivity. The following lines, typed in an admin prompt, fixed it:
netsh int tcp set heuristics disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global rss=enabled
this is what fixed the issue when it happened to me on a laptop with win10.
all other suggestions here did nothing, once i tried to reconnect to the wifi AP it would get a self assigned IP address.
funny timing too because i had just upgraded my internet modem and was recreating my wifi AP so i spent some time verifying other devices did not have this problem (one of them was a win 7 desktop).