Known limitation: There is an issue for MySQL 8.0.16 and higher that prevents the server from starting when the data directory from an earlier server version is reused for a new server installation. MySQL Server automatically initiates an upgrade when an existing data directory from an earlier server installation is reused and MySQL Installer does not process the upgrade as expected.
The workaround is to use the Upgrade operation in MySQL Installer, instead of removing the earlier server installation and then installing a fresh server instance that reuses the previous data directory. Alternatively, install a new server instance with the same version number as the data directory to be reused, then upgrade the server afterwards.
To remove an installed product, MySQL Installer often preforms other tasks, some are nonmandatory. The overall product removal operation can succeed even when a nonmandatory task fails. For better clarity when a nonmandatory task fails, MySQL Installer now sets the operation state to
Completed (with errors)and provides a reminder to evaluate the failed task. (Bug #30107754)
Previously, the MySQL Installer prerequisite engine made assumptions about the forward compatibility of certain installation requirements. The engine now reads more detailed information from the Windows registry and also adds support for executing WMI queries. When applicable, products installed with MySQL Installer can specify the precise version of a requirement rather than relying on the forward or backward compatibility among versions.
Package rules were evaluated only during the initialization of MySQL Installer and not when a common prerequisite was added by another product. Now MySQL Installer checks relevant rules prior to displaying the Check Requirements wizard page and skips the step if, for example, the Visual C++ 2015 Redistributable for Visual Studio requirement was satisfied during a previous installation. (Bug #30483081)
Thebutton remained disabled after MySQL Installer performed the steps to remove a product and changed the status to
Completed. The operation was unable to continue to the Removal Complete page. (Bug #30482915)
Links to the release notes of several MySQL products shown during the upgrade sequence produced an error when selected. (Bug #30397053)
On non-English Windows hosts, MySQL Server 5.6 and 5.7 could not be uninstalled when the product was configured to run as a Windows service. An error occurred because the MySQL MSI attempted to remove the MySQL service after MySQL Installer removed it. MySQL Installer now provides a property to alert the MSI at startup that the MySQL service is gone. In addition, the Remove Service step now executes only when the MySQL service exists and it was created by MySQL Installer. (Bug #30357245)
A newly created InnoDB Cluster instance could not be reconfigured (and recreated) as a new InnoDB Cluster instance because of a timeout condition on the operation. (Bug #30187962)
Product prerequisites for MySQL for Visual Studio were not identified prior to the installation step, which prevented a successful installation. (Bug #30085609)
In all cases, the connection test for MySQL Router failed with MySQL Server 8.0.1 (and lower) configured as a sandbox cluster. Improved validation now determines the role of a server within a cluster. (Bug #30058469)
Thebutton was improperly enabled when an invalid service name was entered on the Windows Service page. (Bug #29788953)
Some interactive messages were unclear. (Bug #29787992, Bug #30134184)