Runtime Broker Can't Delete File: Why This Happens and How to Fix It

You’re staring at a file. You hit delete. Nothing. You try again, and Windows gives you that smug little notification saying the action can't be completed because the file is open in Runtime Broker. It’s annoying. Honestly, it’s one of those Windows quirks that makes you want to toss your laptop out a window. You know the file isn't open. You aren't using it. Yet, this "Runtime Broker" process has a metaphorical death grip on your data and won't let go.

Runtime Broker is a middleman. Specifically, it’s a Windows system process (RuntimeBroker.exe) that manages permissions for apps from the Microsoft Store—what we used to call Metro or Universal apps. It ensures these apps aren't doing anything they shouldn't, like accessing your location or photos without permission. But sometimes, the broker gets confused. It starts a task, finishes it, but forgets to "unlock" the file. That is why your runtime broker can't delete file error keeps popping up.

What is Runtime Broker actually doing with your files?

Most people assume it’s a virus. It isn't. If you check your Task Manager, you’ll see it sitting there, usually consuming very little memory. According to Microsoft’s official documentation, the process should stay under a few megabytes. However, if an app has a memory leak or a flawed permission request, Runtime Broker can spike.

When you try to delete a file and it fails, it’s usually because a background app—maybe Photos, Groove Music, or even the Calculator—is technically "looking" at that file through the Broker. Because Windows has a strict file-locking mechanism, two processes can't control a file's life cycle at the same time. If Runtime Broker is "auditing" the file for a Windows Store app, the File Explorer delete command gets rejected.

It’s a safety feature that feels like a bug.

The Quick Fix: Killing the Process

The fastest way to get your folder clean is to just stop the middleman. You won't break your computer. Open Task Manager by hitting Ctrl + Shift + Esc. Look for Runtime Broker in the "Processes" tab. You might see more than one; that’s normal. Right-click it and hit End Task.

Try deleting your file now.

Usually, this works instantly. The process will restart itself anyway the next time you open a Store app, so it’s a temporary kill that clears the lock. But if it keeps happening, you've got a deeper issue with how Windows is handling background permissions.

Why the "Tips" Feature is Secretly Making This Worse

There is a weird, documented quirk in Windows 10 and 11. The system likes to give you "tips and suggestions" as you use OS features. To do this, Runtime Broker often scans files to see how you're using the system so it can suggest a "better way" to do things. It sounds helpful. In reality, it just locks up your files.

Go to your Settings. Look for System, then Notifications & actions. Find the toggle that says "Get tips, tricks, and suggestions as you use Windows" and flip it to Off. Many users on forums like TenForums and Reddit have found that this single toggle stops the runtime broker can't delete file loop because it stops the broker from constantly "sniffing" files for no reason.

✨ Don't miss: Pyramid Formula for Surface Area Explained: What Most People Get Wrong

The Photos App Culprit

If you're trying to delete an image or a video, the Windows Photos app is almost certainly the villain. Even if the app is closed, its background processes stay active to update the library or generate thumbnails.

Sometimes, the Photos app starts an indexing task. It tells Runtime Broker, "Hey, I need to check the metadata on these 500 pictures." If you try to delete the 5th picture while the Broker is still thinking about it, you get the error. You can try resetting the Photos app in the "Apps & Features" menu, or simply switch to a more lightweight third-party viewer like IrfanView or HoneyView to avoid the constant background indexing of the default Microsoft apps.

Dealing with Stubborn App Permissions

Because Runtime Broker is all about permissions, sometimes the "ownership" of the file gets tangled. If the file was created by an app that has since crashed, the Broker might think the app is still active.

1. Right-click the file you want to delete.
2. Select Properties, then the Security tab.
3. Click Advanced.
4. Look at the "Owner" at the top. If it isn't you, click Change and type your username.
5. Check the box "Replace owner on subcontainers and objects" and hit OK.

By taking explicit ownership away from the "System" or "TrustedInstaller" and giving it to yourself, you can often override the Broker’s lock. It’s a bit of a power move, but it’s effective when the software refuses to be polite.

A Note on System File Checker (SFC)

If this is happening to every file you try to delete, your RuntimeBroker.exe file itself might be corrupted. This is rare, but it happens after bad Windows updates.

Open PowerShell or Command Prompt as an Administrator. Type sfc /scannow.

Windows will scan its own heart. If it finds that the Broker file or its associated DLLs are wonky, it will replace them from a local cached image. It takes about ten minutes. Grab a coffee.

Real World Example: The "Ghost" PDF

I once dealt with a user who couldn't delete a PDF on their desktop for three weeks. Every time they tried, Runtime Broker blocked it. It turned out they had the "Preview Pane" enabled in File Explorer. Because the Preview Pane uses a "mini" version of the Edge browser (a Windows Store app) to show the file content, Runtime Broker was constantly keeping the file "open" so Edge could display it.

We turned off the Preview Pane (Alt + P in Explorer), and the file deleted instantly.

Sometimes the "expert" fix is just realizing that the way you're looking at the file is the reason you can't kill the file.

Immediate Action Steps

• Check the Preview Pane: If you see a preview of the file on the right side of your folder, turn it off. It’s the most common "invisible" lock.
• Use the 'Move' Trick: If Delete fails, try moving the file to a different drive (like a USB stick). Sometimes the act of moving forces Windows to hand off the handle from Runtime Broker to the file system.
• Safe Mode: If all else fails, boot into Safe Mode. Runtime Broker doesn't load its full permission set there, allowing you to delete anything that isn't a core system file.
• Resource Monitor: Open Resource Monitor (type resmon in the Start menu), go to the CPU tab, and search for the filename in the "Associated Handles" search bar. It will tell you exactly which process is holding it hostage. If it says RuntimeBroker.exe, you know where to aim.

The runtime broker can't delete file issue isn't a sign of a dying hard drive or a malware infection. It’s just the friction between a modern app ecosystem and a decades-old file system architecture. Kill the process, tweak your notification settings, and you'll usually be back in control within sixty seconds.