SQL Server Doesn't Start Automatically

Question

SQL Server Doesn't Start Automatically

Waldemar Czarnecki 40

Good morning.

After starting my computer, the SQL Server instance doesn't start automatically. I have to start it manually by restarting the service. This happens in both startup modes: automatic and automatic (delayed start).

SQL Version: Microsoft SQL Server Express (64-bit) 16.0.1180.1

System Version: Windows 11 Pro, Version 25H2, Build 26200.8737, Windows Feature Experience Pack 1000.26100.334.0

Why?

W. Czarnecki

Erland Sommarskog 135.4K Reputation points MVP Volunteer Moderator

2026-07-04T10:50:28.1733333+00:00

First of all, you are running the RTM version of SQL 2022 with only security fixes. You should download an install the most recent Cumulative Update to get access to many fixes and improvements. That alone my not address this particular issue, so we should dig a little deeper.

When you say that it doesn't start, how do you notice this condition? Do you try to connect to SQL Server from SSMS quite directly after you have started your machine? Starting with SQL 2022, SQL Server always runs with delayed start, and it can take a couple of minutes after you have started your computer before SQL Server is available. On the other hand, if you cannot connect 15 minutes after you started your computer, there is something to investigate.

1 answer

Your answer

Erland Sommarskog 135.4K Reputation points MVP Volunteer Moderator

2026-07-04T10:50:28.1733333+00:00

First of all, you are running the RTM version of SQL 2022 with only security fixes. You should download an install the most recent Cumulative Update to get access to many fixes and improvements. That alone my not address this particular issue, so we should dig a little deeper.

When you say that it doesn't start, how do you notice this condition? Do you try to connect to SQL Server from SSMS quite directly after you have started your machine? Starting with SQL 2022, SQL Server always runs with delayed start, and it can take a couple of minutes after you have started your computer before SQL Server is available. On the other hand, if you cannot connect 15 minutes after you started your computer, there is something to investigate.

Answer 1

The behavior indicates a startup problem with the SQL Server service rather than a simple Start Mode setting. Several known causes from the documentation match this scenario, especially when SQL Server is configured for Automatic (Delayed Start) but still fails to come up until started manually.

Use these checks to identify and fix the root cause:

Check SQL Server startup errors (primary step)
- Open Event Viewer → Windows Logs → Application and System.
- Look for errors from MSSQLSERVER or your named instance at boot time (for example, Error 1067, 1069, 7000, 7038, “service did not respond in a timely fashion”, “The specified domain either does not exist or could not be contacted”, “The system cannot find the file specified”).
- Then review the SQL Server error log for the same time period. The startup errors article explains that the exact error text determines the fix and maps common messages to detailed troubleshooters.
Confirm service Start Mode and delayed start behavior
- In SQL Server Configuration Manager → SQL Server Services, verify the Start Mode for the instance is set to Automatic.
- On SQL Server 2022 and later, when Start Mode is set to Automatic, Windows actually uses Automatic (Delayed Start) under the hood. This is by design to allow other services (like NetLogon, NIC teaming, etc.) to initialize first. If the instance still does not start, it usually means a dependency or configuration issue, not the Start Mode itself.
Check for dependency/network timing issues (NIC teaming / NetLogon)
If the machine uses NIC Teaming or domain logon at startup, SQL Server can try to start before the network or NetLogon is ready and fail with a logon or domain error, then remain stopped until started manually.
- For NIC Teaming scenarios (Event ID 7038 with “The specified domain either does not exist or could not be contacted”):
  - Set the SQL Server service Startup type to Automatic (Delayed Start) in Services (already done in your case, but confirm).
  - Optionally configure a scheduled task to start the SQL Server service with a short delay after boot.
  - For SQL services, set Recovery → First failure and Second failure to Restart the Service so that a transient startup failure is retried automatically.
- For standalone servers where NetLogon timing is the issue:
  - Ensure NetLogon is set to Manual on standalone machines.
  - Configure SQL Server to Automatic (Delayed Start) and/or set Recovery options to Restart the service on failure so it retries once the network is ready.
  - If delayed start alone does not help, add dependencies so SQL Server waits for key services:
```
       sc.exe config MSSQLSERVER depend=iphlpsvc/LanmanServer/netprofm
```
    (Use the actual service name for your Express instance, e.g. MSSQL$SQLEXPRESS.)
Verify the SQL Server binary and paths (Event ID 7000)
- If the System log shows Event ID 7000 with “The system cannot find the file specified”, check that Sqlservr.exe still exists in the SQL Server installation folder.
- If it is missing or renamed, repair the SQL Server installation using the documented repair procedure.
Check service account and domain availability (Event ID 7038 / 1069)
- If the event text includes “The specified domain either does not exist or could not be contacted” or a logon failure, the SQL Server service account may be a domain account that cannot authenticate at boot.
- Ensure the domain is reachable at startup, or change the service to use a suitable local account if domain logon is not guaranteed.
- For locked or misconfigured accounts, unlock the account in Active Directory and update the same credentials in SQL Server Configuration Manager and Services, then restart the service.
Use the startup errors article to match and fix the exact error
The startup errors overview groups causes into: service account issues, inaccessible system databases, missing dependencies, incorrect configuration, and certificate/TLS problems. Once the specific error from Event Viewer and the error log is known, follow the matching article from that list to apply the precise fix.

In summary, the instance does not start automatically because SQL Server is encountering a startup error at boot (often dependency, network, or service-account related). The error log and Event Viewer entries at boot time will show the exact reason; then apply the corresponding fix (delayed start/dependencies, recovery options, account/domain configuration, or repair) so the service can start automatically without manual intervention.

References: