My patience is gone, please help.

Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation.

I sounds like the drivers you have for your Headphones may not be compatible with Windows 10, first place to check is with Skull Candy as they are responsible for supplying Drivers for their hardware, (although some manufacturers do not issue drivers for older hardware but expect the user to buy new hardware when they update their PC - hopefully Skull Candy are not one of these manufacturers )

Every single time I boot my pc and try and connect my headset windows reverts all of my settings

Hi, forgetting the headphones for a moment - when you say

all of my settings

- what exactly do you mean?

Do you mean other configuration settings? Such as?

Or are you only and exclusively referring to your paired headphones?

Turning to Bluetooth- do you have any other devices that pair successfully?

You might try turning Fast Startup off just in case that makes a difference.

What is your Windows build number?


Thanks.

According to this I have version 21H1 OS build 19043.2006

When I say it reverts everything I mean it reverts everything back to a device called 24MP55 with a monitor symbol next to it. Everything else is gone, it's as if it never happened. Also on this system I have only ever ran the skullcandy headphones for sound and my monitor does not have speakers so I cannot run sound through there. After I reinstall the ASUS dongle driver and connect the skullcandy headset to said dongle I then have to go into settings and disconnect then reconnect three separate times to get sound. The first time it only says 'connected' but no sound can be heard. The second time it will say 'connected, voice' and still no sound, then on the third time it will say 'connected, music' and I get sound.
Now the infuriating part: when I am done my session and I power down the pc or even put it to sleep Windows clears everything I have done and I get to do it all over again. This has been happening since a windows update in either March or April (I apologize I cannot remember exactly when) and I simply don't understand what's going on or what changed to make this happen. I have ran this set up for a few months before this issue popped up and never had a problem until that.

Edit: To answer your other questions I can successfully and reliably able to connect to my Samsung phone with no issues. All I need to do is power down my pc, tap the round button on the headphones to get it to go into pairing mode (or wait a few seconds without the headset being able to connect to anything) and then connect via my phone. No issues ever on that end.

As to fiddling with any settings I generally won't because lets face it, I am out of my wheelhouse when it comes to matters like this. If you ask me to fix your tractor or grow food in a field I can do that with confidence, but if you ask me to do anything computer related beyond where files are actually located or how to recover my email password for the thousandth time this week I'm probably not going to understand it. I'm so paranoid about changing things in my system by myself that I get anxious just thinking about it because I have almost zero understanding of things beyond the physical steps I take on a regular basis.

I know that is not the answer you were wanting to hear on that end, and I am also aware that my lack of knowledge to this end makes me a target to online scammers and hackers so if any system settings are to be changed I will be passing along it to my tech friend first.

By way of an example of an update that refers to Bluetooth issues see:
https://support.microsoft.com/en-gb/...3-ca41a91c1c56

I am not suggesting this is necessarily what you're experiencing- only indicating that there has been reference to Bluetooth in at least one update around the time you mention.

- you need to expand the relevant sections to see e,g,

Some organizations that have Windows devices paired to Bluetooth devices might receive the error message, "Your device ran into a problem and needs to restart.” and the stop code, ”IRQ NOT LESS OR EQUAL." This issue occurs after installing KB5009596 or later updates, and the messages appear on a blue screen. The errors are in the System log in Event Viewer as, "Microsoft-Windows-WER-SystemErrorRe event 1001" and the text, "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a" appears.

This issue occurs in one of the following scenarios when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile:

The issue occurs during restart at the end of the update installation process if the Windows client device was previously paired with a mobile phone or other audio devices using Bluetooth.

Now there I used the list of applied updates from my Update History and clicked on that one.
You may be able to do the same to read this text and for other updates around this time.

Here are the updates:



Unfortunately the News section here only runs from about July currently so the articles for these have been deleted.

I've not heard of an issue such as yours, nor seen an issue related to an update reported myself- but I don't read all threads of course.

Noting you're on 19043, you could try updating to the current build. (19044.2006 not including preview updates).

And regarding restart etc.. remember I suggesting trying disabling Fast Startup if enabled.

I think the first thing I'd look for is simply the stability of the dongle driver. Irrespective of pairing- leave that aside- does the dongle driver remain installed and survive a restart?

My limited experience of those is that no special driver is needed- I simply plugged mine in.
Your experience may differ of course. (See Rick C's post above with link to the driver).