In reply to
"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!"
I'm a Mainframe Systems Programmer with 40 years experience ( mostly assembler, machine language, and Unix) and figured out they do not have an embedded copy. If they did it would work regardless of what Microsoft did to IE since they would have their own internal version. After a few hours of poking around I figured out the call to IE11 after it has been discontinued fails. IT IS A CALL like calling an API not a branch to an embedded copy. With Edge now supporting IE compatibility I learned that by turning that on, the servicing call FROM QB to IE11 is redirected to Edge and works like a champ. I can once again use my QB Pro 2015.
