You're trying to enable some plug-in—usually in Windows Media Player or an old IE-based app—and bam: NS_E_SCRIPT_DEBUGGER_NOT_INSTALLED (0XC00D1582). The exact message reads "The plug-in cannot be enabled because a compatible script debugger is not installed on this system." I've seen this on Windows 7 machines, but it pops up on Windows 10 too, especially after a fresh install or when someone stripped out IE features.
The root cause is simpler than you'd think. Windows uses a scripting engine (JScript or VBScript) for certain plug-ins, and if the debugger component isn't registered properly, the plug-in refuses to start. It's not that you need Visual Studio or some heavy debugger—it's just the Windows Script Debugger component that's missing. Most people don't even realize it's a separate installable feature.
The Quick Fix
You've got two paths here. The easiest is to enable it through Windows Features. On Windows 10, it's tucked away but still there. Here's the step-by-step:
- Press Win + R, type
optionalfeatures, hit Enter. - Look for Internet Explorer 11—yes, even if you don't use IE. Expand it.
- Check the box for Internet Explorer 11 (if unchecked) and also expand Internet Explorer 11 → Web Platform or similar.
- You'll see Script Debugging or Windows Script Debugger—tick it on.
- Click OK and let Windows install it. Reboot if it asks.
On Windows 7, it's under Control Panel → Programs → Turn Windows features on or off, then Internet Explorer 8/9 → Web Platform → Script Debugging.
If you don't see that option—some stripped-down builds hide it—you can try installing the Windows Script Debugger directly. Microsoft used to offer a standalone download, but it's been rolled into the OS. The registry route works too, but only if you're comfortable poking around. I'd skip that unless the feature toggle does nothing.
When the Feature Is Already On
Last month I had a client whose machine showed the feature was enabled, but the error still killed the plug-in. The problem wasn't the debugger itself—it was a corrupted registration. The fix is to re-register the scripting DLLs. Open an elevated Command Prompt (right-click → Run as administrator) and run these:
regsvr32 jscript.dll
regsvr32 vbscript.dll
regsvr32 dispex.dll
Then restart the app that was throwing the error. This re-registers the scripting engines, and in most cases, the plug-in starts working immediately.
Still Failing? Check This
If you've done the feature install and the regsvr32 dance and you're still stuck, you're dealing with something else. The most common culprit: a third-party script debugger that's partially installed—like an old Office debugger or a debugging tool from some dev environment. It can break the registration. Uninstall any script debugger tools you don't use, then re-run the regsvr32 commands.
Another thing to verify: is the plug-in actually 32-bit or 64-bit? If you're running a 64-bit browser and the plug-in expects 32-bit, you'll get weird errors. On Windows, you can force the 32-bit version of IE or the app to see if that helps. For example, launch C:\Program Files (x86)\Internet Explorer\iexplore.exe directly.
Finally, check that your Windows Script Host isn't disabled. If someone turned it off via Group Policy or the registry, the debugger can't attach. Look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings for a value named Enabled—if it's set to 0, set it to 1 and reboot.
In my experience, the feature toggle fixes 80% of these cases. The regsvr32 trick handles another 15%. Only the last 5% need the registry check. Start there and you won't waste time.