The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Access Connections Issue - After April MS Updates - No Auto Location Switching

    Discussion in 'Lenovo' started by JosephB, May 6, 2013.

  1. JosephB

    JosephB Notebook Guru

    Reputations:
    1
    Messages:
    69
    Likes Received:
    1
    Trophy Points:
    16
    Anybody else, have the *Issue* - Where "Access Connections" stopped performing Automatic Location Switching, following applying - the "April": MS Security Updates on a - Win XP, T61 PC ???

    After applying the April - MS Security Updates, upon Booting up my T61, it no longer performs - Automatic connecting to my Wireless - Location Profile. Now, I have to go to System Tray Access Connection Icon, choose my wireless location profile and click connect.

    Does Automatic Location Switching still work for anyone on Win XP Thinkpad T61, after applying the April MS Updates ??? ... If it still works for you, what Version of Access Connections are you using on Win XP, after applying the "April - MS Updates" ??? (I am running an older version than the current version, as I have not upgraded it for a while)
     
  2. JosephB

    JosephB Notebook Guru

    Reputations:
    1
    Messages:
    69
    Likes Received:
    1
    Trophy Points:
    16
    Problem Solved -- The 3rd Re-Boot, after applying the April MS Updates, "some how" automatically "fixed" it and now Access Connections, once again, performs Automatic Location Switching, upon Boot-Up of the pc.
    ... Nothing else was done. Just 3 Re-Boots and working fine once again, on every boot-up going forth, so far.
    ... Its a mystery alright. If anyone has an explanation of why it took 3 reboots to fix itself, I would be interested in hearing it.
    ... Anyway, I am glad its working again.