Hide DS4 is broken on windows 10 build x64 1607

[fabricioanciaes]

Seems like microsoft broke it again,

Apparently you can get it working by disabling and re-enabling a certain bluetooth device.

There's a video from input mapper dev showcasing this solution: https://www.youtube.com/watch?v=XcnEON9fYSk

Could a way to automate this be implemented on DS4Windows?

Thanks in advance.

[mastafreak]

Yup, I ran into the same problem too after the 1607 upgrade.

[martea]

Also have the issue since the update last night, can you somehow get a log that i can provide?

[Willyum1]

Same here, hopefully it can be fixed

[mastafreak]

I followed this and it worked, you guys might want to try it too.

https://www.youtube.com/watch?v=EsfsTfZnPh8

[Willyum1]

Thanks that worked. Make sure DS4 is closed, go into device manager to human interface devices, right click on Bluetooth hid device, disable it. Enable it, then try to open DS4 and see if the warning is still there.

[antervud]

works for me too

if i connect it with the microusb cable can't have the exclusive mode

ideas?

[miclud]

In the video that was linked, he mentioned he'd create a script. It can be found here https://inputmapper.com/20-windows-10-1607-au-exclusive-mode-fix When I used that with DS4 connected through microsub cable it worked. Just make sure the DS4Windows is closed, then run the script, and open DS4Windows again and it should work.

[halsafar]

go into device manager to human interface devices, right click on Bluetooth hid device, disable it. Enable it, then try to open DS4 and see if the warning is still there.

That worked! I've been without exclusive mode for awhile now.

[NoobTW]

I have no idea why it isn't working. Windows 10 (1607), too.

[ted423]

@NoobTW the mastafreak's video may help you https://www.youtube.com/watch?v=EsfsTfZnPh8

[teokp]

So I made DS4Windows automate this re-enabling process when it detects that it can't open the device in exclusive mode.

I think the problem was because Windows 10 now automatically open gamepads in shared mode, which stops DS4Windows from accessing exclusive mode, re-enabling the device drops the opened handle.

[gpregger]

Just managed to build your fork @teokp and that's probably about as convenient as it gets, nice job :)

[antervud]

@AhMaizeBalls can u share the build?

[gpregger]

@antervud not sure how proper that is but here you go: [https://www.dropbox.com/s/42rld5dgdr3oaqk/DS4Windows.exe?dl=0]()

[shinra358]

@teokp think you can make an automatic xinput port changer option? 80 percent of all problems on the website consists of having to change the xinput ports manually and ppl not knowing. I've had to change mine manually a few times because for some reason, after a while, turning on 2 controllers makes them share 1 xinput position in the joy.cpl instead of their own separate positions. And sometimes the controller just doesn't work (lights come on but no connected sound). This would be a great fix for everyone.

[teokp]

@shinra358 Sorry i dont think i can help with that. i only have 1 ds4 so i havent had this problem before.

[Ronnsens]

Hey,

is there still now fix to get the "exclusive mode" working under win 10 1607?

[ted423]

@Ronnsens have you try 1.4.5? https://github.com/Jays2Kings/DS4Windows/releases/tag/v1.4.5

[gpregger]

Siiick, since 1.4.5 includes teokps fix it will work around the exclusive mode issue, awesome!

[briankendall]

Thanks teokp for that fix! Not only does it apparently fix the Windows 10 issue, but there's many times previously when I'd turn on my ds4 controller and exclusive mode wouldn't work due to another app preventing it, often Steam. With this fix, exclusive mode consistently works!

Also, for those interested, if you launch DS4Windows as an administrator then you don't have to be bothered by the UAC prompt when the exclusive mode fix is triggered.

[dinosauriac]

So I just got the "creator's update" and ran into this problem with exclusive mode for the first time. I've tried every potential workaround I've seen listed here to no avail. The project homepage says there's current issues with Windows 10 and exclusive mode, and to check the website for more info... but there's nothing further on the actual website.

Edit: I've looked around abit and InputMapper when combined with HIDguardian seems to be the way to go. It's a real shame that DS4windows doesn't seem to wanna play ball, it was a beautiful simple little program unlike InputMapper which seems overly GUI-ey while somehow being less user friendly.