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.

    Intel 7620AC Dual Band Wireless---BLUETOOTH NOT WORKING

    Discussion in 'Hardware Components and Aftermarket Upgrades' started by inperfectdarkness, Apr 11, 2014.

  1. inperfectdarkness

    inperfectdarkness Notebook Evangelist

    Reputations:
    100
    Messages:
    387
    Likes Received:
    102
    Trophy Points:
    56
    I'm at my wits end here. I replaced the stock Killer Wireless 1202 card with an Intel 7620AC card. My wifi is ROCK stable now, but I have ZERO bluetooth functionality.

    PC is an MSI GT60 2OD-261US, and I'm running driver 16.5.3.6.

    Can anyone help?
     
    inperfectdarkness, Apr 11, 2014
    #1
  2. inperfectdarkness

    inperfectdarkness Notebook Evangelist

    Reputations:
    100
    Messages:
    387
    Likes Received:
    102
    Trophy Points:
    56
    Fixed.

    Long story short, NEVER use MSI's System Control Manager to disable Bluetooth. It will permanently disable your Bluetooth if you do, and you end up having to do a complete driver wipe and re-install.
     
    inperfectdarkness, Apr 11, 2014
    #2
  3. deadsmiley

    deadsmiley Notebook Deity

    Reputations:
    1,147
    Messages:
    1,626
    Likes Received:
    702
    Trophy Points:
    131
    I had to update my BT drivers from the Intel site to get my LG HBS730 headset to pair. Works really well now!

    Glad you got yours figured out.
     
    deadsmiley, Apr 11, 2014
    #3
  4. inperfectdarkness

    inperfectdarkness Notebook Evangelist

    Reputations:
    100
    Messages:
    387
    Likes Received:
    102
    Trophy Points:
    56
    I might be mistaken, but I don't think my original drivers were the issue. I think it was the SCM all along, but I never realized it after I'd disabled it via SCM the first time.
     
    inperfectdarkness, Apr 11, 2014
    #4