latest update broke the entire software.

[ZiYou777]

uninstalled drivers, rebooted countless times.

with cable, with bluetooth..

nothing works, DS4 won't detect my controller.

I can connect to my PC via bluetooth, but no input is allowed.

all drivers deleted, system restore.. nothing works.

it's like its perma bricked, usb bluetooth, controller all works fine on other pc..

When i start ds4windows exe.. no popup, starts up fine.. detects nothing, press control panel/drivers =

"Install driver"

installs, then all the new files dissapear from the folder and everytime I open the driver installl. repeat.

installs, deletes, installs, deletes.

T_T

[ZiYou777]

INFO - ENTER: DriverPackageInstallW INFO - Looking for Model Section [SCProductions.NTamd64]... INFO - Installing INF file 'C:\Users\Laviticus\Documents\DS4Windows\Virtual Bus Driver\System\ScpVBus.inf' (Plug and Play). INFO - Looking for Model Section [SCProductions.NTamd64]... INFO - Installing devices with Id "Root\ScpVBus" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\scpvbus.inf_amd64_21ca245c0e23d7a5\scpvbus.inf". INFO - Will force install because driver is not better and force flag is set. INFO - ENTER UpdateDriverForPlugAndPlayDevices... SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices. INFO - Installation was successful. SUCCESS - Install completed INFO - RETURN: DriverPackageInstallW (0x0)

[Ghaleon4]

What you describe here sounds very similar to my own issue: https://forums.vigem.org/topic/14/wireless-controller-invisible-unless-i-remove-my-ds4-s-hardwareids-from-affecteddevices/5

[mika-n]

installs, then all the new files dissapear from the folder and everytime I open the driver installl. repeat.

I didn't understand what you mean by that? Dissapear? What files? Files from a profile folder or VirtualBus zip file and extracted folder during driver installation?

What version of DS4Windows are you using? Please note that Jay2King version of DS4Windows is an obsolete version and not exactly the same as hosted on this Github page even when those two share the same root DNA and program name.

Try to close all Steam/UPlay/Origin/GForceExperience or any other app which might natively use DS4 controller (and locking it in use) before running this DS4Windows tool installer or the app itself.

If you have used some other DS4 driver apps or HIDGuardian tools then uninstall all of those to see if the "vanilla version" of DS4Windows app works.

Anyway, please try to download and install the ScpVBus driver manually before running DS4Windows executable because the "Install and Download ScpVBus" button in the installer didn't work for me (it failed to download the driver installation zip file). But when I downloaded the ScpVBus driver manually and installed it that way then this Ryochan7-DS4Windows started to work. See this post: https://github.com/Ryochan7/DS4Windows/issues/475

[Ryochan7]

This issue could be a result of one executive decision made with version 1.5.15 to remove support for HidGuardian. It is posted in the change log and in issue #479. I will copy pasta a workaround that I posted there.

As of version 1.5.15, if you are using HidGuardian then you have to either change the AffectedDevices registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters\AffectedDevices) used by HidGuardian and perform a device hotplug or use some kind of software like WhiteKnight to whitelist DS4Windows temporarily and perform a device hotplug. The "Hide DS4 Controller" option is now the only supported way of hiding the DS4 from other applications.

If you are using HidGuardian and have the DS4 hardware id in the AffectedDevices list, DS4Windows will not detect the DS4 but the device should still show up in the Windows Device Manager. I didn't use HidGuardian regularly anyway and the performance of recent updates is not good for me; I tested version 4.1.126.0.

[ZiYou777]

This issue could be a result of one executive decision made with version 1.5.15 to remove support for HidGuardian. It is posted in the change log and in issue #479. I will copy pasta a workaround that I posted there.

As of version 1.5.15, if you are using HidGuardian then you have to either change the AffectedDevices registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters\AffectedDevices) used by HidGuardian and perform a device hotplug or use some kind of software like WhiteKnight to whitelist DS4Windows temporarily and perform a device hotplug. The "Hide DS4 Controller" option is now the only supported way of hiding the DS4 from other applications.

If you are using HidGuardian and have the DS4 hardware id in the AffectedDevices list, DS4Windows will not detect the DS4 but the device should still show up in the Windows Device Manager. I didn't use HidGuardian regularly anyway and the performance of recent updates is not good for me; I tested version 4.1.126.0.

Deleting AffectedDevices entirely from the registry fixed it...

please! i beg of you, make it automatic in the next update, i know 99% of the people having issues with detection, this will fix it for them.

and for casual users may be to advanced for them to do themselves.

i love ur software @Ryochan7

thank u for it!! but it would be great if u can make it so for the next update, u auto delete that reg key.

nobody needs shitty hidguardian if ur software works iwthout it, thx and love!

[reecespieces]

I had this problem myself and I was able to fix it.

Instead of messing with the registry at all like suggested above, just remove HID Guardian.

Go to Device Manager -> System Devices

Right click on "HID Guardian" and choose uninstall, make sure to check remove software to get a full uninstall.

This is much easier and you don't risk accidentally fucking up your registry.

[Ryochan7]

HidGuardian uninstall instructions

https://docs.vigem.org/#!hidguardian-v1-installation.md#Driver_removal

HidGuardian is charting new territory so having absolute perfect performance is a bit much to ask. I would hope that performance gets better over time though. HidGuardian has its use case but version 4 is a no go for me at this point.

Other software, including software that uses the DS4, utilize HidGuardian so I don't plan to add any routine to remove or alter the AffectedDevices registry entry. That will likely cause even more problems than people are having now. The recommended route at this point is to run WhiteKnight to whitelist DS4Windows temporarily.

https://autohotkey.com/boards/viewtopic.php?p=164497

DS4Windows has had its ups and downs over time. I try to make DS4Windows less shitty with each release though.