How to fix Error 600 on Windows 11

by

Why This Error Happens

Error 600 is an internal status code generated by the ReFS Object File System (OFS) driver during block allocation operations. It occurs when the filesystem determines that the current onode (object metadata node) no longer has sufficient contiguous space and must either relocate the onode or convert the extent stream into a “large stream” format to accommodate further growth. This typically surfaces on heavily fragmented ReFS volumes, volumes nearing capacity, or after abrupt system shutdowns that leave metadata structures in a transitional state.

Step-by-Step Resolution Guide

  1. Check disk health and free space – Open PowerShell as Administrator and run:
   Get-Volume
   Repair-Volume -DriveLetter X -Scan

Ensure at least 10–15% free space remains on the affected ReFS volume, as low space accelerates onode relocation events.

  1. Run a full ReFS integrity scan and repair – Execute:
   Repair-Volume -DriveLetter X -SpotFix

This corrects metadata inconsistencies (including malformed extent streams) without requiring a full offline check.

  1. Update storage drivers and firmware – Go to Settings > Windows Update > Advanced Options > Optional Updates and install any pending storage controller or SSD/HDD firmware updates. Outdated drivers can mishandle allocation callbacks from the OFS layer, triggering repeated Error 600 retries.

  2. Review Event Viewer logs for correlated ReFS events – Open Event Viewer > Applications and Services Logs > Microsoft > Windows > ReFS > Operational and look for adjacent Event IDs (e.g., 5, 50, 300 series) indicating recurring onode moves. If these repeat excessively, schedule an offline chkdsk-equivalent repair:

   Repair-Volume -DriveLetter X -OfflineScanAndFix
  1. Defragment or migrate data if fragmentation is severe – For volumes showing persistent large-stream conversions, back up data and reformat the volume with a larger cluster size (via Format-Volume -FileSystem ReFS -AllocationUnitSize 65536) to reduce future onode relocation frequency.

Alternative or Verification Steps

  • After remediation, monitor the ReFS Operational log for 24–48 hours to confirm Error 600 entries no longer appear during normal write operations.
  • If the error persists despite repairs, run fsutil repair query X: to confirm self-healing status, or consider migrating critical data to a fresh ReFS or NTFS volume as a fallback.