Introduction

If you installed MySQL on Windows and cannot find my.cnf, the first thing to know is that Windows often uses my.ini instead. The MySQL server can read either extension, but Windows installers and documentation usually favor .ini, which is why Linux-oriented instructions can feel misleading on a Windows machine.

Why You Usually See my.ini on Windows

On Unix-like systems, MySQL configuration is traditionally stored in my.cnf. On Windows, the server checks Windows-style option files too, and many installations create my.ini by default.

In other words, “I cannot find my.cnf” often really means “the config file exists, but it is named my.ini.” The contents are the same style of MySQL option groups such as [mysqld] and [client].

A minimal Windows config file might look like this:

1[mysqld]
2port=3306
3basedir=C:/Program Files/MySQL/MySQL Server 8.4
4datadir=C:/ProgramData/MySQL/MySQL Server 8.4/Data
5
6[client]
7port=3306

The syntax is identical whether the file is called my.ini or my.cnf.

Where MySQL Looks on Windows

According to the MySQL reference manual, Windows builds search several locations for option files. Common locations include:

• '%WINDIR%\my.ini'
• '%WINDIR%\my.cnf'
• 'C:\my.ini'
• 'C:\my.cnf'
• the MySQL base installation directory, such as C:\Program Files\MySQL\MySQL Server 8.4\my.ini

MySQL Installer often creates my.ini in the base installation directory, which is why many Windows users never see a my.cnf file at all.

If the file extension is hidden in Explorer, you can also miss it visually. A file shown as my might actually be my.ini.

How to Discover the Active Config File

The most reliable way to see how your server was started is to inspect the service configuration or ask MySQL about its defaults.

From Command Prompt, one useful check is:

mysqld --verbose --help

That output is long, but it includes the default option-file search paths for the server binary.

If MySQL is running as a Windows service, you can inspect the service command line too. In PowerShell:

Get-CimInstance Win32_Service |
  Where-Object { $_.Name -like "*MySQL*" } |
  Select-Object Name, State, PathName

If the service was installed with --defaults-file=..., the exact config path will appear there. That overrides the normal search order and is often the answer in manually configured environments.

Creating the File If It Does Not Exist

A missing file is not automatically a problem. MySQL can start with built-in defaults. But if you need custom settings, create one plain-text option file and point the service at it or place it in a searched location.

For example, create:

C:\Program Files\MySQL\MySQL Server 8.4\my.ini

Then add only the settings you actually need. Avoid copying a huge sample file full of irrelevant values. Smaller configs are easier to audit and troubleshoot.

If you already have one active file, do not create a second competing file casually. Multiple option files can be valid, but they make debugging harder because later files can override earlier ones.

my.ini vs mysqld-auto.cnf

Modern MySQL installations may also contain mysqld-auto.cnf in the data directory. That file is not a replacement for your handwritten server config. It stores persisted system variables written with SET PERSIST or SET PERSIST_ONLY.

So if you see:

C:\ProgramData\MySQL\MySQL Server 8.4\Data\mysqld-auto.cnf

that does not mean you found the traditional main config file. It is a different mechanism.

Practical Troubleshooting Steps

A good Windows checklist is:

1. Search for my.ini as well as my.cnf.
2. Check the MySQL installation directory.
3. Check C:\ and %WINDIR%.
4. Inspect the Windows service PathName for --defaults-file.
5. Run mysqld --verbose --help to confirm the search order.

That sequence is usually faster than guessing based on Linux tutorials.

Common Pitfalls

The biggest pitfall is assuming Windows must use my.cnf. In practice, my.ini is often the real file you want.

Another issue is editing the wrong file when multiple option files exist. MySQL reads more than one location, and later files can override earlier ones.

Developers also sometimes confuse mysqld-auto.cnf with the main hand-edited config file. It serves a different purpose.

Finally, if MySQL runs as a Windows service with --defaults-file, the active config may be outside the normal search locations entirely.

Summary

• On Windows, MySQL often uses my.ini instead of my.cnf.
• The server can search several locations, including %WINDIR%, C:\, and the installation directory.
• MySQL Installer commonly creates my.ini in the base installation directory.
• 'mysqld-auto.cnf is not the same as the main option file.'
• The safest way to find the real config is to inspect the service command line or run mysqld --verbose --help.