Avast Premium Security is interfering with Visual Studio IDE

I develop apps with Visual Studio 2019 and within the last week Avast has started popping up the “Checking this file…” message every time I try to run the VS2019 debugger. It will complete the scan and ask to create an exception, I say OK, and then the debugger will run.
The issue is that in development, one goes back and forth from debugging to the IDE to make changes, etc. And when you re-run the debugger you get the same message and have to go through the create exception, etc., before you can continue. When you’re creating an app you might do this dozens of times an hour, and this behavior of Premium Security getting in the way is unacceptable
Now, I realize that in code development changes will create a new executable when you go to debug. But, come on Avast, what’s the point of the initial exception if I have to go through that popup, scan, and new exception ordeal every time I debug?
I found that the culprits for this behavior are Rootkit and Exploit detectors. If I disable both of those everything works fine. I’ve created several exceptions for the Visual Studio program folder, the Project Folder, and any other items I can find that are related to Visual Studio 2019. None of that helps, it’s as if the Rootkit and Exploit protection IGNORES all these exceptions!
What good is creating exceptions if they aren’t obeyed?
This has not happened in the past, just recently, about a week ago. Whatever Avast did with recent updates they created this unacceptable interference with code development and Visual Studio debugging.
I can leave Rootkit and Exploit protection off, but why should I have to increase the risk of something sneaking in to my system?

Has anyone experienced anything like this? It’s really annoying for a paid Antivirus program to not get this working properly. If you’re listening Avast, please fix this. When I create an exception I am telling Avast to NOT TOUCH what’s being excepted and trust my decision, but apparently Premium Antivirus isn’t following the exception list, and Avast needs to fix this.

It looks like CyberCapture to me, are you really sure it is Rootkit shield? Can you post screenshots?

Years ago when I used Visual Studio 2010, CyberCapture (DeepScreen or autosandbox at that time iirc) did the same thing and I added whole Project directory into CyberCapture-specific exception list. Even with latest Avast, you can configure which exceptions should be applied to each shields.

Please note some shield/functions does not support exceptions, like vulnerable driver blocking.