Join now - be part of our community!

WH-1000XM3 can't connect with Windows 10?

profile.country.SE.title
man0negro0
Member

WH-1000XM3 can't connect with Windows 10?

Hi,

So I'm sure this question has been asked by more than me here but i was unable to find any solution. I have two pcs one new lap top  where they connected fine. But my media pc in my living room which is older refuses to connect, it has paired but not connected. The computer is using the ASUS USB BT 400 usb dongle. 

 

Don't know what to do and SONY does not seem to want to adress the issue, at least not with a solution. Thats bad considering How Maaaany are experiencing this joke of an issue 2021 for so expensive headphones.

 

I read that you mus have the A2DP codec, is that something you can download?

 

Ill be super grateful for ANY pointers in this matter. I have so many new movies to watch and cant watch them as i want to try with these ones 

 

 

Thanks!!!!

13 REPLIES 13
profile.country.NL.title
Strampke
Expert

I had the same problem the other day.

It's not the headphones.

 

Using an app (in my case Microsoft Teams) did it.

I expect that installing Zoom is easier.

These apps are good in searching for connected devices and setting the necessary settings.

 

One other thing to take a look at is your Antivirus software. That software is good in blocking connections.

 

profile.country.GB.title
Win_88
Specialist

I'd make sure the headphones are up to date by connecting them to a smartphone withe the Sony Headphones Connect app installed.

 

A2DP is a Bluetooth profile. It's basically a part of the Bluetooth receiver's specifications and isn't something that can be downloaded. So if you don't have it, your PC wouldn't be compatible with the headphones.

 

 

profile.country.SE.title
man0negro0
Member

Hi,

Thanks! The headphones are connected to the app daily and im 100% ive got the latest update.

Its wierd because they do have semi paired. In the printers and bluetooth section you can see two diffrent devices.

One LE_WH-1000XM3            and another just WH-1000XM3. When i right click on them and choose the Services tab i get the traditional tick boxes of the diffrent drivers/funtions, so i click them all in on both of the deices and then go to the bluetooth devices saction, where you add and, pair, and connect. They are both there the LE_1000XM3 is at the bottom and it just says i guess what in English would be Paired (direct translation from Swedish: Engaged /Coupled) the other one is at the top almost and says the came thing, but when you right click it you get the "Connect" and "Remove" buttons. Klicking the Connect button you Instantly with out even a split second passing the error message saying that it was not possible to connect, please check if the headphones are still recieveing (which they of course are, ive tried the regular alrady paired way and the lets pair way, neither works) But im like Hey, you didnt even TRY no way you could have even almost begun to connect, you threw in the towel on the Go and try to blame it on the headphones, your Fast but not That fast..."  That actually a transcript of how i think in frustration when it happens 🐵

 

Ive got a new laptop and there all is paired, connecting and transmiting. I noticed that one has a driver called A2dp Source, which the other one does not, also on the laptop Both of the WH devices has an LE_ in front of them.both the handsfree and stereo devices of the headphones...

 

So there you have a bit more info....

profile.country.GB.title
konorok
Explorer

I have the same issue now. Paired but not connecting. Easily connecting on Linux Ubuntu on the same PC and to the smartphone. But on Windows getting this message: "That didn't work. Make sure your bluetooth device is still discoverable, then try again." The drivers are all updated. Anyone found a solution yet?

P.S. This is weird, because I also have WF1000-XM3 and they connecting without a problem.

profile.country.GB.title
konorok
Explorer

Update: I fixed this eventually by playing around with Bluetooth drivers, installed, uninstalled, installed, used different Driver updaters and somehow made it to connect to the headphones again.

profile.country.SE.title
man0negro0
Member

Hi,

Sorry for not responding earlier. Im glad to hear you got it resolved as i know what bloody headache i went through myself. Its under All critizism that Sony has not gotten off their fat asses and resolved this with either a fix or pointers, im still super ***** about it. As if its some pair of junk headphones i got free on a bloody airplane...

Anyway F* 'em!

 

So i might be able to compensate you for letting you down on the late response....You know the headphones supports an audio codec called aptX HD? If not here is a link about the codec: https://www.aptx.com/aptx-hd

As much as the headphones may support it its not for granted that your pc is or if it has it installed, so here is a link with instructions: https://www.youtube.com/watch?v=3qr5o8x4LDQ

...and finally here is a download link to the install file: https://www.dell.com/support/home/sv-se/drivers/DriversDetails?driverId=100J9&fileId=3546946146&lwp=...

It says Dell but its an Intel software so never mind the dell name, once yo install it youll see only Intel. My only reservation is that its a 32bit version, could not find a 64bit. Once its installed and the headphones are connected and starts playing youll see a new popup notice down in the right corner by the taskbar. Ive attached a picture of it, its in Swedish but its basically saying that "You are now using aptX with technology from Intel". Lastly youll see whats shown in the second picture from the Sound settings tab saying " aptX Support is now activated." with a ticked in tick box.

 

Now youll have aptX HD playing from your PC... How fantastic it would had been if Sony Cared to share this info, fi they even know about that it Might be neded, well lets not hold our breaths and just solve it ourselves. Just takes so much time totally unneccearily but there you go. They have make some pretty damn good headphones thats not even argueble but the quality of thier information on things like this is sub par. My dog is better at letting me know when he needs to take a *****.... Imagine all the people who have zero tech savvyness, i feel for them.

 

Once again... Anyways... Hope it runs smooth for you know.

 

Best Regards!

Ansu

 

This one pops up for me each time i connect the headphones to the laptop. Youll probably also see a new addition oa a background software named "iBT  Audio monitor" thats the kicker thats making it happen.This one pops up for me each time i connect the headphones to the laptop. Youll probably also see a new addition oa a background software named "iBT Audio monitor" thats the kicker thats making it happen.This mark would also be visible each time, but you must obviously open the Sound settings by right clicking the sound icon in the taskbar.This mark would also be visible each time, but you must obviously open the Sound settings by right clicking the sound icon in the taskbar.

 

 

 

profile.country.GB.title
HannahEd01
Community Team

Hey there konorok , I'm glad that it worked finally. *_* could you share what are the steps that you tried so that may benefit others?

profile.country.GB.title
konorok
Explorer

I don't know to be honest, it was working fine since then but now I'm stuck with this issue again after about a month. The culprit is most likely bad drivers, so I'm trying to sort it out and if lucky will try to figure out which exact driver causing this.

profile.country.GB.title
konorok
Explorer

So did anyone find out what's really causing this issue?


Cause I'm stuck with this issue again, tried all sorts of drivers but nothing works, even did windows repair update install.

Getting these errors:
"Couldn't connect" - via 'Connect' function on the right pane.
"That didn't work. Make sure your Bluetooth device is still discoverable, then try again." - via Bluetooth settings.


It shows this on all Bluetooth devices but it's not even actually trying to connect, instead instantly shows "Couldn't connect" error.