ERROR_RETRY 0X000004D5: The operation could not be completed

What's actually happening here is...

The error code 0X000004D5 (which maps to system error 1225, ERROR_RETRY) is Windows telling you: "I tried, but something got in the way. Try again." It's not a hard failure like a disk crash. It's a soft failure – a timeout, a busy file, or a dead network link.

You'll see this most often when copying files across a network share (like from a NAS to your PC), or when Windows Update hits a hiccup. The trigger? A printer job that stalled, a remote desktop session that dropped, or a file locked by another user. The system didn't crash – it just couldn't finish the job right now.

Below are the three most common causes, ordered by how often they happen. Start with cause #1. If that doesn't fix it, move to #2, then #3. Don't skip.

Cause #1: Stale network credentials or disconnected drive mappings

This is the #1 reason you see this error. Windows cached your login credentials for a network share, but the server changed or the password expired. Now Windows tries to use the old credentials and fails. It throws ERROR_RETRY instead of ACCESS_DENIED because it's confused – it thinks the credentials might work if you try again.

The real fix: Clear those cached credentials and remap the drive.

1. Open Credential Manager. Press Win + R, type control /name Microsoft.CredentialManager, hit Enter.
2. Click Windows Credentials.
3. Look for any entries under Generic Credentials that match your network share (like MicrosoftAccount:target=MicrosoftOffice15_Data:SSPI... or TERMSRV/ServerName). Remove them by clicking the arrow and selecting Remove.
4. Now open File Explorer. Right-click any mapped network drives and choose Disconnect.
5. Remap the drive: Open This PC, click Map network drive, enter the full UNC path like \\ServerName\Share, and check Reconnect at sign-in. Enter fresh credentials when prompted.

Test the copy operation again. If you still see the error, the credentials weren't the only problem. Move on.

Cause #2: SMB service or network stack glitch

Sometimes the Server Message Block (SMB) protocol, which Windows uses for file sharing, just hangs. A bad driver update, a VPN that left a stale route, or a sudden power loss can leave the service in a weird state. You don't need to restart your whole PC – just restart the services that handle network file transfers.

The real fix: Restart the SMB and related services in a specific order.

1. Open an admin Command Prompt. Right-click Start, choose Windows Terminal (Admin).
2. Run these commands one by one. Wait for each to finish before the next:

net stop LanmanServer
net stop LanmanWorkstation
net start LanmanWorkstation
net start LanmanServer

The reason this order works: stopping the server first stops others from trying to connect. Then stopping the workstation clears out your outbound connections. Starting the workstation re-establishes the SMB client. Starting the server makes you visible again (if you're sharing files).

After this, try your file operation. Still failing? Then it's probably a file-level lock issue.

Cause #3: File locked by another process or user

This one's sneaky. The error might show up when you try to delete or move a file, but the file isn't locked by you – it's locked by a background process like Windows Search Indexer, an antivirus scanner, or a backup agent. The system can't access the file, so it returns ERROR_RETRY instead of waiting forever.

The real fix: Find out what's locking the file and stop it.

1. Download Process Explorer from Microsoft Sysinternals. It's free and doesn't need install.
2. Run it as admin. Press Ctrl + F to open the search box.
3. Type the name of the file you're trying to access. It'll show you every process holding a handle to that file.
4. Look for processes like SearchIndexer.exe, MsMpEng.exe (Windows Defender), or a backup agent. If you see one, decide if it's safe to kill. For SearchIndexer, you can stop it temporarily: open Services (services.msc), find Windows Search, right-click, choose Stop.
5. Try your operation again. If it works, you've found the culprit. You might need to exclude that folder from antivirus scanning or adjust indexing options.

If none of the above fixed it, check your hard drive for errors. Run chkdsk /f C: from an admin prompt and restart. Drive corruption can cause weird retry errors too, though it's rarer.

Quick-reference summary table

One last thing: if you're on Windows 11 and you're using a network share from an older NAS (like a QNAP or Synology), check that SMB 1.0/CIFS File Sharing Support isn't enabled in Windows Features. It's a security risk nobody needs. Instead, make sure your NAS uses SMB 2 or 3. That alone can prevent this error from showing up again.