Fix ERROR_BIZRULES_NOT_ENABLED (0XC0090003) in Windows

Quick answer

Open Local Group Policy Editor, go to Computer Configuration > Administrative Templates > Windows Components > Windows Script Host, set "Allow Microsoft script host" to Enabled. Then restart your app. That's usually all it takes.

Why this happens

This error shows up when a program tries to run a business rule script — like a .vbs or .js file — and Windows says "no." The system has a setting that blocks script execution by default or through a policy. You'll often see this after a Windows Update or an IT admin tightened security. I've seen it most on Windows 10 22H2 and Windows 11 23H2, especially after updates like KB5034441. The exact error code is 0XC0090003, and it means the calling application can't use the built-in scripting engine.

Here's the thing: Microsoft disabled script hosts in many apps for security. But some legit business apps — inventory tools, custom automation, scheduling software — rely on them. So you gotta turn it back on for that one app, not for everything.

Fix steps

Before you start, close all running programs. You'll need admin rights.

1. Press Win + R, type gpedit.msc, and press Enter. If you don't have Group Policy (Windows Home edition), skip to the registry fix below.
2. In the left pane, navigate to: Computer Configuration > Administrative Templates > Windows Components > Windows Script Host.
3. In the right pane, double-click Allow Microsoft script host to execute scripts.
4. Set it to Enabled, then click Apply and OK. After clicking Apply you should see the policy change saved.
5. Close Group Policy Editor. Then restart your computer or at least log off and back on.
6. Open the app that gave the error. It should work now. If not, try the alternative fixes below.

Alternative fixes if the main one fails

Registry method (if you don't have Group Policy)

For Windows Home users or if gpedit.msc didn't work, edit the registry.

1. Press Win + R, type regedit, press Enter.
2. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings
3. On the right, look for a DWORD named Enabled. If it's not there, create it: right-click in empty space, choose New > DWORD (32-bit) Value, name it Enabled.
4. Double-click Enabled, set Value data to 1. Click OK.
5. Close Regedit, restart your PC.

After this, the error should disappear. If you still see it, the app might be overriding this with its own settings — check the app's documentation for a scripting enable toggle.

Check app-specific policies

Some business apps, like those from SAP or Oracle, have their own script policy. Look in the app's config folder for a .xml or .ini file that controls script execution. Set ScriptEnabled=1 or similar. I've seen this with older Baan systems and custom .NET applications.

Prevention tip

Don't leave script execution wide open for all apps. That's a security risk. Instead, after fixing it for your specific app, consider restricting it back. Use AppLocker or Windows Defender Application Control to allow only the exact script file your app needs. That way, you keep the fix but don't invite trouble.

Also, always test after a Windows Update. Updates sometimes reset group policies or registry keys. If the error comes back, you'll know where to look.