0x1A9B Miniversion Modify Access Fix

Yeah, This Error Stinks

You're trying to open a previous version of a file — a miniversion (shadow copy) — and Windows slaps you with error 0x00001A9B. It says you can't open it with modify intent. Frustrating, I know. Let's cut through the noise.

The Quick Fix: Open Read-Only

Don't bother fighting the system. The simplest way around this? Open the miniversion as read-only. Here's how:

1. Right-click the file or folder you're trying to access.
2. Select Properties > Previous Versions tab.
3. Highlight the version you want, but instead of double-clicking, click Open (not Restore).
4. When it opens, go to File > Save As and save it somewhere else. Then edit that copy.

This works 90% of the time. You get the data. You move on.

Why This Error Happens

The culprit here is almost always a sharing violation or a backup tool holding a lock. Miniversions are point-in-time snapshots created by Volume Shadow Copy Service (VSS). Windows doesn't let you open them with write intent because:

• Another process (like backup software) already has the original file open with exclusive write access.
• VSS itself protects the snapshot from being modified — it's meant to be a static image.
• File permissions — you might not have write rights on the original volume or the snapshot location.

Think of it this way: the snapshot is a frozen copy. You can view it, but you're not supposed to change it directly. That's by design.

Less Common Variations & Deeper Fixes

Sometimes read-only doesn't cut it. Here's what else I've seen work:

1. Killing the Locking Process

Run handle.exe (from Sysinternals) to find what's holding the original file:

handle.exe -a -u "C:\path\to\your\file.ext"

Look for processes like backup agents, antivirus real-time scanning, or even Windows Search Indexer. Kill or pause them temporarily, then try again.

2. Disable Backup Software Temporarily

If you're running Veeam, Acronis, or built-in Windows Backup, pause it. Those tools often keep VSS snapshots open with exclusive locks. Stop the backup service from Services.msc, retry, then restart it.

3. Check Volume Shadow Copy Settings

Open an admin command prompt and run:

vssadmin list shadows

If you see multiple shadow copies from different tools, you might have a conflict. Delete old ones with:

vssadmin delete shadows /for=C: /oldest

This clears stale snapshots that can cause lock issues.

4. Use a Different Method to Recover the File

If you're stuck, skip Previous Versions entirely. Use robocopy to copy the miniversion to a new location:

robocopy "C:\@GMT-2025-03-15.12.00.00\path\to\folder" "C:\recovered" file.ext

Replace the @GMT-... path with your actual snapshot path (find it via vssadmin list shadows). This bypasses the GUI lock.

Prevention for Next Time

You don't want this error again. Here's the short list:

• Keep backup software updated — old versions of Veeam or Acronis have known lock bugs.
• Don't run multiple backup tools simultaneously on the same volume. They fight over VSS.
• Set VSS storage properly — if you run out of space, snapshots get corrupt and throw weird errors. Use vssadmin resize shadowstorage.
• Monitor your handle count — high file locking activity from apps like SQL Server or Exchange can cause this. Restart the service if needed.

One last thing: if you're on Windows Server 2016/2019 and see this error, check your VSS writer status with vssadmin list writers. A failed writer (like Exchange or SQL) will lock up miniversions. Fix the writer, fix the error.

That's it. You've got the fix, the why, and the edge cases. Save your read-only copy and get back to work.