I've noticed what I consider to be a large number of questions/issues raised on the Q&A Forum regarding PB applications experiencing performance problems and/or suddenly stopping/crashing... and in many/most of these cases, disabling of PB's used of Microsoft Accessibility features resolves or helps to resolve the issue.

I seem to recall seeing word that in PB 2022, PB's use of MS Accessibility will be disabled by default, which I think is a prudent move given the limited need and use of Accessibility and the plethora of problems being reported. I'm concerned, however, that users needing this functionality have no workable option... They don't have use of Accessibility features if the functionality is enabled, but the app experiences a higher risk of crashing and/or experiences significant performance degradation if it's enabled. Neither option is good.

I'd very much like to know more about what is causing PB's problem when Accessibility is enabled. Does Engineering know what is causing the issue(s)? Is the problem on Microsoft's side? (yeah, that NEVER happens). What is the prognosis for use of this functionality in the future?

-John