How to fix Error 342 on Windows 11

by

Windows Error 342: “This object is not externally backed by any provider”

Why This Error Happens

This error typically occurs when the Windows Projected File System (ProjFS) attempts to access a file or directory that is expected to be “virtualized” or backed by an external storage provider (such as OneDrive, Git Virtual File System, or Dev Drive) but finds no active provider attached to it. This commonly happens after an abrupt system shutdown, a corrupted virtualization instance, or when a sync client (like OneDrive) crashes or is improperly uninstalled while placeholder files remain on disk. It can also occur on Dev Drive volumes formatted with ReFS when the associated container or storage sense provider becomes disconnected from the volume.

Step-by-Step Resolution Guide

  1. Restart the associated sync/virtualization service. If the error relates to OneDrive placeholders, close OneDrive completely via the system tray icon (Right-click > Close OneDrive), then reopen it from the Start Menu to reinitialize the provider connection.
  2. Check ProjFS feature status. Open Windows Features (optionalfeatures.exe), scroll to Windows Projected File System, and ensure it is checked/enabled. If it’s already enabled, uncheck it, restart your PC, re-enable it, and restart again to reset the driver binding.
  3. Run System File Checker and DISM. Open an elevated Command Prompt or PowerShell (Win + X > Terminal (Admin)) and run:
   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that manage virtualization filters.

  1. Inspect the specific file/folder for orphaned placeholders. Navigate to the reported file path in File Explorer, right-click the parent folder, and check Properties > Advanced to see if “Free up space” attributes are stuck. If found, copy the file to a new location (forcing a full local copy) and delete the original orphaned placeholder.
  2. For Dev Drive/ReFS-specific errors: Open Disk Management (diskmgmt.msc), verify the Dev Drive volume is mounted correctly, then run fsutil devdrv commands in an elevated terminal to confirm the volume’s trust and filter status is active.

Alternative or Verification Steps

  • Verify the fix: Re-attempt to access the specific file or folder that triggered Error 342. If using OneDrive, check that the cloud icon overlay (checkmark or cloud symbol) has returned to the file, indicating a provider is now attached.
  • Alternative fix: If the error persists on a specific folder, unlink your account (e.g., “Unlink this PC” in OneDrive settings) and relink it. This forces Windows to rebuild the placeholder database and reattach the external provider from scratch.