Comments - Upgrading MariaDB on Windows
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I ran into this same error in Phase 5 when attempting to upgrade from 5.7 to 10.6 on a Windows 2016 server. It's a VM that I've been able to clone and test multiple times by reverting snapshots. I've gradually worked my way forward and found the service upgrade works with the latest versions of 10.2 through 10.5, all the way up to 10.6.12. I get the error if I try 10.6.13 or 10.6.14. Once I had a working 10.6.12 instance, I was able to upgrade in place to the latest version since it didn't require a service update. Version 10.6.12 was released in Feb, 10.6.13 in May and 10.6.14 in June. These other comments align with that timeline. Did something signficant change in the mysql_service_upgrade process between Feb and May that was propagated across versions?