Fix ERROR_CANCELLED (0X000004C7) – User Canceled Operation

Quick Answer

Check for stuck dialogs or pending user input. Open Task Manager, end any hung processes (Explorer, installer, or file copy), then restart Explorer. If that doesn't work, clear your clipboard and reboot.

What's Actually Happening Here

Windows error code 0X000004C7 (decimal 1223) is the system's way of saying "somebody told me to stop." The "somebody" is usually you — you clicked Cancel on a file copy dialog, an installer prompt, or a UAC elevation window. But here's the catch: sometimes the cancellation message arrives after the operation already committed changes, leaving things in a half-baked state.

I've seen this most often on Windows 10 and 11 when:

You cancel a large file copy in File Explorer and the progress window freezes.
An installer shows a "Are you sure?" prompt and you hit No, but the installer ignores the response.
A scheduled task or script calls CancelIoEx or CancelSynchronousIo on a handle.

The real frustration comes when the operation doesn't actually stop — the progress bar hangs, the window stays open, and you can't close it. That's because the cancellation was acknowledged (error returned) but the cleanup code never ran. What's happening under the hood: Windows sets an internal "cancel pending" flag on the I/O request packet, but the driver or application doesn't check it properly before writing data.

Fix Steps

Kill the stuck process. Press Ctrl+Shift+Esc, go to the Details tab, find the process (e.g., explorer.exe for File Explorer, msiexec.exe for installers). Right-click and "End task." If it's Explorer, use "Restart" from the Task Manager menu instead — quicker and restarts the shell cleanly.
Clear the clipboard. Open a Command Prompt as admin and run:
```
echo off | clip
```
This empties the clipboard, which sometimes holds a half-canceled file reference that keeps the operation alive.
Kill hung Explorer handles. Open an admin PowerShell and run:
```
Get-Process explorer | Stop-Process -Force
```
Shell restarts automatically after a few seconds. If it doesn't, press Ctrl+Shift+Esc, click File > Run new task, type explorer.
Check for orphaned background operations. Run tasklist /fi "status eq running" and look for rundll32.exe or dllhost.exe processes hogging CPU. Kill any that look suspicious — these can hold file copy or COM cancellation flags.
Reboot. If the error persists in a single app (like a game or installer), the app's state file is corrupted. Uninstall and reinstall, or delete its config folder under %APPDATA% or %LOCALAPPDATA%.

If Those Don't Work

Sometimes the error shows up inside an event log (Event ID 1223 or generic) and doesn't affect anything visible. In that case, ignore it — it's just Windows logging a user cancel. But if a specific program keeps throwing this error on every action, it's likely a bug in that program's handling of cancellation tokens. Not much you can do except report it to the vendor or switch to an alternative.

For power users: if you're writing a script and seeing this error from Copy-Item or Move-Item in PowerShell, wrap it in a try/catch and check $_.Exception.HResult for 0x800704C7 (same error, different HRESULT). The fix is to ensure your script doesn't call Cancel on the underlying FileStream prematurely.

How to Avoid This

Don't mash the Cancel button. Sounds obvious, but I've seen people click Cancel twice or three times out of frustration — each click sends another cancellation request, and Windows queues them. The first one might get processed, but the second can interfere with cleanup. If a progress window is unresponsive, use Task Manager instead of clicking Cancel repeatedly. Also, avoid dragging large files between drives during heavy system load — the I/O manager gets backlogged and cancellation responses get delayed.