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.

    GT60 0NE-249US Bluetooth Won't Turn On

    Discussion in 'MSI' started by quietas, Dec 23, 2012.

  1. quietas

    quietas Notebook Consultant

    Reputations:
    2
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    It's a weird thing, I've been using my Bluetooth with my mouse and it just stopped working. I press the Fn+F9 combo to turn it on and I get the Bluetooth symbol with a slash through it. If I check the icon in the system tray it is grey and says Turn Adapter On when I right click. I choose to turn it on and nothing happens at all. Device manager shows it is disabled, but Windows can't enable it.

    I'm running Windows 8 and it's a stock machine with current drivers from MSI plus beta nVidia drivers.
     
  2. quietas

    quietas Notebook Consultant

    Reputations:
    2
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    I managed to fix it. The solution was to download and install the Killer Bigfoot drivers again. I installed it and the Bluetooth started working, but wireless stopped. A second install and both seem to work now.
     
  3. areet

    areet Notebook Enthusiast

    Reputations:
    31
    Messages:
    49
    Likes Received:
    0
    Trophy Points:
    15
    I could have saved you a few reboots. I have the drivers for the wireless card posted online. If you do an MSI recovery on a new harddrive, the wifi doesn't work. Instead of uninstalling and reinstalling Bigfoot, you can just use the files I uploaded.
     
  4. quietas

    quietas Notebook Consultant

    Reputations:
    2
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    I could use those drivers. It has once again turned off and a reboot will not get bluetooth to turn on again.

    I'm open to suggestions if anyone has another method to keep bluetooth functioning.
     
  5. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    When/if you re install the drivers (whether they're the ones areet provides for you or not) try uninstalling the original with driver sweeper. You can even try to install the driver using the Add New Hardware wizard or through your Device Manager, and bypass the install utility - although I can't guarantee that will be a surefire fix.
     
  6. quietas

    quietas Notebook Consultant

    Reputations:
    2
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    So far no luck. It's done it to me several times and I've uninstalled with Revo Uninstaller to wipe out all files and registry entries.
     
  7. quietas

    quietas Notebook Consultant

    Reputations:
    2
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    30
    I managed to delete the device and drivers, then reinstall only the bluetooth adapter. I installed the current Killer Bigfoot Doubleshot driver package.

    The drivers are located at: C:\Program Files\Qualcomm Atheros\Killer Network Manager\bflwf

    Via Device Manager I was able to detect new hardware and point it at that location. So far all has been good for a couple days of gaming.

    On a sidenote, here is a good link if you power settings are killing your bluetooth connections. Bluetooth Mouse Losing Connection No More!
     
  8. Prostar Computer

    Prostar Computer Company Representative

    Reputations:
    1,257
    Messages:
    7,426
    Likes Received:
    1,016
    Trophy Points:
    331
    Good deal! So the manual install of the driver worked, eh? Sometimes those setup utilities are the problem, and not so much the driver itself.