Fix ERROR_CHECKOUT_REQUIRED (0x000000DD) fast
This error means the file is locked by a version control system, usually SharePoint or VSS. The fix is to check it out first or disable read-only mode.
Yeah, that error is annoying as hell. You're trying to save your work and Windows pops up with ERROR_CHECKOUT_REQUIRED (0x000000DD). It means the file is under version control and you haven't checked it out yet. Let's fix it.
The Quick Fix
Open Windows Explorer, right-click the file, and select Check Out. If you don't see that option, the file's probably in a SharePoint library or a Visual SourceSafe (VSS) folder. Here's what to do:
- SharePoint: Open the library in your browser. Check the box next to the file. Click Check Out in the ribbon. Then edit and save locally.
- Visual SourceSafe: Open VSS, find the file, right-click, and choose Check Out. If you don't have VSS installed, you're seeing this because the file's attributes are set to read-only.
- Other systems (like TFS/SVN/Git): Use the tool's UI or command line. For Git,
git checkout -- <file>orgit reset HEAD <file>if it's staged.
If none of those apply, the file might just be read-only. Right-click the file, go to Properties, and uncheck Read-only. Apply, OK. Try saving again.
Why This Happens
The culprit here is almost always a version control system that locks files to prevent two people from overwriting each other's work. When you try to save without checking it out, Windows throws 0x000000DD. It's a safety feature, not a bug — but it feels like a bug when you're in a hurry.
Behind the scenes, the file's attributes are set to read-only until you check it out. The OS sees the read-only flag and refuses to write. You don't need to mess with ACLs or permissions — it's just the file attribute.
Less Common Variations
Scenario 1: File is in a SharePoint sync folder
If you're using OneDrive or the SharePoint sync client, the file might show up in File Explorer with a little lock icon. Right-click > Check Out works here too. But if the sync client is stuck, you might need to stop and restart it. Run OneDrive.exe /reset from Command Prompt (as admin). Wait 2 minutes, then retry.
Scenario 2: The error appears on a network share
Some legacy apps (cough, old Visual Basic tools) treat files on network shares like version control. The real fix: copy the file to your local desktop, edit there, then copy it back. Not elegant, but it works.
Scenario 3: The file's on a USB drive or external disk
Rare, but I've seen it. The drive's file system might be corrupted. Run chkdsk /f X: (replace X with drive letter). If that doesn't help, the file's attributes got mangled. Use attrib -r <filename> in Command Prompt to remove read-only.
Prevention
Don't just disable read-only and move on — that breaks the version control system. Instead:
- Always check out files before editing. Make it a habit. SharePoint and VSS have check-out buttons in their UIs.
- Use the client's sync feature. If you're on SharePoint, use the sync client so files check out automatically when you open them. Saves you the headache.
- For VSS users: Upgrade to a modern VCS if possible. Seriously. VSS is ancient and buggy. Git with a GUI like SourceTree is way more reliable.
If you're the admin setting permissions, make sure users have write access to the library or folder. Blocking write access will trigger this error even with checkout. Check NTFS permissions and SharePoint library permissions — they need Contribute (SharePoint) or Modify (NTFS).
One last thing: if you're using an old app that doesn't support SharePoint checkout, you're stuck with the manual copy-to-desktop workaround until you either update the app or move to a flat file share. I've seen this with custom Access databases and old Excel macros. Tell the dev team to update their code.
Was this solution helpful?