How to fix Error 347 on Windows 11

by

Why This Error Happens

Error 347 (ERROR_BLOCK_TOO_MANY_REFERENCES) occurs on ReFS (Resilient File System) volumes that use block cloning technology for fast copy operations (such as Hyper-V checkpoints, Storage Spaces, or deduplication). Each cloned data block can only be referenced by a finite number of files before ReFS’ internal reference counter hits its hard limit, after which no new clone references can point to that block. This typically happens after repeated fast-copy/clone operations (e.g., frequent VM checkpoint merges or Copy-Item with block cloning) are performed on the same underlying data without ever triggering a full physical copy.

Step-by-Step Resolution Guide

  1. Identify the affected volume by checking Event Viewer (Windows Logs > System, filter for Event ID 347) to confirm it’s tied to ReFS block cloning and note the file/drive path involved.
  2. Force a full physical copy of the file instead of a cloned copy. Open PowerShell as Administrator and run:
   Copy-Item -Path "C:\Path\To\File" -Destination "D:\NewLocation\File" -Force

This bypasses the block-cloning API and creates fresh, non-shared blocks.

  1. Run ReFS integrity check and repair using CHKDSK with the ReFS-specific verification flag:
   chkdsk D: /scan
   chkdsk D: /forceofflinefix

Replace D: with your affected ReFS volume letter.

  1. Rewrite the file to reset its block reference count by copying it off the volume to a different (non-ReFS) drive, deleting the original, then copying it back:
   Copy-Item -Path "D:\File.vhdx" -Destination "E:\Temp\File.vhdx"
   Remove-Item -Path "D:\File.vhdx"
   Copy-Item -Path "E:\Temp\File.vhdx" -Destination "D:\File.vhdx"
  1. If using Hyper-V, merge or consolidate any pending checkpoints/snapshots on the affected VM, since chained AVHDX files are the most common cause of hitting the reference limit.

Alternative or Verification Steps

  • Verify the fix by repeating the operation that previously failed (e.g., checkpoint creation or file copy) — it should complete without triggering Event ID 347.
  • If the error persists, back up the data and reformat the volume as NTFS instead of ReFS, since NTFS does not use block cloning and is not subject to this reference count ceiling.