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

by

Troubleshooting Guide: SQL Server 2025 Error 5582 (FILESTREAM Reboot Pending)

Why This Error Happens

Error 5582 occurs when the Windows kernel-mode driver for FILESTREAM (WOF or the FILESTREAM filter driver, sqlflt.sys) is modified or enabled at the OS level but hasn’t been fully loaded into the running kernel session. This typically happens because SQL Server Configuration Manager changes the registry and driver bindings immediately, but Windows Server 2025 requires a full restart to re-initialize the storage filter driver stack. Until the reboot occurs, SQL Server detects a mismatch between the requested FILESTREAM state (enabled) and the actual loaded driver state (not loaded or previous configuration), triggering this blocking error.

Step-by-Step Resolution Guide

Step 1: Verify the Current Driver State

  • Open PowerShell as Administrator.
  • Run fltmc filters to check if sqlflt appears in the list of loaded filter drivers.
  • If it is missing despite being enabled in SQL Server Configuration Manager, this confirms the driver is staged but not active.

Step 2: Force a Full System Restart (Not a Service Restart)

  • Do not simply restart the “SQL Server (MSSQLSERVER)” service, as this will not reload the kernel driver.
  • Execute a full OS restart via shutdown /r /t 0 in an elevated Command Prompt.
  • Ensure no pending Windows Updates are queued, as this can sometimes interfere with the driver reload sequence on Windows Server 2025.

Step 3: Re-validate FILESTREAM Settings Post-Reboot

  • After the server restarts, open SQL Server Configuration Manager.
  • Navigate to SQL Server Services > Right-click your instance > Properties > FILESTREAM tab.
  • Confirm the checkboxes for “Enable FILESTREAM for Transact-SQL access” and “Enable FILESTREAM for file I/O streaming access” are checked and grayed out as saved (not requiring re-application).

Step 4: Update the SQL Server Instance Configuration

  • Open SQL Server Management Studio (SSMS) and connect via sysadmin credentials.
  • Run the following T-SQL to ensure the instance-level configuration matches the OS-level driver state:
EXEC sp_configure filestream_access_level, 2;
RECONFIGURE;
  • Restart the SQL Server service (standard service restart) to apply this specific instance-level change.

Alternative or Verification Steps

  • Verification: Run SELECT SERVERPROPERTY('FilestreamConfiguredLevel') in SSMS; a return value of 2 confirms the setting is fully active and matches the running kernel driver state.
  • Alternative: If the reboot loop persists, manually unload and reload the driver via an elevated prompt using sc.exe query sqlflt to check the STATE, followed by sc.exe start sqlflt if the state shows STOPPED rather than waiting for a Group Policy-driven restart.