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

by

Troubleshooting Guide: SQL Server Error 5134 — FILESTREAM Path Not Supported

Why This Error Happens

This error occurs because FILESTREAM requires the underlying volume to be formatted with NTFS or ReFS, as these are the only file systems that support the extended attributes and transactional semantics FILESTREAM relies on. In most cases, the specified path points to a FAT32-formatted drive, a network share (UNC path) without proper configuration, or a mapped drive that Windows Server 2025 does not recognize as a local supported volume. Additionally, this error can surface if the target directory resides on a compressed or encrypted volume, which FILESTREAM explicitly disallows.

Step-by-Step Resolution Guide

Step 1: Verify the File System Format of the Target Volume

  • Open File Explorer, right-click the target drive (e.g., D:\), and select Properties.
  • Confirm the File System field reads NTFS or ReFS. If it shows FAT32 or exFAT, this is the root cause.
  • Alternatively, run this command in PowerShell or Command Prompt:
fsutil fsinfo volumeinfo D:

Step 2: Reformat or Relocate to a Supported Volume

  • If the drive is FAT32/exFAT, back up all data, then reformat using:
format D: /FS:NTFS /Q
  • If reformatting is not an option, choose a different NTFS/ReFS volume for the FILESTREAM data path.
  • Update the SQL Server FILESTREAM configuration path to the new supported volume (e.g., E:\SQLData\FilestreamContainer).

Step 3: Check for Compression, Encryption, or UNC Path Issues

  • Right-click the target folder, go to Properties > Advanced, and ensure “Compress contents” and “Encrypt contents” are both unchecked.
  • If using a network path, ensure it is a validated UNC path with proper FILESTREAM share permissions (\\ServerName\ShareName), not a mapped drive letter.
  • Confirm the SQL Server service account has Full Control NTFS permissions on the target folder.

Step 4: Restart SQL Server and Re-Attempt the FILESTREAM Operation

  • Restart the SQL Server service via SQL Server Configuration Manager to apply path changes.
  • Re-run the CREATE DATABASE or ALTER DATABASE statement that references the FILESTREAM filegroup path.

Alternative or Verification Steps

  • Verify success by running sys.database_filestream_options or checking SQL Server Error Log for confirmation that the FILESTREAM container was created without errors.
  • If the issue persists, use fsutil fsinfo drives to list all available volumes and cross-check that your chosen path isn’t accidentally pointing to a removable or virtual disk still using FAT32.