Bluetooth adapter prevents the game from starting

[ElizTriad]

The game thinks my bluetooth adapter is a broken Gamepad. But I do not have a gamepad! bluetooth headphones only.

I use the official launcher, install Forge and get this error.
Neither mods nor resource packs, nothing is installed. Only vanilla minecraft and forge.
Without Forge, this error does not occur. If I disconnect the bluetooth adapter from the computer, the game starts without errors.
Other new versions of Forge cause a similar error, version 31.2.0 and 31.2.31 also does not work.
Completely uninstalling minecraft and reinstalling everything again does not give any result.

I use a Bluetooth adapter for headphones, so I can’t refuse it, because then I have to play without sound.
Perhaps there is a quick fix? Is it possible to force the game not to check for a gamepad at all?
 

The game crashed whilst initializing game Error: java.lang.IllegalStateException: GLFW error before init: [0x10004]Invalid button in gamepad mapping 03000000ffff00000000000000000000 (GameStop Gamepad)

Bug report

---- Minecraft Crash Report ----
// This is a token for 1 free hug. Redeem at your nearest Mojangsta: [~~HUG~~]

Time: 07.07.20 22:24
Description: Initializing game

java.lang.IllegalStateException: GLFW error before init: [0x10004]Invalid button in gamepad mapping 03000000ffff00000000000000000000 (GameStop Gamepad)
	at com.mojang.blaze3d.platform.GLX.func_229879_lam_(SourceFile:64) ~[?:?] {re:classloading}
	at com.mojang.blaze3d.platform.GLX$$Lambda$1988/280862192.accept(Unknown Source) ~[?:?] {}
	at net.minecraft.client.MainWindow.func_211162_a(MainWindow.java:130) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
	at com.mojang.blaze3d.platform.GLX._initGlfw(SourceFile:63) ~[?:?] {re:classloading}
	at com.mojang.blaze3d.systems.RenderSystem.initBackendSystem(SourceFile:996) ~[?:?] {re:classloading}
	at net.minecraft.client.Minecraft.<init>(Minecraft.java:371) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
	at net.minecraft.client.main.Main.main(SourceFile:166) [?:?] {re:classloading}
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51] {}
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51] {}
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51] {}
	at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51] {}
	at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) [forge-1.15.2-31.2.0.jar:31.2] {}
	at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$399/818093527.call(Unknown Source) [forge-1.15.2-31.2.0.jar:31.2] {}
	at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-5.1.0.jar:?] {}
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-5.1.0.jar:?] {}
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-5.1.0.jar:?] {}
	at cpw.mods.modlauncher.Launcher.run(Launcher.java:81) [modlauncher-5.1.0.jar:?] {}
	at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) [modlauncher-5.1.0.jar:?] {}


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Render thread
Stacktrace:
	at com.mojang.blaze3d.platform.GLX.func_229879_lam_(SourceFile:64)
	at com.mojang.blaze3d.platform.GLX$$Lambda$1988/280862192.accept(Unknown Source)
	at net.minecraft.client.MainWindow.func_211162_a(MainWindow.java:130)
	at com.mojang.blaze3d.platform.GLX._initGlfw(SourceFile:63)
	at com.mojang.blaze3d.systems.RenderSystem.initBackendSystem(SourceFile:996)
	at net.minecraft.client.Minecraft.<init>(Minecraft.java:371)

-- Initialization --
Details:
Stacktrace:
	at net.minecraft.client.main.Main.main(SourceFile:166)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56)
	at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$399/818093527.call(Unknown Source)
	at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37)
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54)
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72)
	at cpw.mods.modlauncher.Launcher.run(Launcher.java:81)
	at cpw.mods.modlauncher.Launcher.main(Launcher.java:65)

-- System Details --
Details:
	Minecraft Version: 1.15.2
	Minecraft Version ID: 1.15.2
	Operating System: Windows 10 (amd64) version 10.0
	Java Version: 1.8.0_51, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 1200346472 bytes (1144 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB)
	CPUs: 16
	JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
	Launched Version: 1.15.2-forge-31.2.0
	Backend library: LWJGL version 3.2.2 build 10
	Backend API: NO CONTEXT
	GL Caps: 
	Using VBOs: Yes
	Is Modded: Definitely; Client brand changed to 'forge'
	Type: Client (map_client.txt)
	CPU: <unknown>

I recorded a small clip for clarity

Sorry if something is not clear, I use google translate

Edited July 7, 2020 by ElizTriad

[sciwhiz12]

This issue looks similar to MC-132113, where the player found that his bluetooth device's drivers caused a crash similar to yours.

Unfortunately, we cannot reproduce this issue without the exact device that is causing the crash.

If you are able, please describe the bluetooth device in detail: the brand name, if you bought it from official brand stores, the model number and type of device. This way, if someone does have a similar or exact device, we may be able to get more information.

[ElizTriad]

I don’t remember exactly which adapter I have.
Most likely "Adapter USB Buro BU-BT40A Bluetooth 4.0"
This is a niche product.

On the device itself, there is only the inscription "Buro"

As soon as I connect the adapter, the "CSR8510 A10" device appears. After the system determines the device and installs the driver, the adapter is defined as a "dongle", manufacturer: "KOGA", model number "0001".

I also came across this topic, I also noticed that the device mentioned there is the same as mine. But there is no solution, the author simply deleted the device that prevented the launch. It will probably work in my case as well, but I just can't remove it. As I mentioned - I use headphones through this adapter.

Edited July 8, 2020 by ElizTriad

[ElizTriad]

9 minutes ago, diesieben07 said:

Check the bluetooth devices that are paired to your computer and remove any that you don't need, especially game controllers.

I do not have unnecessary or unused bluetooth and other devices, and as I mentioned, I don’t have any game controllers
I have only one bluetooth device - headphones.

[sciwhiz12]

Then the issue lies at the developer of the device which is causing issues with GLFW's input detection mechanisms.

Again, we cannot diagnose the issue properly since we have no access to the device causing these issues.