What's This Error?
You're trying to open a file or program, and bam — error 0x000000AE pops up. It says the file system won't allow atomic changes to the lock type. Translation: your drive (internal or external) can't handle certain low-level lock operations. I've seen this a lot on older USB drives or drives formatted with FAT32 instead of NTFS. It also happens when a drive has minor corruption or outdated drivers.
Let's fix it. Start with the easiest thing — takes 30 seconds. If that doesn't work, move to the next step.
Fix 1: Check Your Drive's File System (30 seconds)
This error often shows up on drives formatted as FAT32 or exFAT. Those file systems don't support atomic locks — it's a feature only NTFS and ReFS have. So first, check what your drive is using.
- Open File Explorer (Windows key + E).
- Right-click your problematic drive (say, D: or E:).
- Click Properties.
- Look at the File system line. If it says FAT32 or exFAT, that's the problem.
The fix: Reformat the drive to NTFS. But wait — that erases everything. So back up your data first. In File Explorer, right-click the drive, choose Format, set File system to NTFS, check Quick Format, and click Start. Done.
If the drive already shows NTFS, move to Fix 2.
Fix 2: Update Disk and Controller Drivers (5 minutes)
Old or corrupt drivers can cause this error too. I've seen it with USB 3.0 controllers and some SATA SSDs. Here's what to do:
- Press Windows key + X and select Device Manager.
- Expand Disk drives. Find your drive (look for model number, like Seagate Barracuda or Samsung SSD).
- Right-click it, choose Update driver > Search automatically for drivers.
- Do the same under Storage controllers — update your SATA or USB controller drivers.
If Windows finds nothing, go to your PC or motherboard manufacturer's website. Look for chipset or storage drivers. For example, with an Intel system, download the latest Intel Rapid Storage Technology driver. For AMD, get the latest chipset package. Install, reboot, and test.
Still broken? On to Fix 3.
Fix 3: Run chkdsk to Repair File System (15+ minutes)
This is the nuclear option for NTFS drives — scans and fixes corruption. But I've had it work when nothing else did.
Step 1: Open Command Prompt as admin. Hit Start, type cmd, right-click Command Prompt, pick Run as administrator.
Step 2: Run this command, replacing X with your drive letter:
chkdsk X: /f /rThe /f flag fixes errors, /r locates bad sectors. For system drives (like C:), it'll ask to schedule at next reboot — type Y and restart.
Step 3: Let it run. Could take an hour on a large drive. Go make coffee. When it's done, check if the error's gone.
If chkdsk reports unfixable errors, your drive might be failing physically. Back up your data immediately and replace the drive.
When All Else Fails
I've seen this error on one weird scenario: a USB drive with a bad cable. Try a different cable or port. Also, if you're using a USB hub, plug directly into the computer. Sometimes power delivery gets flaky.
Still stuck? Post your drive model, OS version (Windows 10, 11, Server 2022), and whether it's internal or external. I'll help narrow it down.