Fix 0X000000B6 (ERROR_INVALID_ORDINAL) on Windows 10/11

Before You Start – 30 Seconds

I know this error is infuriating. You double-click an app, and boom – “The operating system cannot run %1” with error code 0X000000B6. It usually hits right when you need the program most, like opening QuickBooks on a Monday morning or launching a game after a Windows update.

Let's start with the laziest fix that actually works surprisingly often: restart your computer. I'm serious – about 1 in 4 of these errors are caused by a hung DLL handle that a reboot clears. If that doesn't do it, move on.

The 5-Minute Fix – Reinstall the Problem Program

This error means a DLL has the right name but the wrong version (or an exported function is missing). The quickest way to fix that is to reinstall the app that's crashing.

1. Open Settings > Apps > Installed apps (Windows 11) or Control Panel > Programs and Features (Windows 10).
2. Find the program that gives you the error – usually the one you tried to launch.
3. Click Uninstall. Don't skip this step – a repair install rarely fixes ordinal errors.
4. Restart your PC (yes, again).
5. Download the latest version of the program from the official source. Don't use an old installer you saved on a thumb drive – it probably has the same bad DLL.
6. Install it and test.

This fixes the problem maybe 60% of the time. If it doesn't, something deeper is going on – like a system-wide DLL mismatch.

The 15-Minute Fix – System File Checker + Clean Boot

If reinstalling didn't cut it, Windows itself might have a corrupted system file that's confusing the app. Here's the real fix combination I use on support calls:

Step 1: Run SFC and DISM

Open Command Prompt as Administrator – right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin).

sfc /scannow

Let it run. It'll take 10-15 minutes. If it finds corruption but can't fix it, run this next:

DISM /Online /Cleanup-Image /RestoreHealth

DISM downloads fresh system files from Microsoft. You'll need an internet connection. After DISM finishes, run SFC again – yes, one more time. That two-pass approach kills most system-level DLL errors.

Step 2: Clean Boot to Rule Out Third-Party Conflicts

Sometimes another app's DLL hijacks the system. A clean boot starts Windows with only Microsoft services, letting you test the problem app in isolation.

1. Press Win + R, type msconfig, hit Enter.
2. Go to the Services tab, check Hide all Microsoft services, then click Disable all.
3. Go to the Startup tab, click Open Task Manager, disable every startup item.
4. Click OK and restart.

Now try the app that was failing. If it works, you've got a conflict. Re-enable services in small batches (5 at a time) until the error comes back. The last batch you enabled is the culprit – uninstall or update that software.

If Nothing Worked – Advanced: Check DLL Dependencies

This is for when you're still stuck after the first two rounds. You'll need a tool called Dependency Walker (free, from dependencywalker.com). It shows exactly which DLL functions the app is calling and which ones are missing.

1. Download and run Dependency Walker as admin (right-click > Run as administrator).
2. Open the EXE or DLL that's throwing the error.
3. Look for lines with yellow or red icons – those are missing functions or files. The error code 0X000000B6 usually shows as “Ordinal not found” on a specific DLL.
4. Note the DLL name and the ordinal number (like “Ordinal 42”).
5. Google [DLL name] ordinal [number] – you'll usually find forum posts about a specific Windows update that broke it, or a driver version conflict.

I've seen this error most often with iertutil.dll after a botched Internet Explorer update (yes, even in 2025) or with nvlddmkm.sys after a bad NVIDIA driver install. In the driver case, use DDU (Display Driver Uninstaller) in Safe Mode to completely remove the driver, then install the latest from NVIDIA's site – not Windows Update.

Quick Summary – Pick Your Path

That compatibility mode trick surprised me the first time it worked for a legacy accounting app. Try it before you give up – it costs nothing.

If you're still seeing 0X000000B6 after all this, honestly, you're looking at a fresh Windows install. Back up your data, use the Reset this PC option in Settings (keep your files), and start clean. It's rare, but I've seen corrupted Windows installations where nothing short of a reset fixes ordinal errors.