Update:  We determined that this issue was caused by a third-party monitoring app which was monitoring the SQL Server service.  It was attempting to resolve the perceived failure by starting...

We've continued to see this issue randomly when patching SQL Server 2019 RTM so we opened a case with MS support, but they only suggested the following workaround. They were...

Hello,

Did you ever figure out the cause and/or the solution? We've encountered the same issue after applying SQL 2019 CU14.

thank you