Fix STATUS_RESOURCE_NOT_OWNED 0XC0000264 Error

This error means a program tried to release a lock or handle it didn't own. Usually caused by buggy drivers or software. We'll show you how to fix it.

Quick answer for pros

Uninstall or update the driver or software that's causing the conflict. Check Event Viewer for the exact source, then use a clean boot to isolate it. Run SFC and DISM too – corrupt system files can trigger this.

Why does this error happen?

The STATUS_RESOURCE_NOT_OWNED error – code 0XC0000264 – shows up when a program tries to release a lock, handle, or other system resource that it hasn't grabbed first. Think of it like a neighbor trying to unlock your front door with their key – it just doesn't work. This usually happens because of a bug in a driver or an app that's poorly coded. I've seen it most often with older antivirus software, VPN clients, and some game overlays (like Discord or Xbox Game Bar). On Windows 10 and 11, it can also pop up after a bad update or when a driver doesn't fully support the OS version.

Fix steps – do these in order

Step 1: Check Event Viewer for the culprit

You need to know what program or driver is causing the mess. Here's how:

Press Windows Key + X and select Event Viewer.
In the left pane, expand Windows Logs and click Application.
Look for errors with a red icon. The source column will show something like Application Error or .NET Runtime. Double-click each one.
In the details, find the Faulting module name or Exception code – it should mention 0xc0000264. Write down the Faulting application path (like C:\Program Files\SomeApp\app.exe).

After you identify the app or driver, you'll know what to fix. If it's a driver (like nvlddmkm.sys for Nvidia), skip to Step 3. If it's a normal app, go to Step 2.

Step 2: Uninstall or update the problematic app

Once you know the app, get rid of it or update it.

Press Windows Key + I to open Settings.
Go to Apps > Installed apps (or Apps & features on older builds).
Find the app from the Event Viewer log. Click the three dots next to it, then choose Uninstall.
Follow the prompts. Restart your PC afterward.

If you want to keep the app, check the developer's website for a newer version. Download and install it. Restart again. If the error stops, you're good. If not, move on.

Step 3: Update all your drivers

Outdated or buggy drivers – especially graphics, audio, and network drivers – are a common cause. Here's the manual way (skip the automatic updater tools – they often install junk):

Press Windows Key + X, select Device Manager.
Expand Display adapters. Right-click your graphics card (like NVIDIA GeForce RTX 3060) and choose Update driver.
Select Search automatically for drivers. Let Windows find the latest.
Repeat for Network adapters, Sound, video and game controllers, and System devices.

After each update, restart your PC. If Windows doesn't find a new driver, go to the manufacturer's site (like Intel or AMD) and download the latest manually.

Step 4: Run SFC and DISM scans

Corrupt system files can trigger this error too. Let's fix them.

Right-click the Start button and select Windows Terminal (Admin) or Command Prompt (Admin).
Type sfc /scannow and press Enter. Wait – it takes 10-15 minutes.
After it finishes, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This takes longer – maybe 20 minutes. Let it complete.
Restart your PC.

Step 5: Clean boot to isolate the problem

If the error still happens, a clean boot helps you find the exact service or startup program causing the conflict. It disables everything non-Microsoft, then you turn things back on one by one.

Press Windows Key + R, type msconfig, and hit Enter.
Go to the Services tab. Check Hide all Microsoft services at the bottom. Then click Disable all.
Go to the Startup tab. Click Open Task Manager. Disable every startup item by right-clicking and choosing Disable.
Click OK in System Configuration. Restart your PC.

Now test your app. If the error is gone, you know it's one of the disabled services or startup items. Enable them in small groups (5 at a time) and restart between each group until the error comes back. When it does, you've found the culprit. Uninstall or update that item.

Alternative fixes if the main ones fail

Sometimes the steps above don't work. Here are other things to try:

Check for Windows updates. Go to Settings > Windows Update > Check for updates. Install everything and restart.
Run a malware scan. Use Windows Defender's offline scan or Malwarebytes. Bad software can mess with resource ownership.
Roll back a recent driver update. In Device Manager, right-click the device, go to Properties > Driver > Roll Back Driver. If the error started after an update, this often helps.
Repair .NET Framework. This error sometimes shows up with .NET apps. Download the .NET Framework Repair Tool from Microsoft's site and run it.
Do a system restore. If you have a restore point from before the error started, go to Control Panel > Recovery > Open System Restore and pick that point.

Prevention tips

To keep this error from coming back, do these things regularly:

Keep Windows updated. Let automatic updates run.
Update drivers only from official manufacturer sites – no third-party tools.
Uninstall software you don't use. Old or abandoned apps often have bugs like this.
If you see this error often with a specific program, check its support forums. The developer might have a patch.
Run SFC and DISM scans once a month if you're a power user. Windows 11's automatic repair tries to fix corruption, but it's not perfect.

One last thing – if you're using any game overlays (Discord, Xbox, Nvidia GeForce Experience), try turning them off. I've seen 0XC0000264 more times than I can count from those overlays fighting for resources. Disable them one at a time and test.