Hi,
I looked on winbeta.org and couldn't see the announcement. Could you share URL?
PS: Unfortunately I'm getting slow on the 2Ghz as well
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have an Apple Airport Extreme 802.11ac wireless router at home and am only connecting at a max of speed of 72Mbps (usually closer to 11Mbps if I'm more than 20 feet away from the WAP). I have two other 802.11ac laptops at home (Samsung AB9+ and rMBP) and my two other computers are connecting up at 800Mbps+ and pulling down the same on Internet speed tests; yes, I have real GigE connectivity. Is anyone else having these problems?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi,
I looked on winbeta.org and couldn't see the announcement. Could you share URL?
PS: Unfortunately I'm getting slow on the 2Ghz as well
according to the winbeta site MS announced today further wifi fixes coming in the future. It's nice they are continuously trying to sort it out. I've had many devices where oem not so supported.
I split off my 5ghz on my asus 68w ac router to a different ssid than the 2.5ghz to see which it would connect and test speeds. It seems my sp3 i7 won't even connect to the 5ghz channel.
The connection to the 2.6hz is just dandy and it'll dl at 6MB/s so no complaints really. be nice if they work it and get the uber speeds of the ac working.
Looks like no WiFi driver update this time around...
This article claims that all WIFI issues has been resolved in Windows 10...
Unfortunately I don't want to install the developer preview on my Pro3, (I have it on my Pro2).
Key reason is because if anything goes wrong then the first comment on any of these boards will be, "have you tested it with the original OS, as Windows 10 preview is not supported)
(Plus it's not unreasonable to assume that something released should work)
I repost because Zach_T does not say Microsoft is continuing to look at this. He implies that 2.4GHz problems were fixed in the September 9 release (although 2.4 plus 5 GHz dual-band issues remain), but they were not for me.
Yes... +1 to that... the Zach-T post implies it's now fixed... whereas everyone on the thread is saying it's not.. (and possibly it was even the 9/9 update that *causes* the error)