That would be the same result then? If the system shut down a request before the CIS alert was answered or timed out, then the "issue" would not have any changed permissions and we'd likely run into it sometime again later on.
Yes, a default deny/block will not be remembered, although it will be logged. I suspect that it is very likely that you will encounter it again. If, so.. and you're unsure, take a screen shot, post here & somebody will probably be able to give you solid advice on how to answer it.
And on the mouse, probably a few different exe's are needed for it, different functions, I bet there is a not often used feature of the mousepad that is currently denied by CIS, and it will show up again.
lol, the hard part is giving it permission with the mousepad froze. The keyboard only worked on the window that was open behind the alert. So it's a good thing the time out exists.
OK, once a default/deny is issued, whilst it is not remembered by CIS in the long term, it is remembered and deployed for the remainder of CIS' processes/drivers lifetime. ie. Reboot to clear it time.
Assuming you're happy with whatever is trying to happen is safe, there is a relatively painless way out.. stick Defense+ into Training Mode. Then do what provokes CIS's blocking behavior and if that means rebooting, do so. Once done, return Defense+ to its normal Mode and reboot for the final time. This usually is able to teach Defense+ everything it needs to know & resolve any issues. Actually Training Mode is very useful at introducing safe applications and games to CIS.
Author