Windows 10: Problem with Sony WF 1000XM3 Connectivity and sound

So recently i just installed and upgrade my laptop from harddisk to ssd and windows 8.1 to windows 10. Then i installed the bluetooth Qualcomm Atheros then connect my headset Sony WF 1000XM3. At first it connected fine and i can hear the sound clearly. But after some time and some update, i disconnected my headset and try to pair it up new. Now i managed to connected my headset to laptop but somehow i can't hear the sound from this headset even after i set my bluetooth headset default. I have run troubleshooting multiple times, not solved at all. I opened the sound setting and if i play musi

:)

 

Sony WH-1000XM3: driver problem after Windows Update (no stereo driver)

I recently ran a Windows 10 Pro update on my laptop. Since then my Sony WH-1000XM3 headphones don't seem to work correctly.

It seems that before the update I used to have at least 2 audio-devices for the headphones: a stereo device for high quality audio and a "handsfree headset device". After the update they were replaced with the "WH-1000XM3 Hands-Free AG Audio" device:





This device acts as a headset not as a stereo-heaphone set: it only gives mono and low definition sound. So it makes my headphones completely unusable for listening to music.

What I already did:

- removing and reconnecting the device.

- looking for Sony Driver on the web: nothing is to be found.

Can anybody give advice on how to fix this problem?

 

No voice output through sony earbuds while connected to pc (windows 10)

Hi Vijay,

thanks for your quick respond.

as i said when running the trouble shooting on the wf-1000xm3 (stereo) it says that the device is not connected, and when i run it on the wf-1000xm3 (headset) it is all good and the trouble shoot doesn't find any problem.

i tried all the changes with the drivers and it didnt changed a thing and i also done the Audio service part which also didn't work.

any other solutions?

Regards,

Dor

 

Unable to connect WH-1000XM3 headset to Windows 10 PC.

I have spent way too many hours now trying to reconnect my bluetooth headset to my stationary PC. I need help.

I've reached the conclusion so far, that the issue might be with the microsoft bluetooth drivers.

The issue:

After recently disconnecting my bluetooth headset from my PC, I was unable to reconnect. When I put the headset in pairing-mode, and search for available bluetooth devices, the avaiable bluetooth device I see is "LE_WH-1000XM3". This device is not recognized as a headset, and adding it brings me no closer to connecting. It adds the device as "Unrecognized", Shows: "Connected", and shortly after "Paired".

I've tried most tricks in the book. From SFC scans, updating windows, installing the most recent drivers (see below), removing and reconnecting the devices, removing and reinstalling all bluetooth-dongle related drivers, removing and reinstalling realtek audio drivers. I've unsuccessfully tried to manually delete the driver files.

The odd things I've noticed:

ODDITY 1: I cannot completely remove the drivers identified as relating to WH-1000XM3. They show up in devices and drivers every time new hardware changes are identified (even though headset is turned off):

--- Other devices > AudioWear

--- Other devices > AudioWear Voice

--- Other devices > CSR GAIA(TM)

--- Bluetooth > LE_WH-1000XM3

--- Bluetooth > WH-1000XM3

--- Bluetooth > WH-1000XM3 Avrcp Transport

--- Sound - Video and game controllers > WH-1000XM3 Stereo

If I go through the process of deleting the devices (headset is turned off):

1. Settings > Bluetooth and other devices

2. Select WH-1000XM3 and/or LE_WH-1000XM3 and choose remove.

3. Go to Device Manager, and see that all the driver entries above are gone.

4. Search for hardware changes

5. The device drivers mentioned above appear again. I do not know how or why or from where they are recovered, because the PC should not still store data on that headset. And it's turned off, so not discoverable via bluetooth.

ODDITY 2:

This goes for most of the bluetooth devices. If I go to Device manager > Events, I see every time I reconnect a device, I receive the following error or similar:

Device BTHENUM\Dev_94DB5618E6D6\8&1f614739&0&BluetoothDevice_94DB5618E6D6 was not migrated due to partial or ambiguous match.



Last Device Instance Id: BTHENUM\Dev_000C8A98862B\8&2c67b990&0&BluetoothDevice_000C8A98862B

Class Guid: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}

Location Path:

Migration Rank: 0xF000FFFF0000F120

Present: false

Status: 0xC0000719

ODDITY 3:

1. When I go through the steps described in "The issue", I can add the LE_WH1000XM3 device. If I do so, it shows up under "Other devices".
   
2. I then go into device manager, update the driver of "Bluetooth > WH-1000XM3" using the steps "Select driver on this computer" and "Select from a list of drivers" -> Only one driver displays: "Bluetooth-device"
   
3. I can now go back to settings > Bluetooth and other devices, and the headset shows up as WH-1000XM3. It is now recognized as a headset. But if I turn on my headset and try to connect, it skips briefly to "Connected" and then returns to "Paired". I can still not connect to the headset.
   

Systems and drivers involved (17-11-2021):

* gigabyte b450m ds3h - (BIOS v. F62d [most recent as per gigabyte])

* ASUS BT-400 Bluetooth dongle (Driver version Broadcom 12.0.1.658 [most recent per manufacturer])

* Sony WH-1000XM3 headset (Drivers seem to be Microsoft standard bluetooth drivers. No drivers from supplier)

* Windows 10 build 19044 [all recommended updates installed]

* (Realtek Audio driver: 6.0.9225.1 [most recent as per gigabyte])

The background info:

I have for some time struggled with the fact that I had to enter pairing mode every time I started the headset to connect to my PC. I decided to remove and re-add the device. I was unable to re-add the device.

The headset works flawlessly with my laptop (also Win10 19043) and my mobile phone (android).

The bluetooth dongle works flawlessly with other bluetooth headsets and devices.

This leads me to think that there is an issue with the microsoft driver.

Ps. If your name is Greg, and you want me to step through a 500-line list of standard mitigating steps, save yourself the hazzle and don't respond. Your response is the equivalent of going to the doctor and having a medical textbook shoved in your face with a message of "follow this guide and you will be cured". It might be well wished, but it's of no help.