Bug #92445 MySQLInstallerConsole update fails with 'Configuration file was not found'
Submitted: 16 Sep 2018 14:23 Modified: 17 Sep 2018 15:17
Reporter: BSOD 2600 Email Updates:
Status: Verified Impact on me:
Category:MySQL for Windows: Installer Severity:S3 (Non-critical)
Version: OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[16 Sep 2018 14:23] BSOD 2600
Per https://dev.mysql.com/doc/refman/8.0/en/MySQLInstallerConsole.html  one should be able to run "MySQLInstallerConsole update". This fails with:
"Configuration file was not found. Please resinstall a MySQL Installer bundle."

There is also a typo with "resinstall" in the error dialog.

screenshot: https://imgur.com/lIgHQm5

How to repeat:
msiexec /i mysql-installer-community- /qn
C:\>cd C:\Program Files (x86)\MySQL\MySQL Installer for Windows

C:\Program Files (x86)\MySQL\MySQL Installer for Windows>MySQLInstallerConsole update
=================== Start Initialization ===================
MySQL Installer is running in Commercial mode

<error dialog is shown>
[17 Sep 2018 7:33] MySQL Verification Team

Thank you for the report and feedback.
Observed reported issue on Win7 with *only* "mysql-installer-commercial-" installer i.e MySQL Installer is running in Commercial mode. Issue was not seen when MySQL Installer is running in Community mode

[17 Sep 2018 7:36] MySQL Verification Team
Commercial installer - screenshot

Attachment: 92445_commercial.png (image/png, text), 126.36 KiB.

[17 Sep 2018 15:17] BSOD 2600
Ah, good catch with the commercial vs community modes.

So even though the community installer was used, its defaulting to use commercial mode.   No where in the ' MySQLInstallerConsole Reference' does it mention the modes to be used.  IMO, as the community installer was used, it should be defaulting to community mode. separate bug?