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

by

Troubleshooting Guide: Error 5585 – FILESTREAM File I/O Access Could Not Be Enabled

Why This Error Happens

This error occurs because FILESTREAM support is disabled at the Windows operating system level, even though it may be enabled within the SQL Server Database Engine settings. SQL Server 2025 requires both the OS-level file I/O streaming access and the instance-level configuration to be synchronized before it can mount FILESTREAM-enabled filegroups. Typically, this happens after a fresh install of SQL Server 2025 on Windows Server 2025 or Windows 11 where the administrator enabled FILESTREAM via T-SQL (sp_configure) but skipped the corresponding step in SQL Server Configuration Manager.

Step-by-Step Resolution Guide

Step 1: Open SQL Server Configuration Manager

  • Press Win + R, type SQLServerManager17.msc (version number may vary for SQL Server 2025 builds), and hit Enter.
  • Alternatively, search for “SQL Server 2025 Configuration Manager” directly in the Windows 11 Start Menu.
  • Navigate to SQL Server Network Configuration > SQL Server Services in the left-hand pane.

Step 2: Enable FILESTREAM on the Instance Properties

  • Right-click on your specific instance (e.g., SQL Server (MSSQLSERVER)) and select Properties.
  • Go to the FILESTREAM tab.
  • Check the box for Enable FILESTREAM for Transact-SQL access.
  • If you require access from remote clients, also check Enable FILESTREAM for file I/O streaming access and enter a valid Windows Share Name (e.g., MSSQLSERVER).
  • Click Apply and then OK to save the configuration.

Step 3: Restart the SQL Server Service

  • In the Configuration Manager, right-click the instance again and select Restart.
  • This is mandatory, as the OS-level FILESTREAM driver changes do not take effect on a running instance without a full service restart.

Step 4: Verify and Sync T-SQL Configuration

  • Open SQL Server Management Studio (SSMS) and connect to the instance.
  • Run the following query to ensure the instance-level setting matches the OS-level setting (set to 2 or 3 depending on remote access needs):
EXEC sp_configure filestream_access_level, 2;
RECONFIGURE;
  • Restart the SQL Server service one final time to ensure the T-SQL change and the OS-level change are fully synchronized.

Alternative or Verification Steps

  • Verification: Run SELECT SERVERPROPERTY('FilestreamConfiguredLevel'); in SSMS. If the result returns 2 or higher, the OS and SQL instance settings are successfully synced and the error should be resolved.
  • Alternative: If the GUI checkbox is grayed out or fails to save, manually enable the Windows Server 2025 role via PowerShell by running Enable-WindowsOptionalFeature -Online -FeatureName FileStream (if applicable to your build) or check Local Group Policy to ensure the “Local Security Authority” isn’t blocking the required FltMgr.sys driver from loading.