shtml.dll Missing on Windows 11 and 10: Safe Repair Steps

“shtml.dll is missing from your computer,” “shtml.dll was not found,” and “The code execution cannot proceed because shtml.dll was not found” all point to a missing or unusable legacy component. shtml.dll is the Microsoft FrontPage Server Extensions SmartHTML Interpreter, normally used by FrontPage-powered IIS websites rather than by Windows itself.

The 60-second answer

Do not download shtml.dll from a DLL website and do not copy it into System32.

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$124.97	Buy on Amazon
2		Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |...	$119.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

The file belongs to Microsoft FrontPage Server Extensions, also used by Microsoft SharePoint Team Services. On an IIS server, it is commonly associated with this website path:

/_vti_bin/shtml.dll

The safest repair is to identify which old FrontPage, FrontPage Server Extensions, SharePoint Team Services, or IIS website installation requested the file, then repair or reinstall that matching component. If the website no longer uses FrontPage Server Extensions, removing the obsolete dependency and migrating the site is usually safer than restoring it.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$124.97

Buy on Amazon

A local application may show a standard Windows loader error. An IIS site may instead return a FrontPage or HTTP error, including:

Cannot run the FrontPage Server Extensions on this page:""

Microsoft documents shtml.dll as part of FrontPage Server Extensions and as an ISAPI entry point for FrontPage dynamic content, including forms and other WebBot features. It is not a general-purpose Windows runtime library.

What is shtml.dll?

shtml.dll is a Microsoft application component with the description or internal name “Microsoft FrontPage Server Extensions.” Its historical role was to process dynamic FrontPage content on a web server.

It was associated with:

• Microsoft FrontPage 2000 and 2002 server functionality
• FrontPage Server Extensions 2000 and 2002
• Microsoft SharePoint Team Services 2002
• IIS installations on older Windows versions
• FrontPage website features such as forms, search, and WebBot components

Microsoft identifies the file as an ISAPI DLL. ISAPI extensions are loaded by Internet Information Services, so the file is normally part of a particular website’s server configuration rather than a Windows operating-system component.

Why is it usually under _vti_bin?

FrontPage Server Extensions placed executable website components in a special directory named _vti_bin. A typical IIS request looked like this:

the official source

That location is different from the normal locations for Windows runtime libraries:

C:WindowsSystem32
C:WindowsSysWOW64

If you find shtml.dll beneath a website directory or an _vti_bin folder, that strongly supports an FPSE or SharePoint-related origin. A copy found in System32 or an unrelated application folder should not automatically be trusted.

shtml.dll is not normally part of Windows 10 or Windows 11. Microsoft did provide legacy FPSE packages for certain older IIS 7 systems, including separate x86 and x64 packages, but those were optional legacy server components rather than current Windows redistributables.

First determine what is actually failing

Before repairing anything, establish whether this is a desktop application problem or an IIS website problem.

If a local program shows the error

Record:

1. The exact wording of the message.
2. The program name in the title bar.
3. The full path, if the message or Event Viewer provides one.
4. Whether the error started after uninstalling FrontPage, Office-era software, IIS, or a backup.
5. Whether antivirus software recently quarantined a file.

A normal desktop game or application should not generally need shtml.dll. If a local program requests it, that program may contain an old web-authoring, server-management, or FrontPage dependency. Repair or reinstall that specific program instead of treating the file as a Windows component.

If an IIS website returns the error

Check whether the affected site still contains FrontPage metadata or references _vti_bin. The problem may be caused by:

• FrontPage Server Extensions being removed
• An incomplete IIS upgrade
• A broken ISAPI mapping
• A missing website extension
• An application-pool architecture mismatch
• Permissions or dependency problems
• A site that still contains old FrontPage references but no longer has a functional FPSE installation

This is a server-side issue, even if the error appears in a web browser.

Identify the file and its owning product

Do not replace the file until you know which installation owns it.

1. Search for existing copies

Open Command Prompt and run:

where /r C: shtml.dll

This searches the C: drive recursively. If you have additional disks containing websites or application files, search those locations separately.

Pay attention to the full path. A path similar to this is relevant:

C:Inetpubwwwroot_vti_binshtml.dll

A random copy in a temporary folder is not evidence that it is the correct replacement.

2. Check file properties

Right-click the file, select Properties, and open the Details tab. Record:

• Company
• Product name
• File description
• Version
• Digital-signature status

Then open the Digital Signatures tab if it exists. A missing signature does not by itself prove that the file is malicious because old software and copied website files can have different signing states, but an unexpected company or location is a reason to stop and investigate.

3. Check IIS configuration

On the server:

1. Press Windows key, type IIS, and open Internet Information Services (IIS) Manager.
2. Expand the server and Sites.
3. Select the affected website.
4. Check Basic Settings to confirm the site’s physical path.
5. Inspect that path for _vti_bin.
6. Open Handler Mappings and ISAPI and CGI Restrictions where available.
7. Look for an old FrontPage or ISAPI mapping referring to shtml.dll.

Do not create a new mapping by guessing. FPSE normally installs the required files, permissions, mappings, and website metadata together.

Fix 1: Repair or reinstall the matching FrontPage component

This is the most likely solution when an IIS website or FrontPage project still depends on shtml.dll.

The exact repair method depends on what is installed.

Repair an installed Microsoft application

1. Press Windows key + R.
2. Type:

text
appwiz.cpl

1. Press Enter.
2. Find the relevant Microsoft FrontPage, Office-era product, SharePoint Team Services installation, or other product that owns the website.
3. Select it and choose Change.
4. Choose Repair, if the option is available.
5. Follow the prompts and restart the computer or server if requested.

Use the original installation media if the repair wizard asks for a source. Do not point the wizard at a random copy of shtml.dll.

After repair, test the website again. If the site still fails, the website may need to be re-extended with the matching FPSE release. Microsoft’s IIS documentation describes legacy FPSE installation and website extension using the appropriate administration procedure or owsadm.exe.

Reinstall the correct FPSE release

If repair is unavailable:

1. Identify whether the old installation used FPSE 2000, FPSE 2002, or SharePoint Team Services.
2. Identify whether the system and IIS application require x86 or x64 components.
3. Obtain the installation package from the original licensed software media or the relevant official Microsoft documentation and administration process.
4. Back up the website files, configuration, and content before changing IIS.
5. Install the matching component.
6. Re-extend the affected IIS website.
7. Test the _vti_bin endpoint from a controlled network location.

Do not mix files from FPSE 2000, FPSE 2002, and SharePoint Team Services. These products and their updates are not interchangeable merely because they use the same filename.

How to tell whether this fix worked

The repair succeeded if:

• The original program starts without the loader message.
• The IIS site no longer reports a missing FrontPage extension.
• FrontPage forms or other required dynamic features work as expected.
• Event Viewer and IIS logs stop recording the same load failure.

If the file exists but IIS still cannot load it, the problem may be permissions, a missing dependency, an incorrect ISAPI mapping, or application-pool bitness rather than a missing file.

Fix 2: Remove the obsolete dependency and migrate the site

FrontPage Server Extensions are obsolete. If the website no longer needs FrontPage forms, search, WebBot components, or publishing features, restoring FPSE may create more risk and maintenance work than it solves.

Before removing anything:

1. Make a complete backup of the site and IIS configuration.
2. Search the website for _vti_bin, FrontPage metadata, and forms that depend on server extensions.
3. Identify any publishing or administrative workflow still using FPSE.
4. Test a copy of the site on a supported platform.
5. Replace FrontPage-specific forms and components with supported application code or hosting features.
6. Remove the obsolete IIS mapping only after the replacement works.
7. Confirm that the public site does not still request _vti_bin/shtml.dll.

Microsoft has advised removing FrontPage Server Extensions when they are not needed because of their age and security exposure. Do not expose a restored FPSE installation to the public Internet without a deliberate security review and a plan to migrate it.

This is often the correct solution when the error began after a Windows or IIS upgrade and the old website is no longer actively maintained.

Fix 3: Check antivirus quarantine

Security software may quarantine an old server extension, especially on a machine where the file is exposed through IIS.

Rank #2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

• STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
• OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
• OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
• PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
• GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

Buy on Amazon

1. Open Windows Security.
2. Select Virus & threat protection.
3. Choose Protection history.
4. Review detections involving shtml.dll, the website directory, or FrontPage Server Extensions.
5. Check the security product’s quarantine and event history if you use another antivirus product.
6. Compare the quarantined file’s path with the known FPSE installation.
7. Verify the owning product and signature before considering restoration.

Restore the file only when you have confirmed that it belongs to a known installation and that the surrounding FPSE files and configuration are intact. Then update the security product and run a full scan.

Do not disable antivirus simply to force an old Internet-facing component to run. If security software repeatedly detects the component, treat that as a reason to migrate or isolate the website, not as a reason to add a permanent exclusion.

Fix 4: Recheck the IIS upgrade and architecture

An upgrade can leave old FrontPage services disabled or partially configured. Microsoft documents upgrade issues involving old FPSE installations and notes that separate legacy packages were required for some IIS 7 systems.

Check the following:

• Windows version and server role
• IIS version
• FPSE release
• Whether the installation is x86 or x64
• Application-pool Enable 32-Bit Applications setting
• Website physical path
• ISAPI restrictions
• File and directory permissions
• IIS and Event Viewer logs

To check application-pool bitness:

1. Open IIS Manager.
2. Select Application Pools.
3. Select the pool used by the website.
4. Choose Advanced Settings.
5. Find Enable 32-Bit Applications.
6. Confirm that the setting matches the legacy component you installed.

Do not change this setting repeatedly on a production server without testing. A bitness change can affect other applications using the same pool. If necessary, place the legacy site in its own application pool.

The x86 and x64 FPSE packages are not interchangeable. Installing an x64 component does not repair an x86 application requirement, and copying an x86 DLL into a 64-bit system directory is not a valid conversion.

Fix 5: Repair Windows components only when Windows corruption is plausible

shtml.dll is primarily an FPSE application component, so SFC and DISM are not guaranteed to restore it. Use these commands when you also have evidence of broader Windows component corruption, damaged protected files, or failures affecting several Windows features.

Open Windows Terminal (Admin) or Command Prompt (Admin):

1. Right-click Start.
2. Select Terminal (Admin).
3. Run:

cmd
DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. Then run:

cmd
sfc /scannow

1. Restart Windows.
2. Test the application or IIS site again.

Microsoft recommends running DISM before SFC. DISM repairs the Windows component store, while SFC checks protected Windows files against that store.

Success means DISM completes without an unrepaired error and SFC reports that it repaired corrupt files or found no integrity violations. If SFC reports that it could not fix some files, review the CBS log and continue investigating the owning FPSE product. Do not assume that repeated SFC runs will recreate an application DLL that was never part of that Windows installation.

Manually running these commands and interpreting their logs can be time-consuming, especially when several components are damaged. Outbyte PC Repair can scan for problems and show what it found, while its repair functions require the full version; it is optional, and repairing or reinstalling the specific FPSE product remains the definitive fix for an application-owned shtml.dll.

Fix 6: Use System Restore only for a recent, known change

System Restore may help if the file disappeared immediately after a known installation or upgrade change and a suitable restore point exists.

1. Press Windows key and search for Create a restore point.
2. Open it.
3. Select System Restore.
4. Choose a restore point created before the problem began.
5. Review the affected programs.
6. Start the restore and restart Windows.

System Restore is a rollback mechanism, not a preferred way to deploy FrontPage Server Extensions. It can remove applications, drivers, and updates installed after the restore point. Back up current work first, and do not use it on a server without understanding the operational impact.

Is regsvr32 the right fix?

Usually, no.

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer, commonly COM or ActiveX components. shtml.dll is an IIS ISAPI extension installed as part of FrontPage Server Extensions. Its operation depends on the surrounding FPSE files, IIS configuration, website metadata, permissions, and the correct architecture.

Running a command such as this is therefore not a general repair:

regsvr32 shtml.dll

It may produce an entry-point error, or it may change nothing. Do not use regsvr32 unless the owning product’s official installation instructions specifically require it.

Why copying or downloading shtml.dll is unsafe

A standalone replacement can have:

• The wrong FPSE release
• The wrong x86 or x64 architecture
• Missing companion files
• Incorrect permissions
• Incompatible exports or dependencies
• An unsafe or modified source
• No corresponding IIS mapping or website metadata

Random DLL download websites also create a malware risk and often leave the original installation problem unresolved. Do not download shtml.dll from those sites, copy it from another computer, or place it in System32 or SysWOW64.

Use the original product media, an intact backup of the same installation, or the relevant official Microsoft installation documentation. Before restoring any backup, verify the product, path, architecture, and security status.

What if the file is present but still will not load?

A present file can still fail because:

• IIS cannot access the directory
• The application pool uses the wrong bitness
• The ISAPI mapping is missing or incorrect
• A required companion file is missing
• The file is blocked or quarantined
• Website permissions are damaged
• The old FPSE installation is incomplete
• The application is requesting a different release

Check the full path in IIS logs and Event Viewer. Record the website name, application pool, Windows version, FPSE release, architecture, and exact error code. Avoid replacing files until those details identify the actual failure.

Do drivers or Windows Features fix this?

Drivers are not a normal cause of an shtml.dll error. Device Manager cannot repair an IIS ISAPI extension.

If the error appeared alongside broader hardware or Windows instability, check Device Manager:

1. Right-click Start.
2. Select Device Manager.
3. Expand categories with warning icons.
4. Right-click a relevant device.
5. Select Update driver or Uninstall device, then restart if appropriate.

This is a separate diagnostic step, not a replacement for repairing FPSE.

Manually checking many devices and finding the correct driver versions can be tedious. Outbyte Driver Updater can scan and identify driver issues, while installing drivers requires the full version; it is optional and is not expected to repair an IIS-owned shtml.dll dependency.

Windows Features are relevant only when you are deliberately configuring an IIS server. Open Turn Windows features on or off and inspect Internet Information Services, but do not enable random legacy features hoping they will create the file. Installing IIS alone does not recreate a complete FrontPage Server Extensions installation.

Frequently asked questions

Is shtml.dll a Windows 10 or Windows 11 system file?

No. It is primarily a legacy Microsoft FrontPage Server Extensions component. A current Windows installation should not be assumed to contain it.

Does shtml.dll belong only to FrontPage 2000?

No. It was associated with FrontPage Server Extensions 2000 and 2002 and was also used by Microsoft SharePoint Team Services. Identify the installed product before choosing a repair package.

Should I put shtml.dll in System32?

No. Its expected IIS location is commonly under a website’s _vti_bin directory. Copying it into a Windows system directory can create a second, misleading problem.

Why does a browser show the error instead of a program?

The browser may be displaying an IIS or FrontPage Server Extensions failure. The browser is only the client; the missing or unusable component is on the web server.

Can SFC restore shtml.dll?

Only if that particular file is a protected Windows component on the affected installation. SFC does not generally reinstall FrontPage Server Extensions.

What should I do if the site no longer needs FrontPage?

Back up the site, remove FrontPage-specific dependencies, migrate the forms and publishing workflow, and remove the obsolete server extension. This is generally safer than restoring an old Internet-facing service solely to eliminate the message.

What information should I provide to an administrator?

Provide the full file path, requesting process or IIS site, Windows version, FPSE or SharePoint version, application-pool bitness, antivirus history, and relevant IIS and Event Viewer entries. That information distinguishes a missing file from a broken mapping, permission problem, quarantine event, or obsolete dependency.

Quick Recap

SaleBestseller No. 1

Microsoft Windows 11 (USB)

Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation

$124.97

Bestseller No. 2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

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.