[SOLVED] Windows has stopped bluetooth device (after bthps3 installation)


  • Hi, after many years of thankful use of your SCPtoolkit, I've come across this forum when trying to give Bluetooth connection a go again. It has worked partially through Zadig before but somehow I never managed to keep it that way, and ended up giving up. Now that I've found this goldmine of new tasty software to try I got super excited. The bthps3 package all works splendid, but I can't seem to get my Bluetooth to actually work. According to Shibari, my devices are paired. But upon disconnecting the USB cable it won't actually connect. I started looking into my device manager and found this:
    1774b6bb-9a88-4f61-8ec0-894a8125f429-image.png

    I don't really know if this is to be expected, but I'm thinking this is the reason my Bluetooth set-up doesn't work.
    Any tips? Help would be gladly appreciated ^^

    Software-versions:
    ViGEmBus 1.16.116
    and I think there's only one FireShock version (3.0.0.0)


  • To keep it complete, here's the log I got when I pulled the USB cable out (after connection)

    2020-03-14 22:09:24.338 +01:00 [Information] Launching Shibari, version: "1.5.166.0"
    2020-03-14 22:09:24.607 +01:00 [Fatal] Unhandled exception: "System.ApplicationException: This application can only be run once, please check if the service may be running already
       at Shibari.Dom.Server.Program.Main(String[] args)"
    2020-03-14 22:13:19.961 +01:00 [Information] Launching Shibari, version: "1.5.166.0"
    2020-03-14 22:13:21.376 +01:00 [Information] Loaded sink plugin "ViGEm Xbox 360 Sink"
    2020-03-14 22:13:21.517 +01:00 [Information] Loaded bus emulator "BthPS3 Bus Emulator"
    2020-03-14 22:13:21.532 +01:00 [Information] Starting bus emulator "BthPS3 Bus Emulator"
    2020-03-14 22:13:21.642 +01:00 [Information] BthPS3 Bus Emulator started
    2020-03-14 22:13:21.642 +01:00 [Information] Bus emulator "BthPS3 Bus Emulator" started successfully
    2020-03-14 22:13:21.642 +01:00 [Information] Loaded bus emulator "FireShock Bus Emulator"
    2020-03-14 22:13:21.642 +01:00 [Information] Starting bus emulator "FireShock Bus Emulator"
    2020-03-14 22:13:21.642 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&2#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&2")
    2020-03-14 22:13:21.704 +01:00 [Information] Device is DualShock3 with address "E0:AE:5E:6B:7C:4A" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:13:21.720 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got attached via USB
    2020-03-14 22:13:21.720 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:13:21.720 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    2020-03-14 22:13:21.720 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&1#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&1")
    2020-03-14 22:13:21.735 +01:00 [Information] Device is DualShock3 with address "64:D4:BD:3B:BE:25" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:13:21.735 +01:00 [Information] Device "DualShock3 (64:D4:BD:3B:BE:25)" got attached via USB
    2020-03-14 22:13:21.735 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:13:21.735 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    2020-03-14 22:13:21.735 +01:00 [Information] FireShock Bus Emulator started
    2020-03-14 22:13:21.735 +01:00 [Information] Bus emulator "FireShock Bus Emulator" started successfully
    2020-03-14 22:14:43.640 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" disconnected
    2020-03-14 22:14:43.641 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got removed via USB
    2020-03-14 22:15:17.156 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&2#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&2")
    2020-03-14 22:15:17.156 +01:00 [Information] Device is DualShock3 with address "E0:AE:5E:6B:7C:4A" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:15:17.156 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got attached via USB
    2020-03-14 22:15:17.157 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:15:17.159 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    

    And then when I tried again (with the other controller as well, just in case)

    2020-03-14 22:24:34.039 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" disconnected
    2020-03-14 22:24:34.039 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got removed via USB
    2020-03-14 22:25:49.929 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&2#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&2")
    2020-03-14 22:25:49.929 +01:00 [Information] Device is DualShock3 with address "E0:AE:5E:6B:7C:4A" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:25:49.929 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got attached via USB
    2020-03-14 22:25:49.930 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:25:49.932 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    2020-03-14 22:25:52.909 +01:00 [Information] Device "DualShock3 (64:D4:BD:3B:BE:25)" disconnected
    2020-03-14 22:25:52.909 +01:00 [Information] Device "DualShock3 (64:D4:BD:3B:BE:25)" got removed via USB
    2020-03-14 22:26:08.309 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" disconnected
    2020-03-14 22:26:08.309 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got removed via USB
    2020-03-14 22:26:40.012 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&2#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&2")
    2020-03-14 22:26:40.013 +01:00 [Information] Device is DualShock3 with address "E0:AE:5E:6B:7C:4A" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:26:40.013 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got attached via USB
    2020-03-14 22:26:40.013 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:26:40.015 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    2020-03-14 22:27:14.105 +01:00 [Information] Found FireShock device "\\?\USB#VID_054C&PID_0268#6&3B069A8E&0&1#{51AB481A-8D75-4BB6-9944-200A2F994E65}" ("USB\VID_054C&PID_0268\6&3B069A8E&0&1")
    2020-03-14 22:27:14.106 +01:00 [Information] Device is DualShock3 with address "64:D4:BD:3B:BE:25" currently paired to "00:02:72:A6:66:C4"
    2020-03-14 22:27:14.106 +01:00 [Information] Device "DualShock3 (64:D4:BD:3B:BE:25)" got attached via USB
    2020-03-14 22:27:14.106 +01:00 [Information] Connecting ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller"
    2020-03-14 22:27:14.108 +01:00 [Information] ViGEm target "Nefarius.ViGEm.Client.Targets.Xbox360Controller" connected successfully
    2020-03-14 22:27:20.329 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" disconnected
    2020-03-14 22:27:20.330 +01:00 [Information] Device "DualShock3 (E0:AE:5E:6B:7C:4A)" got removed via USB
    

  • Hello!

    Try this please.

    Cheers


  • Thanks for your reply ^^ So I tried to delete that and I reinstalled all the components, but I still can't seem to get the Bluetooth to work. Cabled works fine still, but he won't recognize anything on Bluetooth. The device manager look has changed however:

    35e0d184-036b-4437-b692-faf71c8c9bde-image.png

    Note: the registry file was deleted again after fresh installation, not quite sure if I got that right now.

    I've tried reinstalling after this, since my old drivers seem to be back and he can't find the bthps3 driver, but that ends up looking the same.


  • Nope, BthPS3 will never properly function as long as that exclamation mark is there. So far all I can recommend is apply the fix mentioned and try a re-install, I have no clue why this happens on some systems, sorry.


  • Tried to do that numerous times, the end-result keeps on staying the same. I'll try a full clean install somewhere soon but I highly doubt that will change anything. Thanks for thinking with me anyway, and I guess my Bluetooth adapter just isn't supported at the moment. Would you have any idea/examples of which adapters would or should work? Also, would you have any clue if this could be fixed by something similar to Zadig? I might try some things on my own in the meantime, and will keep this forum up to date if I ever do find a fix.


  • Basically any modern 4.0+ dongle works and latest Windows 10. No, Zadig would only worsen this case, it has nothing to do with these drivers and how they operate.


  • Got myself a new Bluetooth 4.0 dongle (wavlink csr 4.0 for those who are interested) and now everything is working like a charm! Guess my other adapter was just really outdated, can't even remember when/where I got it. Thank you so much for this elegant solution to the big ds3 problem! If you ever need any help in graphics (logo's, ui/ux design, video fx or anything) or in general, do let me know! I'd love to return the favor.


  • Great to hear! I am indeed in need of some UIX help here and there... 🤔


  • As long as it's on the design side of things rather than the coding, I'm sure I can help you out somehow 👌