How to fix Error 206 on Windows 11

by

Windows 11 Error 206: “The Filename or Extension Is Too Long”

Why This Error Happens

Error 206 occurs when a file path exceeds the traditional Windows MAX_PATH limitation of 260 characters, including the drive letter, folder names, filename, and extension. This is a legacy restriction baked into the Win32 API that many applications—especially older ones or command-line tools—still enforce even though modern NTFS supports paths up to 32,767 characters. The issue is commonly triggered by deeply nested folder structures, synced cloud storage folders (OneDrive, Dropbox), or files extracted from compressed archives with long internal paths.

Step-by-Step Resolution Guide

  1. Enable Long Path Support via Group Policy (Recommended)
  • Press Win + R, type gpedit.msc, and press Enter.
  • Navigate to Computer Configuration > Administrative Templates > System > Filesystem.
  • Double-click Enable Win32 long paths, set it to Enabled, click Apply, then OK.
  • Restart your PC for the change to take effect.
  1. Enable Long Path Support via Registry (For Home Edition users without gpedit)
  • Press Win + R, type regedit, and press Enter.
  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
  • Find the LongPathsEnabled DWORD (create it if missing) and set its value to 1.
  • Restart the computer.
  1. Shorten the File Path Manually
  • Move the file closer to the root of the drive (e.g., C:\Data\file.txt instead of a deeply nested folder path).
  • Rename parent folders to shorter names, or rename the file itself to reduce character count.
  1. Use a Command-Line Workaround (Robocopy)
  • Open Command Prompt as Administrator.
  • Run: robocopy "C:\VeryLongSourcePath" "C:\Short" /E /MOVE
  • This bypasses some MAX_PATH restrictions during file transfers by using Windows API extensions.
  1. Map a Network Drive or Use Subst for Deeply Nested Folders
  • Open Command Prompt and run: subst Z: "C:\Users\YourName\Very\Long\Nested\Folder\Path"
  • Access the files via the new Z: drive, which shortens the effective path length.

Alternative or Verification Steps

  • Verify the fix: Try copying, renaming, or opening the previously problematic file again—if Error 206 no longer appears, the long path support is active.
  • Alternative tool: If the built-in fixes don’t resolve it (especially in third-party apps), use a dedicated long-path utility like Long Path Tool or 7-Zip (which has better long-path handling than Windows Explorer) to move or delete the affected files.