Fix IIS Restore Error 0x8007007e Module Not Found

This guide walks you through resolving the IIS restore error 0x8007007e, which typically appears when a web application or site fails to load because a required module or DLL is missing. You’ll learn how to identify the missing component, repair your IIS installation, and restore your site to working order. No advanced tools are needed—just administrative access to your Windows server.

What You’ll Need

Administrator access to the Windows server running IIS.
Access to the IIS Manager (inetmgr) or command prompt.
The path to your web application’s root folder (where web.config resides).
Optional: The original installer for any third-party modules you use (e.g., URL Rewrite, ARR).

Step-by-Step

Identify the exact error message. Open the IIS Manager, select your site, and click on “Error Pages” in the middle pane. Look for the error 0x8007007e entry. Note the module name mentioned in the error details—this is often something like “FastCgiModule”, “RewriteModule”, or a custom DLL.
Check the web.config file. Navigate to your site’s root folder and open web.config with a text editor. Look for <modules> and <handlers> sections. Any module or handler listed here must be installed on the server. If you see a module that isn’t in the IIS Modules list (step 3), that’s likely the culprit.
Verify installed modules in IIS. In IIS Manager, select your server node (top of the tree), then double-click “Modules”. Compare the list with what’s referenced in web.config. If a module is missing, you’ll need to install it. For built-in modules, you can re-enable them via “Configure Native Modules” in the Actions pane.
Repair or reinstall the missing module. If it’s a Microsoft module like URL Rewrite or Application Request Routing (ARR), download the latest installer from the official Microsoft website and run it. For third-party modules, use the vendor’s installer. After installation, restart IIS by running iisreset from an elevated command prompt.
Re-register ASP.NET (if applicable). If the error involves ASP.NET (e.g., aspnet_isapi.dll), run the following from an elevated command prompt:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
Adjust the path if you’re using a different .NET version or 32-bit mode.
Check for 32-bit vs 64-bit mismatches. If your application pool is set to “Enable 32-Bit Applications = True”, but the module is 64-bit (or vice versa), you’ll get this error. In IIS Manager, select Application Pools, right-click your pool, choose “Advanced Settings”, and set “Enable 32-Bit Applications” to match the module’s architecture.
Verify the module’s DLL exists. Some modules reference a DLL path in the registry or web.config. Ensure the file exists at that path. For example, if a custom module points to C:\Program Files\MyModule\mymodule.dll, confirm that file is present.
Restart IIS and test. Run iisreset from an elevated command prompt, then browse to your site. If the error persists, check the Windows Event Viewer (under Windows Logs > System) for more details.

Common Mistakes

Ignoring the module name. The error message always names the missing module. Skipping this step leads to random reinstalls that don’t fix the issue.
Forgetting to restart IIS. After installing a module, you must restart IIS for changes to take effect. A simple app pool recycle may not be enough.
Mixing 32-bit and 64-bit. Installing a 64-bit module on a server with 32-bit app pools (or vice versa) is a common cause. Always match the architecture.
Editing web.config incorrectly. Removing a module from web.config without uninstalling it from IIS can cause other errors. Only edit web.config if you’re sure the module isn’t needed.

Tips

Use the Configuration Editor. In IIS Manager, select your site, then “Configuration Editor” in the middle pane. This tool lets you edit web.config values safely without breaking syntax.
Backup web.config. Before making any changes, copy web.config to a backup file. This allows quick rollback if something goes wrong.
Test in a staging environment. If possible, replicate the error on a test server first. This avoids downtime on production.
Keep a list of installed modules. Maintain documentation of all modules and their versions. This helps when migrating or restoring servers.

Troubleshooting

If the steps above don’t resolve the error, try these additional measures:

Check the Application Pool identity. The app pool account must have read permissions to the module’s DLL and the site’s folder. Right-click your site in IIS, select “Edit Permissions”, and grant the app pool identity (e.g., IIS AppPool\YourPoolName) read access.
Review the Windows Event Viewer. Look for errors from IIS-W3SVC or IIS-Configuration. The event log often contains the exact module path that failed.
Use Failed Request Tracing. Enable tracing on your site (under “Failed Request Tracing” in IIS) to capture detailed logs of the request that fails. This can pinpoint the exact handler or module.
Run System File Checker. If you suspect corrupted system files, run sfc /scannow from an elevated command prompt. This may repair missing IIS components.
Repair the IIS installation itself. Go to Control Panel > Programs > Turn Windows features on or off. Uncheck Internet Information Services, reboot, then re-check it and reboot again. This reinstalls core IIS files.

Frequently Asked Questions

What does error 0x8007007e mean?

It means “The specified module could not be found.” Windows cannot locate a DLL or executable that IIS needs to run your site.

Why does this happen after a server restore?

Restores often miss registry entries, DLLs, or module installations. If the backup was taken before a module was installed, the restore won’t include it.

Can I fix this without reinstalling IIS?

Yes, in most cases you can fix it by reinstalling the specific missing module or re-registering ASP.NET. Full IIS reinstall is a last resort.

How do I find which module is missing?

Check the error page in IIS Manager, or look at the web.config file’s modules and handlers sections. The error message usually names the module.

Is this error related to a 32-bit vs 64-bit issue?

Yes, it’s a common cause. Ensure your application pool’s “Enable 32-Bit Applications” setting matches the architecture of the module.

Will I lose my site configuration if I reinstall IIS?

Reinstalling IIS via Windows Features will preserve your configuration files (applicationHost.config) but may reset some defaults. Back up your configuration before doing this.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →