I just started getting this same error. None of the things PG support asked me to try had any effect. I still get the error.
I'm on the latest version of Win11 Pro.
Question to those of you also experiencing this access violation: are you on the latest version of Win11? Is it possible that a recent Windows update is responsible?
I don't mean to suggest that I'm happy about the situation, but I'm happy that I'm not the only one. That tells me that there's a real problem.
Now, after doing a full reset to factory defaults, I've got to try to remember how I got my BiaB UI set up the way I did. Sigh.
Last edited by TheMaartian; 05/10/24 11:23 PM.