Cannot turn off 'automatically connect' option on WIFI connections

Anonymous
2013-06-19T04:07:13+00:00

This I think is either really strange or normal.

I have windows 8 on my notebook and an Inter Centrino N-2230 wireless adapter.

Recently, all WIFI connections that appear as available have the 'connect automatically' option checked. I uncheck the box, but they automatically get checked again.  I am sure that previously, all wifi connections had the box unchecked by default.

However this is NOT the case with the one wifi connection I primarily use, ie my home cable connection. I can uncheck the option for this one and it stays unchecked. Bizarre.

I am a bit concerned that if I use my notebook near an unsecured connection, it will automatically connect to this without my knowing resulting in security concerns.

Any idea if this is an issue, and how to resolve it?

Thanks

Windows for home | Previous Windows versions | Internet and connectivity

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.

0 comments No comments
Answer accepted by question author
Anonymous
2014-03-08T01:36:03+00:00

I assume that all of the trouble machines that are automatically connecting are using Intel PROSet Wireless Tools.  Simple fix.

Goto the Control Panel.  

Type Wireless in the search panel.

If Intel PROSet Wireless Tools is an option click it (if not then you may have another issue)

Under the option Intel Wifi HotSpot Assistant click Settings

Uncheck Automatically Connect to free WiFi Hotspots.  

Click Close 

Your DONE!

Problem Solved Unless you are not using Intel PROSet Wireless Tools.

Was this answer helpful?

90+ people found this answer helpful.
0 comments No comments

90 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-03-20T00:15:55+00:00

    ;)

     ...and ditto will apply for any other 'unsecured' (whether you have used them or not) networks, ONCE you have initially removed the ticks.

    *don't worry about the 'ticked' "secured" networks (that is only done for convenience), you CANNOT be connected to ANY network unless you have entered its code at least once.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-03-20T00:08:02+00:00

    I can confirm that the box is unticked for a non secure nearby connection that I've never connected to.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-19T23:59:16+00:00

    ..."the customer is always right" is so seventies. :)! Welcome to 2016...and Microsoft. I believe you have mistaken me for someone who works for, or represents, Microsoft. Nope.

    *It is not a bug. That tick next to 'unsecured' connections can be removed and will remain removed. ANY other ticked 'secured' connections are possible connections and as one is not available attempt WILL be made at the following 'ticked' connection in the list. In any case, automatic connection to ANY ticked 'secured' connection will not happen without an access code.

    *Interesting (subjective) point of view. Run that by Microsoft and see how much they 'value' you as a customer.

    Hold it....."...which I'm not sure there is or should be ", "problem" solved then? :)

    *...doesn't work like that, for users who prefer ALL available 'secured' connections be 'ready' for attempt at connection, they are ticked in advance in anticipation of need. It will however remember those unticked 'unsecured' connections.

    *"Another option is to get rid of the checkbox altogether until the first time a connection to the network is made.", see second and third points.

    "NOTE: First time includes first time after forgetting about a network."....in which case the NEXT time you see that 'forgotten' network in your list you will no longer have ANY option to connect to it 'automatically (with access code') in future. :(

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-19T22:56:04+00:00

    I did not think this would be necessary....simply substitute "Windows 8/8.1", in lieu of my "Windows 10", the same 'functioning' applies. If you do as I have explained, in Windows 8/8.1/10, and it does not work AS IT IS INTENDED to then get back to me. ;)

    Was this answer helpful?

    0 comments No comments