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

by

Troubleshooting Guide: SQL Server Error 5580 – FILESTREAM InstanceGuid is Null

Why This Error Happens

This error occurs when the FILESTREAM registry keys associated with the SQL Server instance become corrupted, deleted, or improperly migrated, causing the InstanceGuid value to be missing or unreadable. It commonly surfaces after an in-place upgrade to SQL Server 2025, a failed patch installation, or manual edits to the registry that disrupted the MSSQLServer\Filestream key hierarchy. Without a valid InstanceGuid, the SQL Server service cannot initialize the FILESTREAM filter driver, preventing the database engine from starting or accessing FILESTREAM-enabled data.

Step-by-Step Resolution Guide

Step 1: Verify the Current FILESTREAM Registry State

  • Open the Registry Editor (regedit.exe) with administrative privileges.
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL17.<InstanceName>\Filestream.
  • Check if the InstanceGuid value exists; if missing or blank, this confirms the corruption.
  • Export the current key as a backup before making any changes (File > Export).

Step 2: Rebuild the FILESTREAM Instance GUID

  • Stop the SQL Server service via services.msc or by running net stop MSSQLSERVER in an elevated Command Prompt.
  • Use SQL Server Configuration Manager to disable and then re-enable FILESTREAM support under the instance’s Properties > FILESTREAM tab.
  • This action forces SQL Server to regenerate a new InstanceGuid value in the registry upon the next service start.
  • Restart the service using net start MSSQLSERVER.

Step 3: Repair via Setup if Registry Rebuild Fails

  • If the GUID still fails to regenerate, launch SQL Server 2025 Setup from the installation media.
  • Select Maintenance > Repair and choose the affected instance.
  • Allow the repair process to complete, as this will restore the Filestream registry subkey structure to its default state.
  • Reboot the Windows Server 2025 / Windows 11 machine to ensure the filter driver (rsfx.sys) reloads correctly.

Step 4: Validate Permissions on the Registry Hive

  • Right-click the MSSQL17.<InstanceName> key and select Permissions.
  • Ensure the NT SERVICE\MSSQLSERVER (or named instance equivalent) account has Full Control.
  • Apply the changes and restart the SQL Server service to confirm the account can write the new GUID value.

Alternative or Verification Steps

  • Run SELECT SERVERPROPERTY('FilestreamConfiguredLevel'); in SQL Server Management Studio; a return value of 2 or 3 confirms FILESTREAM is active and the instance GUID is valid.
  • If the error persists after a repair, uninstall and reinstall the Database Engine component entirely, as a deeper MSI package corruption may be preventing the registry write operation.