Introduction

This Windows error means the shell cannot find mysql.exe when you type mysql. In practice, that usually means one of two things: MySQL is not installed where you think it is, or the directory containing mysql.exe is not on the system Path.

Verify That the MySQL Client Exists

Before changing environment variables, make sure the command-line client is actually installed. On a typical Windows installation, the executable often lives in a path similar to:

C:\Program Files\MySQL\MySQL Server 8.0\bin

You can test it directly from Command Prompt:

"C:\Program Files\MySQL\MySQL Server 8.0\bin\mysql.exe" --version

If that works, the MySQL client exists and the real problem is path configuration. If it does not, the installation may be incomplete, or the executable may be in a different folder than expected.

Add the bin Directory to Path

Windows resolves commands by searching the directories listed in the Path environment variable. If MySQL's bin directory is missing from that list, the shell cannot find mysql.

You can add it through the Environment Variables UI:

1. Open "Edit the system environment variables".
2. Open "Environment Variables".
3. Select Path under either user variables or system variables.
4. Add the MySQL bin folder path.
5. Open a new terminal window.

After that, verify with:

where mysql
mysql --version

where mysql is especially useful because it shows exactly which executable Windows is resolving.

Use the Full Path as a Temporary Workaround

If you need to connect immediately and do not want to edit Path yet, call the executable directly:

"C:\Program Files\MySQL\MySQL Server 8.0\bin\mysql.exe" -u root -p

That is not a permanent fix, but it confirms the client works and isolates the issue to shell lookup rather than database connectivity.

This distinction matters because "mysql is not recognized" is a command-discovery problem, not a login or password problem. You fix it before the client ever tries to contact the server.

Do Not Confuse Server Installation with Client Availability

Some users install MySQL Server through a bundled tool and assume the CLI client will automatically be available in every terminal. That is not guaranteed. The server, Workbench, and command-line client are related, but they are not the same thing operationally.

You can have:

• a running MySQL server
• MySQL Workbench installed
• no working mysql command in Command Prompt

That is why checking the executable path is the first meaningful troubleshooting step.

PowerShell and Command Prompt follow the same basic lookup rule here. If the executable directory is not on Path, both shells will fail to resolve mysql by name even though the database software itself may be installed correctly.

Common Pitfalls

The most common mistake is editing Path correctly but continuing to use an already-open terminal window. Existing shells do not automatically reload environment-variable changes, so you need a new terminal session.

Another issue is adding the wrong directory. The folder that matters is the one containing mysql.exe, usually the bin directory, not the parent MySQL folder.

People also sometimes have multiple MySQL or MariaDB installations. In that case, where mysql may reveal a different executable than the one you expected.

Summary

• This error means Windows cannot locate mysql.exe from the current shell.
• First verify the client exists by running it with its full path.
• Add the MySQL bin directory to the Path environment variable for a permanent fix.
• Open a new terminal after changing Path.
• Use where mysql and mysql --version to confirm that Windows now resolves the command correctly.