W8.1 Does not connect to network automatically

Notacord

Honorable
Sep 23, 2013
15
0
10,520
I have the "automatically connect" option checked and all other network profiles have been deleted. I have to manually connect EVERY time. I havent found a solution except for the typical "go to Manage Networks in Control Panel", except it doesnt bloody exist, either that or I have boiled eggs instead of eyes. :na:

Is there a way to use "Schedule Tasks" to automatically connect upon startup?
 

WinOutreach6

Honorable
Apr 10, 2013
72
0
10,710
Notacord,

If you haven’t already, check and make sure you have the latest driver for Windows 8.1 installed for your Wi-Fi adapter. Sometimes outdated or corrupt drivers can cause issues during startup which cause other processes to not work correctly.

Another option is to perform a clean boot on your computer. Performing a clean boot will allow you to start Windows using a minimal set of drivers and startup programs to help eliminate software conflicts. For example, there are cases where things like antivirus and other security related software can prevent processes or services from working properly.

The Manage wireless network profiles page may also have information that could be relevant to your issue, such as how Windows determines connection priority.

Hopefully this helps!

Mike
Windows Outreach Team – IT Pro
The Springboard Series on TechNet
 

Notacord

Honorable
Sep 23, 2013
15
0
10,520

I updated my drivers but it hasnt solved the problem.


Can you elaborate? Do I need to boot with programmes/drivers disabled, and then by process of elimination figure out what is conflicting? How do I disable certain drivers etc..?

Also, surely theres a way to schedule connecting to a specific network on startup as a task :??:
 

WinOutreach6

Honorable
Apr 10, 2013
72
0
10,710
Notacord,

You are correct that through process of elimination, you’ll be able to tell which programs and/or drivers might be causing your issue.

As far as disabling anything, you’ll be doing that in the Services tab of System Configuration and then in the Startup tab of Task Manager. Take a look at the How to perform a clean boot in Windows page for more details and step by step instructions.

If you’re determined to create a task to connect to your network, you can do that but keep in mind that it’ll only be a band aid on the underlying issue. The correct way to deal with this is to find the cause of the issue and fix that. With that said, here’s how you’d accomplish creating a task to connect:

1. Go into Task Scheduler.
2. Select Create Basic Task.
3. Give your task a name.
4. Set the task to start when the computer starts.
5. Set the task to start a program.
6. In the Program/script field, type in netsh.exe
7. In the Add arguments field, type in wlan connect name=yournetworkname

Depending on what your underlying issue is, you may need to set a delay. If you find that the connection is failing, try giving the task a delay of 1 minute to give enough time for drivers to load. You can do this by going back into the created task and editing it. The option for the delay is under the Triggers tab.

Mike
Windows Outreach Team – IT Pro
The Springboard Series on TechNet
 

Notacord

Honorable
Sep 23, 2013
15
0
10,520
A quick update:
I created a shortcut that executes the network join command and placed it in the start-up folder. It will not join the network unless I have joined it during the current session. So after the session ends, I still have to join manually upon start-up.

Something odd Ive noticed is that all networks (except unsecure ones) in the side bar have "Connect automatically" checked and if I uncheck it, it will default back to checked when I open the side bar again.

I will attempt scheduling (with delays etc) but doubt it will work since the start-up shortcut hasn't.
 

Notacord

Honorable
Sep 23, 2013
15
0
10,520
Sorry for the delay,
Task scheduling didnt work, and it's not worth going through the hassle of finding the driver conflicts. How have Microsoft not fixed this? I've had this problem since day one (been 18 months since) and I really doubt its the network card's fault.
 

TRENDING THREADS