I've been having the same issue ever since I got my XPS 13 9360 running stock Windows 10 x64 (Build 14393). This did not happen on the XPS 9343 nor the 9350 (both did not have the new Killer Wireless 1535 card).
After every restart/hibernate/sleep - I have to manually reconnect to the network that was connected before the restart/hibernate/sleep.
One of the cumulative updates back in Oct or Nov seems to have introduced networking problems and Wi-Fi was one. Microsoft even put up a sticky trying to help folks get their systems back to normal.
Normal users don't have enough information to make a determination if the problem is because of their specific wireless adapter. Using an external USB adapter may allow normal operations, which would indicate your internal device.
You might check to see if there is any additional software which could be loaded for that adapter to help it auto-connect. Router firmware updates could also make a difference if you use one.
Checking the Event Viewer and comparing connection specific information may help track down problems.
Well, I can say that my system has had this problem since day one - I received the laptop in the beginning of November and it has never connected to a network automatically. I believe if this was the case for all XPS 9360's I would have heard about it by now?
I did check for newer drivers for the Killer Wireless 1535 adapter, and factory reset my Windows to no avail.
If you left click your wireless icon on the taskbar. Then left click your network and select properties you should have a good idea of what is happening.
Which band are you one, 5 or 2.4 .. Does the IP Address look normal are you showing an IPv6 address. You can compare the driver version to what you see online to make sure and driver update succeeded.
You get some additional info if you right click the speaker icon and open the network and sharing center. Go to change adapter settings and check the status of your Wi-Fi adapter. Look for the Lease info, when was it obtained and how long is it good for.
I am not a networking person so all I can do is guess. I have replaced all the Dell supplied Wi-Fi adapters on my systems. Luckily they all work fine, so hopefully you can find a solution to your situation.
My XPS 13 9360 (with Rivet / Atheros WiFi drivers) has performed exactly as desirable for release versions of Windows 10 (Home), across all aspects of the hardware environment. Only after the installation of the (at the time of this writing) current Windows 10 slow ring insider build did my trouble with WiFi auto-connect start.
At this time, I can only recommend to _not_ install the WiFi drivers provided by Dell for the Killer 1535 WiFi card (as these included the Killer network QoS / balancing / throttling manager driver). Do download from Rivet Networks the plain drivers, and just the plain drivers.
Apart from that, I have only minimal amounts of coil whine (on an i7/16 GB/QHD device), which drowns in the background noise of any office - this is very manageable. Reviews complain about the "quality of the sound" emitted by the built-in XPS13 speakers. To be frank, any _laptop_ will have these issues with such small speaker drivers.
At this time, my most serious complaint is about the Windows 10 operating system (Microsoft software!) having challenges with mixed DPI multi-monitor configurations - and even here, I seem to be making progress by making the lowest DPI screen the primary screen upon "docking".
FWIW; I have not yet tried to reassign the IPv4 network interface priorities (netsh interface ipv4 show config). I have two virtualizers (VMware Workstation, Oracle Virtualbox) installed. This may, or may not, improve matters.
At this time, I'd rate my experience at 8.5/10, the Dell hardware environment at 9.25/10, but only because I do not yet know how to squeeze the remaining 0.75 out of the system.
I am coming from a Haswell-generation, matte display, Full HD Toshiba Satellite Z30-A, which I'd rate 9.5/10 for weight, size, connectivity, 16 GB of memory. And that for the cheap bastardized consumer version of the grossly overpriced Portege business version. Truth to be told - if a Kaby Lake version of that laptop had been available to me, the Toshiba it would have been, again. Matters being as they are, the XPS 13 9360 was the device of choice. I seriously hope that over the course of the next 12 months, all parties involved (Dell, Microsoft, Intel, Qualcomm / Rivet Networks) will work on making the XPS 13 9360 as lovable as the Toshiba Z30-A.
FWIW, I currently suspect that network interface metrics play a role, combined with changes in the Windows 10 insider build, combined with my sufficiently extensive use of virtual network adapters.
At this time, I have no reason to blame Dell hardware, only the slightly of all chances for the problems originating from Rivet Networks drivers, with the likely culprit being the insider build of Windows 10 home.
I am having this same issue on my xps 13 9360 with killer 1535 adapter. It is not related specifically to just insider builds. I am running the latest version of windows 10 and the latest killer driver
Well I'm on the stock build that came with the XPS, with no virtual network adapters and I can't get the thing to work. I downloaded the drivers from Rivet networks (www.killernetworking.com/.../other-downloads - on the right). My network card is now showing v. 12.0.0.285 from 20-Oct-2016. Is this what you mean @shoffmeister?
I'm pretty sure this is the same version I had before...
I was using these very drivers successfully, indeed, to auto-connect - before my upgrade to the insider build. The benefit of these drivers is that they do not contain the Killer bandwidth management code, which for my scenarios would not add any value.
The only thing that changed matters for me (into the wrong direction = no auto-connect any more) was the Windows insider build.
Over the past couple of days I have been running with the changes applied as above. WiFi auto-connect works (again) flawlessly, survives access point switches, survives reboots, cold starts, sleeps, hibernates, ...
For now I blame vagrant / Oracle Virtualbox, or Microsoft Connected Standby.
I am still running VMware Workstation 12.5.2 on the aforementioned Windows 10 insider built, with bare KIller network drivers (and without the Killer funky traffic shaper)
namnoops
15 Posts
0
January 9th, 2017 00:00
I've been having the same issue ever since I got my XPS 13 9360 running stock Windows 10 x64 (Build 14393). This did not happen on the XPS 9343 nor the 9350 (both did not have the new Killer Wireless 1535 card).
After every restart/hibernate/sleep - I have to manually reconnect to the network that was connected before the restart/hibernate/sleep.
shoffmeister
1 Rookie
•
53 Posts
0
January 9th, 2017 03:00
FWIW - this seems to be a problem associated with Windows insider builds (AKA "Windows 10 beta releases").
Things appeared to be working well (after a complete rebuild of the XPS), only to deteriorate after installation of the insider build.
namnoops
15 Posts
0
January 9th, 2017 06:00
Though my build can't be an insider build as it's the version that came with the Dell XPS when I purchased it?
Saltgrass
4 Operator
•
4.3K Posts
0
January 9th, 2017 07:00
One of the cumulative updates back in Oct or Nov seems to have introduced networking problems and Wi-Fi was one. Microsoft even put up a sticky trying to help folks get their systems back to normal.
Normal users don't have enough information to make a determination if the problem is because of their specific wireless adapter. Using an external USB adapter may allow normal operations, which would indicate your internal device.
You might check to see if there is any additional software which could be loaded for that adapter to help it auto-connect. Router firmware updates could also make a difference if you use one.
Checking the Event Viewer and comparing connection specific information may help track down problems.
namnoops
15 Posts
0
January 9th, 2017 09:00
Well, I can say that my system has had this problem since day one - I received the laptop in the beginning of November and it has never connected to a network automatically. I believe if this was the case for all XPS 9360's I would have heard about it by now?
I did check for newer drivers for the Killer Wireless 1535 adapter, and factory reset my Windows to no avail.
Any more ideas?
Saltgrass
4 Operator
•
4.3K Posts
0
January 9th, 2017 12:00
If you left click your wireless icon on the taskbar. Then left click your network and select properties you should have a good idea of what is happening.
Which band are you one, 5 or 2.4 .. Does the IP Address look normal are you showing an IPv6 address. You can compare the driver version to what you see online to make sure and driver update succeeded.
You get some additional info if you right click the speaker icon and open the network and sharing center. Go to change adapter settings and check the status of your Wi-Fi adapter. Look for the Lease info, when was it obtained and how long is it good for.
I am not a networking person so all I can do is guess. I have replaced all the Dell supplied Wi-Fi adapters on my systems. Luckily they all work fine, so hopefully you can find a solution to your situation.
shoffmeister
1 Rookie
•
53 Posts
0
January 9th, 2017 12:00
To clarify even further:
My XPS 13 9360 (with Rivet / Atheros WiFi drivers) has performed exactly as desirable for release versions of Windows 10 (Home), across all aspects of the hardware environment. Only after the installation of the (at the time of this writing) current Windows 10 slow ring insider build did my trouble with WiFi auto-connect start.
At this time, I can only recommend to _not_ install the WiFi drivers provided by Dell for the Killer 1535 WiFi card (as these included the Killer network QoS / balancing / throttling manager driver). Do download from Rivet Networks the plain drivers, and just the plain drivers.
Apart from that, I have only minimal amounts of coil whine (on an i7/16 GB/QHD device), which drowns in the background noise of any office - this is very manageable. Reviews complain about the "quality of the sound" emitted by the built-in XPS13 speakers. To be frank, any _laptop_ will have these issues with such small speaker drivers.
At this time, my most serious complaint is about the Windows 10 operating system (Microsoft software!) having challenges with mixed DPI multi-monitor configurations - and even here, I seem to be making progress by making the lowest DPI screen the primary screen upon "docking".
FWIW; I have not yet tried to reassign the IPv4 network interface priorities (netsh interface ipv4 show config). I have two virtualizers (VMware Workstation, Oracle Virtualbox) installed. This may, or may not, improve matters.
At this time, I'd rate my experience at 8.5/10, the Dell hardware environment at 9.25/10, but only because I do not yet know how to squeeze the remaining 0.75 out of the system.
I am coming from a Haswell-generation, matte display, Full HD Toshiba Satellite Z30-A, which I'd rate 9.5/10 for weight, size, connectivity, 16 GB of memory. And that for the cheap bastardized consumer version of the grossly overpriced Portege business version. Truth to be told - if a Kaby Lake version of that laptop had been available to me, the Toshiba it would have been, again. Matters being as they are, the XPS 13 9360 was the device of choice. I seriously hope that over the course of the next 12 months, all parties involved (Dell, Microsoft, Intel, Qualcomm / Rivet Networks) will work on making the XPS 13 9360 as lovable as the Toshiba Z30-A.
shoffmeister
1 Rookie
•
53 Posts
0
January 9th, 2017 14:00
FWIW, I currently suspect that network interface metrics play a role, combined with changes in the Windows 10 insider build, combined with my sufficiently extensive use of virtual network adapters.
At this time, I have no reason to blame Dell hardware, only the slightly of all chances for the problems originating from Rivet Networks drivers, with the likely culprit being the insider build of Windows 10 home.
Jamwagon
1 Message
0
January 9th, 2017 16:00
I am having this same issue on my xps 13 9360 with killer 1535 adapter. It is not related specifically to just insider builds. I am running the latest version of windows 10 and the latest killer driver
namnoops
15 Posts
0
January 9th, 2017 23:00
Well I'm on the stock build that came with the XPS, with no virtual network adapters and I can't get the thing to work. I downloaded the drivers from Rivet networks (www.killernetworking.com/.../other-downloads - on the right). My network card is now showing v. 12.0.0.285 from 20-Oct-2016. Is this what you mean @shoffmeister?
I'm pretty sure this is the same version I had before...
shoffmeister
1 Rookie
•
53 Posts
0
January 10th, 2017 04:00
Networking problems were isolated to DHCP, which again was a side-effect of some other component failing.
The items under discussion here is automatic association of the WiFi card with an access point in range.
shoffmeister
1 Rookie
•
53 Posts
0
January 10th, 2017 04:00
I was using these very drivers successfully, indeed, to auto-connect - before my upgrade to the insider build. The benefit of these drivers is that they do not contain the Killer bandwidth management code, which for my scenarios would not add any value.
The only thing that changed matters for me (into the wrong direction = no auto-connect any more) was the Windows insider build.
shoffmeister
1 Rookie
•
53 Posts
0
January 10th, 2017 05:00
FWIW, in order to simplify my little universe, I removed the following two pieces of software from the system:
- Oracle Virtualbox
- vagrant
I also disabled "Connected Standby" mode for Windows 10 via a registry setting - search Google in case you are inclined to do this for your self.
At this time, it seems as if the ability to automatically connect to WiFi networks has returned. Knock on wood.
namnoops
15 Posts
0
January 10th, 2017 05:00
So the problem is not these drivers but the Windows build I am on, which is not an insider version. It's build 14393.
I'm stuck.
shoffmeister
1 Rookie
•
53 Posts
0
January 12th, 2017 13:00
FInal update from my side:
Over the past couple of days I have been running with the changes applied as above. WiFi auto-connect works (again) flawlessly, survives access point switches, survives reboots, cold starts, sleeps, hibernates, ...
For now I blame vagrant / Oracle Virtualbox, or Microsoft Connected Standby.
I am still running VMware Workstation 12.5.2 on the aforementioned Windows 10 insider built, with bare KIller network drivers (and without the Killer funky traffic shaper)