Inverse cloak ceases to work after restart

[d4maniac]

Using inverse application cloak to hide all controllers except one for a specific application.
Works the first time. Mixed to no results upon restart of PC.

"Controllers" connected:

Azeron kb - Cyborg 2
8Bitdo Ultimate 2.4ghz controller v2
8Bitdo Ultimate 2.4ghz controller v2
8Bitdo Ultimate 2.4ghz controller v1
8Bitdo Ultimate 2.4ghz controller v1
Xbox elite controller
Steps to reproduce
Standard installation
Inverse application
Chosen game to cloak controllers in
Cloak all active controllers (usually only 1, 2 and 6 are "on") except number 2.
Enable device hiding, disable and enable again
Restart controller
Works the first time but ceases to function after first restart. I have attempted to block all other HID devices including controllers that are not activate via 2.4ghz connection (+ non gaming HIDs) as they are not important for function but it doesn't change the fact that the it fails.

I tried adding a secondary browser and going to gamepadtester, which still shows that two controllers are connected.

I have tried to disable steam input. I don't use a ds4 controller.

Machine info
Windows 10, version 22H2
CPU AMD Ryzen 5950X
GPU RTX 4090
RAM 64GB DDR4

Grateful for any help

[davinchy2410]

Cross-posting this here since it's directly relevant: I wrote up a detailed repro + root-cause writeup on a related issue about inverse mode surviving reboots, in case it helps: #28 (comment)

Short version: in our testing (3 separate full PC reboots, standalone diagnostic independent of any whitelisted/blacklisted app), inverse cloak blacklist enforcement was still fully in effect immediately after boot every time, with no live re-toggle needed - so we weren't able to reproduce "stops working after restart" as described in this thread. Not sure if it's a different trigger (this thread hides all-but-one controller rather than blacklisting a single game exe) or something else, but wanted to flag our results here in case they're a useful data point either way.