Yes, Intuit has known about this issue since at least May 27, 2022 when this thread started, and reps continue to post and re-post the same tired suggestions that don't work.
And of course they don't work, because they are not capable of fixing whatever bugs Intuit introduced in the last patches when it replaced the embedded browser (which was IE) with their own buggy little solution, at the very last moment before MS pulled support, though we knew this would happen for over a year. Based on some Windows errors I've reviewed, I think they licensed the new browser (the one that doesn't work and crashes QuickBooks constantly) from some little company, so they may have little control over it. How clever.
This seems typical of Intuit development, now in India, over the last several years. Getting them to fix anything, much less do it fast, seems impossible.
