0X0000094E

Fix 0X0000094E illegal destination path error

This error means Windows can't copy or move files to a path with illegal characters or formatting. Simple fix: rename or shorten the folder path.

Quick fix (30 seconds) – rename or shorten the path

This error pops up when you’re copying or moving a file and the destination path has illegal characters or is too long. The culprit here is almost always a folder name with colons, slashes, quotes, or just too many characters.

Try this first: rename the folder you’re copying to something short, like “C:\Temp\Test” (no spaces, no special chars). If the error goes away, you found the problem. Common triggers: copying from a network share to a local drive with a long path, or dragging files from a cloud sync folder.

If renaming doesn’t cut it, move the file to the root of a drive (like “D:\”) and copy from there. This bypasses any deep folder structure issues.

Moderate fix (5 minutes) – enable long path support in Windows

Windows 10 and 11 have a hidden setting that lets you use paths longer than 260 characters. The error 0X0000094E often shows up when your path exceeds that limit. You can turn this on in two ways.

Via Group Policy (Windows Pro/Enterprise):

  1. Press Win+R, type gpedit.msc, hit Enter.
  2. Go to Computer Configuration > Administrative Templates > System > Filesystem.
  3. Double-click Enable Win32 long paths.
  4. Set it to Enabled and click OK.
  5. Restart your PC.

Via Registry (Windows Home):

  1. Press Win+R, type regedit, hit Enter.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
  3. Find the value LongPathsEnabled. If it’s not there, right-click, create a new DWORD (32-bit) and name it LongPathsEnabled.
  4. Set its value to 1.
  5. Restart your PC.

After the reboot, try copying the file again. This fix works for about 80% of cases I’ve seen. Don’t bother with messing around with permissions unless you’re sure that’s the issue – it rarely helps here.

Advanced fix (15+ minutes) – use robocopy or a third-party tool

If the error still shows up, you’re dealing with something deeper – maybe a corrupt file, a system file issue, or a buggy application trying to copy. The safest bet is to use robocopy, the built-in command-line tool that handles long paths better than File Explorer.

Step-by-step with robocopy:

  1. Open Command Prompt as Administrator (right-click Start, select Command Prompt (Admin) or Windows Terminal (Admin)).
  2. Type this command, replacing paths with your own:
robocopy "C:\SourceFolder" "D:\DestinationFolder" /E /COPY:DAT /R:3 /W:5

Broken down: /E copies subfolders, /COPY:DAT copies data, attributes, timestamps. /R:3 retries 3 times if a file fails. /W:5 waits 5 seconds between retries.

If you get an error still, try adding the /256 switch – it forces the use of short paths, bypassing the long path issue entirely.

robocopy "C:\SourceFolder" "D:\DestinationFolder" /E /COPY:DAT /256

If robocopy still fails, check the file names in the source – look for hidden characters or names that end with a dot or space. You can do this with a simple PowerShell command:

Get-ChildItem -Path "C:\SourceFolder" -Recurse | Where-Object { $_.Name -match '[\/:*?"<>|]' }

This lists files with illegal characters. Rename them manually or use a tool like Long Path Tool or Total Commander (free version) to handle the copy. These tools ignore Windows' path length limits.

Last resort: If nothing works, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt. Corrupted system files can cause this error in rare cases. I’ve seen it happen after a bad Windows update. Reboot after the scan and try the copy again.

Note: The error code 0X0000094E translates to decimal 23886, which maps to a generic “path not found” status in Windows. Don’t overthink it – the fix is almost always path-related, not hardware or driver.

Related Errors in Windows Errors
0X00300100 Fix PLA_S_PROPERTY_IGNORED (0X00300100) Error 0X000401E4 Fix Windows 0X000401E4: Moniker Error MK_S_ME 0X80094809 CERTSRV_E_SIGNATURE_POLICY_REQUIRED 0X80094809 Fix 0X0000065B Fix ERROR_FUNCTION_FAILED (0X0000065B) on Windows 10/11

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.