STG_E_CANTSAVE (0x80030103) – Drive won’t let you save? Here’s why

Cause 1: File permissions are locked down – most common fix

This is the first thing I check when a client calls and can’t save a file to their external drive or network share. 9 times out of 10, the permissions on the folder or drive got messed up. Maybe you moved a drive from one PC to another, or Windows Update decided to reset security settings (yes, it happens).

The error 0x80030103 basically means Windows tried to write and the storage said “no way”. Let’s fix that.

Fix: Take ownership and grant Full Control

1. Right-click the drive or folder where the error appears, go to Properties.
2. Click the Security tab, then Advanced.
3. At the top, next to Owner, click Change.
4. Type your username (like Derek or Administrators), click Check Names, then OK.
5. Check the box Replace owner on subcontainers and objects. Click OK.
6. Back in the Security tab, select your user, click Edit, and tick Full Control.
7. Apply, OK, and try saving again.

Had a client last month whose entire print queue died because of this – turns out their file share permissions were set to Read-only for the whole department. Took five minutes to fix once I saw the error code.

Cause 2: The drive is failing – bad sectors or dying hardware

If permissions look fine but you still get the error, the drive might be toast. I’ve seen this a lot with external USB drives that get bumped or overheat. The error code is Windows saying “I tried to write, but the drive gave me garbage back”.

Quick check: Run CHKDSK

1. Open Command Prompt as Administrator (search cmd, right-click, run as admin).
2. Type chkdsk D: /f /r (replace D: with your drive letter).
3. Let it run – this can take an hour on a big drive.

What the output means:
If CHKDSK reports bad sectors or unrecoverable errors, start backing up your data immediately. Do not keep using that drive for daily work – it will fail completely.

I once had a client’s external drive with this exact error – CHKDSK showed 2,000 bad sectors. We copied what we could, then tossed the drive. The error was the warning.

Cause 3: File system corruption – NTFS structure got bent

Sometimes the drive is physically fine, but the file system table is corrupted. This can happen after a power outage during a write, or when you yank a USB drive without safely ejecting. Yes, that actually matters.

Fix: Use SFC and DISM for system files

1. Run Command Prompt as Admin.
2. Type sfc /scannow – let it finish.
3. Then run DISM /Online /Cleanup-Image /RestoreHealth – this fixes Windows system files that might be messing with the storage stack.

Also: Run Check Disk with repair

If CHKDSK from cause 2 didn’t find bad sectors, run it again with /f only:

chkdsk D: /f

This repairs file system errors without the deep sector scan. I’ve fixed this exact error on a USB stick this way – the stick was fine, but the NTFS master file table had a hiccup.

Quick-reference summary table

Bottom line: Start with permissions. If that doesn’t work, check the drive health. Don’t waste time on uninstalling drivers or running registry cleaners – they won’t fix 0x80030103. Been there, seen that.