SQL Server 2025 Express - service starts with delay of some hours after restart of computer

Hi,

This issue is typically caused by resource contention during a reboot, or a change in default behavior regarding how SQL Server 2025 manages its background telemetry, dependency checks, or licensing validation upon startup. Because Express edition is often installed on client machines or lower-spec servers, it is highly susceptible to getting stuck in the Windows Service Control Manager (SCM) queue.

Here are the most likely causes and how to fix it:

1. The Service Startup Type is set to Automatic (Delayed Start)

SQL Server installations sometimes default to Automatic (Delayed Start) instead of Automatic. This explicitly instructs Windows to wait until all other critical system services have loaded before initiating the SQL Server service. Depending on system load, this delay can be massive.

 The Fix: 1. Open services.msc.

   2. Locate SQL Server (SQLEXPRESS).

   3. Right-click and choose Properties.

   4. Change the Startup type from Automatic (Delayed Start) to Automatic.

2. Service Timeout During Boot (SCM Timeout)

During a system restart, multiple services compete for CPU and Disk I/O. By default, Windows allows a service only 30 seconds to start before it forcefully gives up and logs an error (or leaves the service in a stalled state until a system trigger revives it hours later).

 The Fix: Increase the global Windows service startup timeout via the Registry:

   1. Open regedit and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

   2. Look for a DWORD value named ServicesPipeTimeout. (If it doesn't exist, right-click -> New -> DWORD (32-bit) Value* and name it exactly that).

   3. Set the Value to 60000 (Decimal), which increases the timeout to 60 seconds (or 120000 for 2 minutes).

   4. Reboot the machine.

3. Network/Domain Controller Dependency Checks

SQL Server might be attempting to validate network protocols, TLS certificates, or domain accounts before the network stack or Domain Controller connectivity is fully established during boot. It stalls until a network timeout occurs (which can take a long time).

 The Fix: Force SQL Server to depend on the network infrastructure being ready first.

   1. Open the command prompt as Administrator.

   2. Run the following command:

cmd

     sc config MSSQL$SQLEXPRESS depend= LanmanWorkstation/LanmanServer

     (Replace MSSQL$SQLEXPRESS with your actual instance service name if different).

 4. Setup a Recovery Trigger as a Fail-safe

Since your batch script works perfectly, you can configure Windows to automatically execute that logic if the service fails to respond within the expected initial window:

 1. In services.msc, open the SQL Server service properties.

 2. Go to the Recovery tab.

 3. Set First failure Second failure and Subsequent failures to Restart the Service.

 4. Set Reset fail count after to 1 days, and Restar

t service after to 1 minutes.