Fix ERROR_FUNCTION_FAILED (0X0000065B) in Windows

Quick answer for advanced users

Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. If that doesn't stick, check the user account's permissions on the affected path—usually C:\Windows\System32 or the app's install folder.

What's this error really about?

0X0000065B pops up when Windows tries to execute a function—like opening a file, creating a process, or loading a driver—and the call fails partway through. The culprit here is almost always one of three things: a corrupted system file, a permission mismatch, or a third-party service that's blocking the operation. I've seen this most often when someone runs an installer without admin rights, or after a failed Windows Update leaves a DLL in a bad state. The error itself doesn't tell you which function failed, so you have to work backwards from the context.

Numbered fix steps

Run System File Checker — Open Command Prompt as Administrator. Type sfc /scannow and hit Enter. Let it finish. If it finds corrupt files and fixes them, reboot and test.
Use DISM to fix the image — If SFC fails or finds nothing, run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store that SFC relies on. Takes a few minutes—don't cancel it.
Check file and folder permissions — Right-click the folder where the error occurs (e.g., the app's install directory or C:\Windows\System32). Go to Properties > Security. Make sure your user account has Full Control or at least Modify. If not, click Edit and add it.
Run the program as Administrator — Right-click the executable, choose Properties > Compatibility tab, check 'Run this program as an administrator'. Apply and restart the app.
Disable third-party antivirus temporarily — Norton, McAfee, and even some AVG builds can intercept system calls and cause 0X0000065B. Turn off real-time protection, test the operation, then re-enable and consider switching to Defender if it's the root cause.

When the main fix doesn't work

If the steps above fail, try these alternative approaches:

Create a new user profile — This error sometimes follows a corrupted user profile. Go to Settings > Accounts > Family & other users, add a new user, log into it, and test the same operation.
Perform a clean boot — Use msconfig to disable all non-Microsoft services. If the error disappears, one of your startup programs or services is the culprit. Enable them one by one to isolate it.
Check the Event Viewer — Press Win + X and select Event Viewer. Go to Windows Logs > System. Look for events with ID 1000 or 7034 around the time of the error. The details often point to a specific DLL or driver file. Google that filename with '0x65B' for more targeted help.

Prevention tip

Keep Windows Update current—most 0x65B bugs get patched in cumulative updates. Also, avoid running installers or scripts from untrusted sources that might alter permissions on system folders. If you're a developer, make sure your code uses SEH (structured exception handling) to catch these failures gracefully instead of crashing the app.