My gut feeling is that your CIS registry config settings might be damaged or corrupt.
If I were you I would fully uninstall and install CIS again the recommended way.
That is:
Uninstall CIS via Windows Remove Programs.
Next and importantly run CIS cleanuptool to remove any remnants of previous CIS installation including any config settings in the registry.
Finally install CIS again and use a new fresh config setting (no import of older config setting as it may also be corrupt).
I understand the sigh, unfortunately the number of possible root causes is shrinking.
Maybe devs or mods can assist or help you resolving the issue in another way.
1: Version 12.2.4.8032
2: Win 10 Home 64 bit
3: Shotcut version 22.06.23 Shotcut - Download
4: Just MalwareBytes, but I don’t have it running and only use it as a “second opinion” scanner
5: Nothing I haven’t already shared here
6: If you mean other CIS features, I think it’s just the basic CIS with Secure DNS enabled
Really need to see the containment log as that will show what is being contained and why, also what containment alert did you get and how did you answer it? All you needed to do was choose don’t isolate again assuming its the same script that is getting auto-contained. FInally you can try switiching to a different config like the proactive configuration.
Import one of the new fresh config files (which were created by CIS during install time) found in the directory given below and see if that resolves the issue. (Do not export to, save to or overwrite the config files in this directory.)
Well, this is weird. Shotcut seems to work now, but the problem remains that I can’t run unknown status applications anymore without them getting auto-contained. And I can’t unblock them because they won’t show up on the list.
Are you kidding me… I created the rule and manually added the application as Trusted, and it still will contain it and show it as “Evaluation: Unknown” in the contained applications window.
What the hell is wrong with this thing…
Apparently it does now, but another thing I noticed checking the HIPS event list is WerFault also was blocked along with the application I tested. Either this CIS version needs some bugs fixed or I need to reinstall. AGAIN.
(Also, figure I’m going to change this topic’s title to better describe the situation if I can)