MySQL Workbench / Windows 10 Compatibility Checks and Installation

MySQL Workbench is a MySQL management client installed on Windows using an MSI package. If you want to use it on Windows 10, first check the operating-system support of the release you intend to install. The current official installation manual specifies Windows 11 or Windows Server 2022, so downloading the newest package does not establish Windows 10 support.

On Windows 10, check support conditions first

General support for Windows 10 Home and Pro ended on October 14, 2025. Do not confuse that lifecycle with LTSC editions that have separate support periods or with the conditions of Extended Security Updates. For a new development environment, first consider moving to a supported operating system and then installing Workbench.

If you must retain an older environment matching this article’s Windows 10 topic, separately verify the Workbench version approved by your organization, that release’s supported operating systems and its security-maintenance status. Finding a file in Archives does not guarantee current support or safety. Do not treat forcing an unsupported installer to run in compatibility mode as the default solution.

The current Windows installation manual lists Windows 11 or Server 2022, .NET Framework 4.5.2 and the Visual C++ Redistributable 2015–2022 as prerequisites. The newest download and the version used in a manual’s examples may differ. Check both the requirements shown by your selected installer and the release documentation, obtaining missing components from Microsoft’s official distribution channels. You do not need to remove a runtime that already meets the requirements or replace it with an older one without a reason.

Installing Workbench and installing a database server are different tasks

Workbench is a client for connecting to servers, running SQL (Structured Query Language) statements and modeling databases. Installing Workbench alone does not automatically create a MySQL server service or a server account. Modeling can be done without a server connection, but executing actual SQL requires a running MySQL server and permission to connect.

Prepare local connection details if the server is on this PC, or the address, port, account and TLS or SSH connection policy supplied by the administrator if it is on another computer. TLS (Transport Layer Security) protects network connections; SSH (Secure Shell) can provide a secure connection route when configured for the server. Reinstalling Workbench does not reset a server password you do not know. The commonly illustrated local address 127.0.0.1 and port 3306 apply only when they match the actual server configuration.

The official Workbench introduction describes its MySQL features and notes that compatibility of some functions depends on the server version. Even if a MariaDB connection succeeds, this does not guarantee compatibility of administration, backup or modeling features. If you need a tool for MariaDB, check the particular operations and server version separately.

Choose the Windows installer on the official website

1. Open the MySQL Workbench Community download page. Distinguish it from similarly named products such as MySQL Community Server.
2. Check the required version under Select Version and Microsoft Windows under Select Operating System. Windows (x86, 64-bit) identifies an x64 package, rather than a 32-bit installer. Also check System type under Windows Settings → System → About.

An x64 MSI filename can look like mysql-workbench-26.10.0-winx64.msi. Treat this as an example of the product, version, architecture and package format rather than a requirement to find that exact release. Version numbers, download sizes and page layouts can change. A Windows download listing does not prove Windows 10 compatibility.

3. Select Download for the chosen file. If an Oracle account screen appears, the No thanks, just start my download. link lets you download without creating an account.
4. Check that the downloaded file matches the chosen product and version. Review its digital signature in file properties and the official page’s package-verification guidance. Do not use an installer from a redistribution site whose origin you cannot establish.

What to choose in the MSI installation wizard

The following is the basic standalone-MSI flow described by the official Windows manual. Proceed when the selected release supports the operating system and its prerequisites are met. On a company PC, first check installation rights and management policy. If another version is already installed, save connection settings, model files and open SQL files, check the upgrade conditions, and close the existing Workbench.

1. Run the MSI and continue with Next in the setup wizard. If a privilege-elevation prompt appears, check the program name, publisher and file path against the package you just downloaded, then approve using an account with installation rights.
2. Check the installation location. Use the default unless you have a deployment requirement. You do not need to enter a Workbench 8.0 example path from the manual for a different release.
3. If Setup Type is offered, Complete installs all Workbench components, while Custom lets you select components or a location. Complete here does not mean that MySQL Server is also installed.
4. Review the summary and select Install. If your version displays license terms, read them and decide whether to agree. When installation finishes, select Finish and launch Workbench.

The screens for MySQL Installer, which manages multiple MySQL products, differ from this standalone-MSI route. A standalone file makes the intended product clear when you only need Workbench. If installation reports a missing prerequisite, record its name, resolve that requirement and try again. Avoid downloading an individual DLL from an arbitrary website and copying it into the program folder.

Launch Workbench and check the connection with a read-only query

Open MySQL Workbench from the Start menu. Reaching its home screen confirms that the application starts; a successful database connection needs a separate check. Following the official connection-creation guide, add a connection with the + button beside MySQL Connections.

1. Enter a recognizable Connection Name. For a simple local network connection, choose Standard (TCP/IP) under Connection Method and enter the actual Hostname, Port and Username.
2. Select Test Connection. If a password is requested, enter the password for that server account. For a remote server, use the TLS certificate-verification or SSH method required by its administrator. Do not disable encryption or authentication merely to remove an error.
3. After a successful test, save with OK and open the connection to reach the SQL editor. Enter and execute the read-only statement below. If other statements are present, select only this statement before executing it.

SELECT 1 AS connection_ok;

A result grid with a connection_ok column and one row containing 1 shows that a request reached the server and returned a result. This basic check does not create or delete tables or data. It does not validate every administrative feature, so verify the permissions needed for your actual work separately. On a shared PC, do not choose to store the password, and close the connection when finished.

Distinguish startup and connection errors, and uninstall when needed

• The program itself does not open: first compare operating-system, architecture and runtime requirements. An installation-complete message does not prove supported operation on Windows 10. Record the full error and the selected Workbench version.
• Connection refused or timeout: check whether the server is running, its address and port, and the network route rather than focusing only on Workbench installation. Do not expose the database port to the entire internet in an attempt to fix a client error.
• Access denied: check the server account name, password and permissions for the source of the connection. A Windows login password and a MySQL account password are separate credentials.
• Version or feature-compatibility warning: consult release documentation for the particular administrative operation even if a connection works. Do not immediately change a production server’s version solely because a warning appears.

If an unfinished setup offers Cancel, use that option to stop it. To remove an installed copy, close Workbench and use Windows 10 Settings → Apps → Apps & features, select MySQL Workbench, and uninstall it. Do not remove other products such as MySQL Server along with it.

Removing Workbench is separate from deleting server data, and connection settings or personal model and SQL files may remain. Keep the files you need before removal and decide separately whether to reuse previous settings after reinstalling.