Extremely unstable and stuttery bluetooth connection with win 11 and Momentum 4

Question

Extremely unstable and stuttery bluetooth connection with win 11 and Momentum 4

Elijah Derwahl 0

I've recently dual booted with arch and since then my momentum 4s have not been able to properly connect to win 11, they may show up as "connected" in the bluetooth menu however no audio will come through nor will it be recognised as a speaker by win 11, nor when it says "connected audio and mic" will only occasionally come through stutters of volume with quite a delay, this will also cause my source to buffer. I have tried reinstalling bluetooth drivers, updating bluetooth drivers, updating windows, checking all early fail points such as selected wrong output and so forth yet it prevails.

I can confirm it being a windows issue as my phone functions perfectly as prior. I can only assume win 11 is having difficulties with arch on its drive though I was careful in my installations and made no error that should lead to this.

I am on a hp victus 15 btw

0 comments

1 answer

Your answer

Answer 1

Hi Elijah Derwahl,

I understand how frustrating this must be, especially since the headset works correctly on your phone and the issue started after setting up a dual-boot environment.

To narrow this down further, could you confirm:

Which Bluetooth adapter is installed in the HP Victus 15 (Intel, Realtek, MediaTek, etc.)?
Does the Momentum 4 appear under "Sound, video and game controllers" in Device Manager when connected?
Approximately when did the problem start, immediately after installing Arch Linux, or only after booting back into Windows later?

In the meantime, please try the following:

1, Remove all existing Momentum 4 Bluetooth profiles and pair again

Sometimes multiple stored Bluetooth profiles can cause Windows to connect incorrectly.

Open "Settings" > "Bluetooth & devices" > "Devices".
Remove every entry related to Momentum 4 or Sennheiser.
Put the headset into pairing mode.
Restart the PC.
Pair the headset again and check whether Windows creates both the audio output and microphone devices.

2, Check whether the audio endpoint is being created

When the headset shows as connected, press Win + R, type: mmsys.cpl and press Enter.
Under "Playback", verify whether the Momentum 4 appears as an audio output device.

If it does not appear at all, that would indicate Windows is establishing a Bluetooth connection but failing to register the audio service.

3, Disable and re-enable the Bluetooth audio services

Press Win + R, type: services.msc
Locate "Bluetooth Audio Gateway Service".
Right-click it and select "Restart".
Also verify that its Startup type is set to "Automatic".

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Elijah Derwahl 0 Reputation points

2026-06-28T01:03:36.05+00:00

after leaving the laptop shut down for a day it seems to have resolved itself however in case of its return i will answer questions.

Mediatek bluetooth adapter is installed, It has shown up in sounds, video and game controllers, the issue began as soon as I booted into windows after the dual boot installation.

I have tried the first fix to no avail many times, the headset would momentarily connect and create endpoint however it never held longer than a minute where then the endpoint would disappear too and restarting the bluetooth service also had no effect.
Sin-D 10,745 Reputation points Microsoft External Staff Moderator

2026-06-28T06:40:01.1066667+00:00

Hi Elijah Derwahl,

Thank you for the update. I'm glad to hear the issue appears to have resolved itself after the laptop was left powered off for a day.

The additional details are helpful. Since the MediaTek Bluetooth adapter is installed and the headset briefly connects and creates an audio endpoint before disconnecting, and since restarting the Bluetooth service did not help, this may point to a driver or device interaction issue rather than a Bluetooth service problem alone.

I look forward to your update if the problem reappears.