STATUS_CANNOT_MAKE (0XC00002EA) - Fix When File Creation Fails
Windows throws this when it can't create a file or folder. Usually a permissions or path issue. Quick fix: check permissions and clear temp files.
Yeah, I know that feeling. You're trying to save a file or install something, and Windows throws up that cryptic STATUS_CANNOT_MAKE (0XC00002EA) error. It's annoying. Let's get it fixed.
The Quick Fix: Check Permissions and Clear Temp
Most of the time, this error comes down to one of two things: you don't have write permission to the folder, or Windows' temp folder is full or corrupted. I've seen it happen in Windows 10 and 11, especially when you're saving to a system-protected location like C:\Program Files or C:\Windows.
Here's what to do first:
- Move the file to a different folder. Try saving to your Desktop or Documents folder. If it works, the original location is the problem.
- Clear your temp files. Press
Win + R, type%temp%, and hit Enter. Delete everything in that folder. Some files might not delete—skip them. Then restart your PC. - Check disk space. If the drive is full, Windows can't create files. Free up some space.
If that doesn't work, move on to the next step.
The Real Fix: Adjust Permissions
Permissions are the usual suspect. For example, last month a client had this error when trying to save a PDF to a shared drive. The folder was set to read-only for everyone. Here's how to fix it:
- Right-click the folder where you're saving the file, choose Properties.
- Go to the Security tab.
- Click Edit to change permissions.
- Select your user name, and make sure Write is checked under Allow.
- Click OK and try again.
Sometimes the issue is with a specific program that runs as a service—like a backup tool. In that case, you need to give the SYSTEM account write access too. I've had to do that for a few database apps.
Why This Happens
The error code 0XC00002EA translates to STATUS_CANNOT_MAKE. It's Windows' way of saying: "I tried to create that file, but something stopped me." The operating system checks permissions before it writes anything. If the folder is read-only, or if the temp folder is full, or if the drive is out of space, it'll throw this error.
Another common trigger: antivirus software. I've seen Norton and McAfee block file creation on certain folders. If you're running one, temporarily disable it and see if the error goes away. If so, add an exception for that folder in your antivirus settings.
Less Common Variations
Sometimes the error isn't about permissions or space. Here are a few other scenarios I've run into:
Corrupt System Files
If Windows itself has corrupt files, it might fail to create files in system locations. Run these commands:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
This scans and fixes system files. I've seen it resolve the error on a Windows 10 PC that had a messed-up WinSxS folder.
Long File Paths
If the file path is over 260 characters, Windows can choke. Try saving the file with a shorter name or in a folder with a shorter path. For example, move from C:\Users\John\Documents\Project\Data\2024\Reports\Final\v2 to C:\Reports\.
Third-Party Software Locking the File
Had a client whose backup software was locking the entire D:\ drive. The error only appeared when they tried to create a file in the root of that drive. Closing the backup tool fixed it. Check Task Manager for anything that might be holding the folder open.
Prevention Tips
To avoid this error in the future, do these three things:
- Keep your drives clean. Don't let them fill up past 90%. Use Disk Cleanup regularly.
- Set correct permissions from the start. If you're setting up a shared folder, give the right users write access right away.
- Use a good antivirus. Some free ones cause more problems than they solve. Stick to Windows Defender—it's usually fine.
That's it. No fluff. Try the steps above, and you'll probably be done in five minutes. If not, hit me up in the comments.
Was this solution helpful?