How to fix Error 3404 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 3404 – “Failed to Check for New Installation or Renamed Server at Startup”

Why This Error Happens

This error occurs when SQL Server 2025 attempts to validate the server’s identity against the registry and machine name during startup, but the logic fails due to corrupted registry keys or mismatched server name metadata. It is commonly triggered after a server rename, a failed cluster failover, or domain/workgroup changes that leave stale entries in the SQL Server Configuration Manager or Windows registry. Insufficient permissions on the registry hive or a corrupted sys.servers system catalog can also prevent SQL Server from completing this internal validation check.

Step-by-Step Resolution Guide

Step 1: Verify Server Name Consistency

  • Open a Command Prompt as Administrator and run hostname to get the current Windows machine name.
  • Connect to SQL Server via SQLCMD or SSMS and run SELECT @@SERVERNAME; and SELECT SERVERPROPERTY('ServerName');.
  • If the values do not match, this mismatch is the root cause of the Error 3404 logic failure.

Step 2: Drop and Re-Add the Server Name

  • In SSMS, execute sp_dropserver 'OldServerName'; to remove the stale registration.
  • Re-register the correct name using sp_addserver 'NewServerName', local;.
  • Restart the SQL Server service via services.msc or run net stop MSSQLSERVER && net start MSSQLSERVER.

Step 3: Check Registry Permissions and Integrity

  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL17.MSSQLSERVER\Setup in Registry Editor (regedit).
  • Confirm the SQLServerName and ComputerNamePhysicalNetBIOS values match the actual host name.
  • Ensure the NT AUTHORITY\SYSTEM and SQLServerMSSQLUser$<InstanceName> accounts have Full Control permissions on this registry key.

Step 4: Repair the SQL Server Installation

  • Launch the SQL Server 2025 Installation Center from the original setup media or ISO.
  • Select Maintenance > Repair and choose the affected instance.
  • Allow the repair wizard to complete, then reboot the Windows Server 2025 / Windows 11 machine before attempting to start the SQL Server service again.

Alternative or Verification Steps

  • After applying fixes, restart the SQL Server service and check the SQL Server Error Log (ERRORLOG file in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\) to confirm Error 3404 no longer appears during startup.
  • If the issue persists, use sp_helpserver to inspect server metadata directly, or as a last resort, uninstall and perform a clean reinstall of the SQL Server instance to rebuild the corrupted setup logic.