How to fix Error 434 on Windows 11

by

Troubleshooting Guide: Error 434 – Cloud File Dehydration Disallowed

Why This Error Happens

Error 434 occurs when the Windows Cloud Files API (CldFlt) attempts to dehydrate a file (convert it from a locally cached, fully downloaded state to an online-only placeholder) but the associated cloud sync provider explicitly blocks this action. This typically happens because the file is marked as “Always Keep on This Device,” is currently open/locked by another process, or the sync client (OneDrive, Dropbox, Google Drive, etc.) has a pinning policy or file-lock in place that prevents the OS from freeing local disk space. It can also occur if the sync provider’s placeholder database is corrupted or out of sync with the actual file state on disk.

Step-by-Step Resolution Guide

  1. Check File Pinning Status
  • Right-click the affected file/folder in File Explorer.
  • If using OneDrive, look for “Always keep on this device.” If checked, click it to uncheck it, allowing the file to become cloud-only when needed.
  1. Close Applications Locking the File
  • Ensure no application (Word, Excel, antivirus scanners, backup tools) has the file open in the background.
  • Use Task Manager (Ctrl+Shift+Esc) → check the “Details” tab for lingering processes and end them if safe to do so.
  1. Restart the Sync Client
  • Right-click the sync provider’s icon in the system tray (e.g., OneDrive) → Close OneDrive (or equivalent).
  • Reopen the application from the Start Menu to reinitialize its connection to the Cloud Files API.
  1. Reset the Sync Provider’s Cache/Placeholder Database
  • For OneDrive: Press Win + R, type onedrive.exe /reset, and press Enter. Wait a few minutes for OneDrive to restart and resync placeholders.
  • For other providers, check their documentation for a similar “reset sync state” or “rebuild index” command.
  1. Verify Storage Sense / Free Up Space Settings
  • Go to Settings → System → Storage → Storage Sense.
  • Ensure “Automatically clean up cloud content that is not opened locally” isn’t misconfigured or conflicting with the sync provider’s own dehydration rules. Adjust the day threshold or disable temporarily to test.

Alternative or Verification Steps

  • Verify the fix: Right-click the file → check its status icon (cloud vs. checkmark). Run dir in Command Prompt with the /a switch to confirm the file shows as a reparse point (offline placeholder) after a successful dehydration.
  • Alternative: If the error persists, unlink and relink the cloud sync account (Settings → Accounts → Unlink this PC), then let it resync from scratch—this rebuilds the placeholder metadata from zero.