I should note that I have run CIS with this HIPS setting for a long time, but it was only after an update I believe from 1903 to a higher Windows 10 build that I started to get these system locks when HIPS was not set to auto-block.
I recall this freeze would also occur if I ran Chrome browser for example, and any other application that asks for System Memory access. DS4Windows was just the latest culprit, since I just started using this app and figured I’d make the rules “quicker”.
Prior to that I’d usually only get a “hang” when a fullscreen application was launched just as it took control of the screen and/or keyboard, i.e. the usual “\KsecDD, Adf\Endpoint, AsyncConnectHlp” etc would go ok, then the game would go fullscreen and freeze… couldn’t even toggle numlock on/off at this point. but if I did a power-button-press and wait 4-5 minutes Windows would finally give me an option to kill the offending process through task manager (and also require a relog, as many other processes would be killed at this point)…
But I never had a freeze while I was only using the desktop and applications back then.
Edit:
The installation prompt appears after you launch the application, as it launches itself with a -install cmd which I believe is when it tries to run the ViGEmBus driver. You get a UAC prompt at this time.
This is the x64 installation using 64-bit .NET 6.0 runtime.
Edit2: I think I can avoid this problem i the future if I make a profile with “block” on System Memory and a few other things, and just have the rest set to “Ask”.
Course this also means I have to go through all previous applications and reconfigure them with this memory block. So it would be nice if it is fixed in CIS as well 
Thanks for a great product by the way! I always recomend this if someone asks.