I'm a programmer and can tell you you're out of luck.  The way they built QB is to embed a copy of the IE11 engine into it  - so it is not like they can update a setting to use another browser.  They'd have to go back and re-engineer QB2019 - a product that will soon loose support by May 2022.  It is an antiquated programming design which leaves you to the mercy of the owner of that engine - though wouldn't fault MSFT here because they have many. many years communicated to the developer community NOT to do what QB has been doing.  So in a way, this is planned functional obsolescence and timed just right for the shiny new QB2022.  enjoy!

My reply...

Thank you for the insight, and I expected the same plan to replace IE11. Sadly, it seems that the shiny 2022 version hasn't fixed the problem and is now reliant on Edge with IE11 enabled AND has an annual subscription fee instead of a buy and replace at obsolescence or at your leisure if you can get by with it. Another thread I was on about the same problem has blown up in the last two weeks over this issue as 2022 users are struggling. It's a poor workaround and not a solution as you point out that it has been many years in the making that IE would be gone. I hope your QB work is continuing successfully though. Thank you again for your comment.