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

by

Troubleshooting Guide: SQL Server Error 5578 — FILESTREAM Configuration Failure

Why This Error Happens

Error 5578 occurs when SQL Server 2025 attempts to enable or modify FILESTREAM settings but cannot complete the underlying Windows-level configuration changes. This is most commonly caused by the SQL Server service account lacking local administrative rights needed to modify system registry keys, a conflict with the FILESTREAM share name already existing on the host, or the SQL Server Configuration Manager service failing to communicate with the Windows Server 2025 kernel driver (FltMgr) that governs FILESTREAM’s filter driver. In some cases, Group Policy restrictions on Windows 11 workstations block the creation of the required file share entirely.

Step-by-Step Resolution Guide

Step 1: Verify FILESTREAM is Enabled at the Windows Level

  • Open SQL Server Configuration Manager and navigate to SQL Server Services.
  • Right-click your SQL Server instance (e.g., MSSQLSERVER) and select Properties.
  • Go to the FILESTREAM tab and ensure “Enable FILESTREAM for Transact-SQL access” is checked.
  • If enabling the share, confirm the Windows share name field does not conflict with an existing SMB share (check via net share in Command Prompt).

Step 2: Check Service Account Permissions

  • Confirm the SQL Server service account has local administrator rights on Windows Server 2025, as FILESTREAM requires registry and share-level write access.
  • Run services.msc, locate the SQL Server service, and verify the Log On As account.
  • Grant necessary permissions via:
  net localgroup Administrators "DOMAIN\SQLServiceAccount" /add
  • Restart the SQL Server service after applying changes.

Step 3: Enable FILESTREAM via T-SQL and sp_configure

  • Open a new query window in SSMS and run:
  EXEC sp_configure filestream_access_level, 2;
  RECONFIGURE;
  • Restart the SQL Server service for the change to take effect.
  • If the error persists, check the SQL Server error log (ERRORLOG file, typically in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\) for a more granular Windows API error code tied to Event ID 5578.

Step 4: Inspect Windows Registry and Driver State

  • Open regedit and navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FltMgr
  • Confirm the FltMgr service Start value is set to 0 (Boot) or 1 (System); if set to 4 (Disabled), change it to 1 and reboot.
  • Verify the FILESTREAM filter driver is loaded using:
  fltmc filters
  • Look for MSSQLFSF in the output list; if absent, reinstall the FILESTREAM feature via the SQL Server 2025 setup media (Repair option).

Alternative or Verification Steps

  • Confirm the fix by running EXEC sp_configure 'filestream_access_level'; — the run_value should return 2, and you should be able to create a test table using FILESTREAM column storage without error.
  • If the issue persists after all steps, uninstall and reinstall the Database Engine FILESTREAM feature via Add or Remove Programs > Microsoft SQL Server 2025 > Modify, ensuring no pending Windows Updates are queued that might lock the filter driver during installation.