- Posts: 3
- Thank you received: 0
Demon King wrote: It had fixed both
Unfortunately, update 1709 broke exclusive mode again, and this time not even a full reinstall of IM + HidGuardian fixed it. So we're back where we started...
Many headaches can be saved by switching over to the Windows 10 "business" branch which will delay so-called "feature" updates. The regular consumer branch is in essence a beta Microsoft foists on regular users whose stability/compatibility they consider less important than their real customers in "business". On top of that, those "feature" updates (the new builds that break things) can be delayed up to an additional 365 days if you so choose.
This doesn't affect simple bug fixes or security fixes which everyone gets at the same time.
tayedash82 wrote: Yeah same here for now I'm using the Xbox one controller till they fix it
wirenut48 wrote: Double click AffectedDevices then cut and paste the two lines below to the end of the white list.
You have to edit the AffectedDevices registry value via regedit in order for HidGuardian to take control of the device.
The file generated by InputMapper does not include the device instance path for the version 2 DS4 controller so HidGuardian will not be used. Here are the lines that should be used for a version 2 controller. The first line is for a USB connection and the next line is for a BT connection.