isapi.dll is a Windows component of Internet Information Services (IIS), not a game or general-purpose runtime DLL. If Windows or IIS says isapi.dll is missing, cannot load, or is invalid, restore the IIS feature and then check the site’s module and handler configuration.
What is isapi.dll
isapi.dll implements IIS support for ISAPI, which stands for Internet Server Application Programming Interface. IIS uses its native IsapiModule to load and process ISAPI extensions used by older web applications, Classic ASP sites, and some third-party server components.
Microsoft documents the normal system path as:
%windir%System32inetsrvisapi.dll
| Item | Correct identification |
|---|---|
| File | isapi.dll |
| Windows component | Internet Information Services |
| IIS module | IsapiModule |
| Feature | IIS → World Wide Web Services → Application Development Features → ISAPI Extensions |
| Normal path | %windir%System32inetsrvisapi.dll |
| Typical context | IIS, Classic ASP, ISAPI-based web applications |
The file is not part of Visual C++, DirectX, .NET, a graphics driver, or an ordinary desktop application. Microsoft’s IIS Modules overview identifies IsapiModule and its default image path.
Do not confuse the IIS host module with an application extension. Files such as asp.dll, aspnet_isapi.dll, a PHP ISAPI module, or a vendor’s custom ISAPI DLL are separate components. Installing ISAPI Extensions will not automatically restore one of those application-specific files.
#1 Best Overall
First, identify the type of error
The exact wording points to the next step.
IIS HTTP 500 error
A Classic ASP site may show:
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x8007000d
Handler "ASPClassic" has a bad module "IsapiModule" in its module list.
This can mean that IsapiModule is missing from the site or server module list. The file may exist even though IIS is not registering or loading it correctly.
Microsoft also documents 0x800700c1 for an invalid script mapping, including a mapping to an incorrect or incompatible DLL. In that situation, replacing isapi.dll is unlikely to help.
Generic Windows loader message
Messages such as these may come from an application or loader rather than IIS:
- “The program can’t start because isapi.dll is missing from your computer”
- “Error loading isapi.dll”
- “isapi.dll is not designed to run on Windows”
Treat these as possible loader wording until you identify the program, event log entry, or IIS request that produced them. If only one site fails, configuration or a handler mapping is more likely than a missing system file. If every IIS site fails, an IIS feature or Windows component problem becomes more likely.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Fix 1: Install or enable ISAPI Extensions
This is the safest first fix when IIS was never installed, was removed, or changed during Windows setup, hardening, or an upgrade.
Windows 11 and Windows 10 client editions
- Press Windows + R.
- Type
optionalfeatures. - Press Enter.
- Expand Internet Information Services.
- Expand World Wide Web Services.
- Expand Application Development Features.
- Select ISAPI Extensions.
- Select any other IIS feature your application explicitly requires, such as ASP for Classic ASP.
- Select OK.
- Allow Windows to install the components.
- Restart the computer, or restart IIS from an elevated Command Prompt:
iisreset
The servicing feature name is IIS-ISAPIExtensions. You can install it from an elevated Command Prompt with:
Rank #2
DISM /Online /Enable-Feature /FeatureName:IIS-ISAPIExtensions /All
Microsoft lists the feature under its typical IIS workloads.
Windows Server
- Open Server Manager.
- Select Manage.
- Choose Add Roles and Features.
- Select Role-based or feature-based installation.
- Select the target server.
- Expand Web Server (IIS).
- Expand Web Server.
- Expand Application Development.
- Select ISAPI Extensions.
- Continue through the wizard and select Install.
- Restart IIS or reboot if prompted.
Microsoft’s ISAPI and CGI Restrictions documentation also describes the IIS installation path and related configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check whether the fix worked
Open File Explorer and enter this path:
%windir%System32inetsrvisapi.dll
Then open the affected site. A successful repair usually removes the missing-module error. If the file exists but the site still reports a bad module, continue with the IIS configuration checks below.
Fix 2: Repair Windows component files with DISM and SFC
Use this step when ISAPI Extensions is installed but the file is missing, damaged, or Windows reports that the component installation failed.
- Open Start.
- Type
cmd. - Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish. It may take time and can appear paused.
- Run System File Checker:
sfc /scannow
- Restart Windows.
- Check again:
%windir%System32inetsrvisapi.dll
DISM repairs the Windows component store that SFC uses, so run DISM before SFC. Microsoft documents this sequence in its guidance for repairing Windows Update and component corruption and explains SFC behavior in its System File Checker documentation.
If DISM says that source files cannot be found, use matching Windows installation or repair media rather than downloading an individual DLL. Microsoft documents /Source and /LimitAccess in Repair a Windows image.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
Manually hunting through Windows component versions and repeating DISM or SFC without knowing what changed can be time-consuming. Outbyte PC Repair can scan for issues and show what needs attention; its repair features require the full version, and reinstalling or repairing IIS remains the definitive fix for this component.
Fix 3: Confirm IsapiModule in IIS Manager
If the file exists and the feature is enabled, the IIS configuration may be incomplete or damaged.
- Press Windows + R.
- Type
inetmgr. - Press Enter.
- In the Connections pane, select the server or affected site.
- Open Modules.
- Look for
IsapiModule. - If it is absent at the appropriate server or site level, review the configuration before adding anything manually.
- Select the site and open Handler Mappings.
- Find the handler that produces the error, such as a Classic ASP mapping.
- Confirm that its module list includes the expected IIS module.
- Confirm that its executable path points to the application’s intended extension, not an unrelated DLL.
Microsoft’s HTTP 500 troubleshooting reference specifically discusses a bad IsapiModule entry and the native module configuration.
Do not change applicationHost.config blindly. Export or back up the IIS configuration first, and make changes at the narrowest level possible. If only one site fails, compare its Modules and Handler Mappings with a working site or restore the site’s known-good configuration.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Fix 4: Check ISAPI and CGI Restrictions
IIS can block an otherwise valid extension through its security restrictions.
- Open IIS Manager.
- Select the server in the Connections pane.
- Open ISAPI and CGI Restrictions.
- Look for the affected extension.
- If it is listed and denied, confirm that it is a known, required file.
- Allow it only if you trust the publisher and the application requires it.
- Recycle the application pool and test the site again.
Do not allow every unknown DLL. A missing aspnet_isapi.dll, PHP module, or vendor extension must be verified against that application’s official documentation and installer.
Fix 5: Check the application pool architecture
A 32-bit ISAPI extension cannot always run in a 64-bit-only application pool, and a 64-bit extension may not work in a 32-bit configuration.
Rank #4
- Upgraded Two Zipper Pockets: Forvencer server books feature two secure zipper pockets for better organization of coins, cash, and receipts, ensuring that everything you collect has a safe and secure place
- Smart Storage & Quick Access: Designed with 8 multi-functional compartments, the right side includes a guest receipt pad, while the left has a money pocket, ticket pocket, and credit card slot. Two small clear pockets store bills, receipts, and other visible items. A stitched pen loop ensures you always have your favorite pen ready
- High-quality & Easy to Clean: Crafted from high-quality PU leather with heavy-duty stitching, this server book is built to last. It resists tears, scratches, and its waterproof surface makes cleaning easy with just a damp cloth or a non-chlorine sanitizer
- Perfect Fit for Your Apron: Measuring 5” x 8”, this compact organizer is slightly smaller than other models, making it ideal for bending or sitting while carrying in your server apron. It holds everything a waitress needs—a place for everything
- What's Included: This server organizer comes with multiple open and zippered pockets to store money, receipts, tips, etc. Clear sleeves are perfect for keeping menus or special lists while serving. Available in a variety of colors, allowing you to express yourself even when in uniform
- Open IIS Manager.
- Select Application Pools.
- Find the pool used by the affected site.
- Select Advanced Settings.
- Check Enable 32-Bit Applications.
- Confirm the setting required by the application or ISAPI extension vendor.
- Check the extension’s documented architecture.
- Recycle the pool and test again.
Do not copy a file into SysWOW64 or another directory as a guess. IIS installation details and application architecture determine which component is loaded. Historical Microsoft servicing records show separate x86 and x64 IIS files, while exact versions vary by Windows release and servicing level.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIf the problem began after installing a third-party ISAPI extension, remove or repair that extension using its official installer. The Microsoft isapi.dll module and the third-party DLL are not interchangeable.
Fix 6: Investigate antivirus quarantine or servicing failure
If the file disappeared suddenly:
- Open your antivirus or Windows Security quarantine history.
- Check whether the file was quarantined.
- Confirm that the file is in the expected IIS path and is published by Microsoft before restoring anything.
- Run a full Microsoft Defender or reputable security scan.
- Run DISM and SFC after the scan.
- Review Event Viewer for Windows servicing, IIS, or application errors.
If the issue started immediately after a failed Windows update or IIS configuration change, use System Restore or a known-good configuration backup where available. Reinstalling IIS can be a later option, but do not assume it will preserve every existing IIS setting or site configuration.
What not to do
Do not download isapi.dll from a DLL website
Random DLL downloads can contain malware, the wrong Windows build, the wrong architecture, or a file with an incompatible servicing level. Copying such a file into System32, inetsrv, or an application folder may also hide the real IIS configuration problem.
Use Windows Features, Server Manager, DISM, SFC, Windows repair media, or the official installer for the affected application instead.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not normally run regsvr32 isapi.dll
regsvr32 registers DLLs that provide registration entry points such as DllRegisterServer. It does not install the IIS role service or configure IsapiModule.
Running this command is generally inappropriate:
regsvr32 isapi.dll
It may produce a registration error and distract from the missing feature, module list, handler mapping, restriction, or architecture problem. Microsoft explains the command’s purpose in its regsvr32 documentation.
Do not use Device Manager for this problem
isapi.dll is an IIS software component, not a hardware driver. Device Manager will not restore it. Driver updates are relevant only if a separate hardware or application problem is also present.
If a related application update exposes several unrelated driver errors, manually identifying the correct driver can be tedious. Outbyte Driver Updater can scan and identify stale drivers; installation through the full version is optional, and it is not a substitute for repairing IIS or its application-specific ISAPI extension.
FAQ
Is isapi.dll part of Windows?
Yes. It is part of IIS, specifically the ISAPI Extensions feature. IIS is optional on Windows client editions and is an optional server role service on Windows Server.
Where should isapi.dll be located?
The normal IIS path is:
%windir%System32inetsrvisapi.dll
Exact file versions and sizes vary with the Windows release and servicing level.
Is isapi.dll the same as asp.dll or aspnet_isapi.dll?
No. isapi.dll is the IIS host module. asp.dll, aspnet_isapi.dll, PHP modules, and vendor ISAPI extensions are separate files that may be required by particular applications.
Why does IIS mention a missing DLL when the file exists?
The error may actually describe a missing IsapiModule registration, a bad handler mapping, a denied ISAPI restriction, or an incompatible application-pool architecture. Check Modules and Handler Mappings before replacing the file.
Should I reinstall IIS?
Only after enabling the required feature, repairing Windows files, and checking configuration. If you do reinstall IIS, back up site files, certificates, application pools, and configuration first because existing settings may not all be preserved.
What if DISM and SFC cannot repair it?
Use a matching Windows repair source as documented by Microsoft. If that fails, consider System Restore, repair media, or professional support. If only one application extension is missing, repair that application from its official installer instead of replacing Microsoft’s IIS module.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
