MySQL Bugs: #115128: Password not generated while installing the mySQL Workbench

Bug #115128	Password not generated while installing the mySQL Workbench
Submitted:	26 May 7:30	Modified:	29 Jun 12:11
Reporter:	Vinod Guru	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	8.0.36	OS:	Windows (Microsoft Windows 10 Home Single Language)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\email\AppData\Roaming\MySQL\Workbench\log\wb.log]

I have installed the latest version of mySQL Workbench for practicing SQL queries in Windows OS.

Build version: Version 8.0.36 build 3737333 CE
Windows 11 Single

No root password generated, nor no password is shared after installation. Kindly provide the default password or share the steps to reset the password. 

Please resolve this issue ASAP. Looking forward to reply.

How to repeat:
Install the mySQL Build 8 version in Windows 11 OS
After installation, try to perform test connection
No connection established message appearing
This is due to no connection and to establish one we need root username's password.

Suggested fix:
Please share the steps to reset the password.

Hello Vinod,

Thank you for the bug report.
Please go through below documentation to install MySQL Server on Windows
https://dev.mysql.com/doc/refman/8.0/en/windows-installation.html

Regards,
Ashwini Patil

After reinstalling the mySQL Workbench again and when performing Test connection, the username and password prompt is appearing. Since password is unknown, the connection is failing. Please advise. Attaching the screenshot for reference.

Hello Vinod,

Thank you for the details.
Have you installed MySQL Server? If yes, you were prompted to set username and password to set up the connection while installing.

Regards,
Ashwini Patil

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".