php_xsl.dll Not Found: Repair the PHP Setup Behind It

PHP Startup: Unable to load dynamic library 'php_xsl.dll' means PHP cannot load its XSL extension. If you see php_xsl.dll was not found, The specified module could not be found, or Class 'XSLTProcessor' not found, the cause is usually a PHP configuration, package, dependency, or build mismatch rather than a missing Windows system file.

Which fix applies to you

Use the first description that matches what you see:

As an Amazon Associate I earn from qualifying purchases.

• PHP runs, but XSLTProcessor is missing: XSL is probably disabled in the active php.ini.
• The error names the wrong folder or an old PHP path: PHP or Apache/IIS is loading a different installation than the one you edited.
• php_xsl.dll is absent from the PHP ext folder: the PHP package is incomplete. Reinstall or re-extract the matching PHP build.
• The DLL exists, but Windows says the module or procedure cannot be found: check dependent DLLs, the Visual C++ runtime, PHP architecture, version, and thread-safety mode.
• An antivirus product removed the file: inspect quarantine before restoring anything.
• The error comes from XAMPP, WAMP, MAMP, a CMS, or another bundled application: repair that product’s PHP installation, not an unrelated standalone PHP directory.
• Only an old application fails: do not replace its DLL with a current one. Use the PHP version and runtime expected by that application.

Do not begin by copying php_xsl.dll into C:WindowsSystem32. This file belongs to PHP and should normally remain beside the other PHP extensions.

What php_xsl.dll does

php_xsl.dll is the Windows PHP extension named XSL, supplied by The PHP Group. It enables PHP applications to perform XSLT transformations through the XSLTProcessor class and the libxslt library. PHP’s XSL extension also requires PHP’s libxml support.

The file is normally located here:

C:phpextphp_xsl.dll

The exact path may differ. For a bundled installation, it may be under a product directory such as an application’s PHP folder. The important point is that it belongs in the ext directory of the PHP installation that actually runs the failing application.

It is not:

• a Windows system component;
• a graphics, sound, or game driver;
• a COM or ActiveX library that normally needs registration;
• a general-purpose DLL shared by every PHP installation;
• a standalone redistributable downloaded separately from PHP.

The official PHP for Windows packages contain the matching extension files. Use the package for the same PHP release, architecture, compiler generation, and thread-safety mode as the PHP executable.

Start with the PHP installation that is actually running

Before changing files, identify the executable and configuration file in use.

Open Command Prompt and run:

where php
php --ini
php -v
php -i | findstr /I "PHP Version Architecture Thread Safety extension_dir libxslt"

Read the results carefully.

where php can show multiple PHP installations. The first one may be an old copy on PATH, while Apache, IIS, XAMPP, WAMP, or a scheduled task uses another copy.

php --ini reports the configuration file used by CLI PHP. Note the value beside:

Loaded Configuration File

Also note:

Scan for additional .ini files in

The php -i command reports the PHP version, architecture, thread-safety state, extension directory, and XSL-related information.

Then check whether the extension file exists in the reported extension directory:

dir "C:phpextphp_xsl.dll"

Replace C:phpext with the extension_dir shown on your computer.

If the error occurs through a website, CLI results may not describe the web server. Create a temporary PHP diagnostic page containing:

<?php phpinfo();

Open it through the affected site and check:

• Loaded Configuration File
• extension_dir
• PHP Version
• Architecture
• Thread Safety
• whether an XSL section appears

Remove the diagnostic page after testing. It exposes configuration details that should not remain publicly accessible.

Fix 1: Enable XSL in the correct php.ini

This is the most likely fix when PHP itself starts normally and php_xsl.dll is present.

Edit the configuration

1. Open the php.ini shown by php --ini, or the file shown as Loaded Configuration File in phpinfo().
2. Open it in Notepad as administrator if the PHP directory is protected.
3. Search for xsl.
4. If you find a commented line like this:

ini
;extension=xsl

remove the semicolon:

ini
extension=xsl

1. On older PHP configurations, the line may instead be:

ini
extension=php_xsl.dll

1. Confirm that extension_dir points to the correct ext directory:

ini
extension_dir = "C:phpext"

1. Save the file.

Current PHP configurations generally prefer the extension-name form, extension=xsl. Do not enable both forms unless you have a specific reason. Loading the same extension twice can create a duplicate-load warning.

Restart the process that runs PHP

For CLI PHP, close and reopen Command Prompt.

For Apache, restart the Apache service through its control panel or Services:

1. Press Win+R.
2. Enter services.msc.
3. Find the Apache service.
4. Right-click it and choose Restart.

For IIS:

1. Open IIS Manager.
2. Select the server in the left pane.
3. Choose Restart in the right pane, or restart the relevant application pool.
4. If PHP runs through FastCGI, recycle the application pool after changing php.ini.

For XAMPP, WAMP, MAMP, or another control panel, stop and start its Apache or PHP service from that product’s own interface.

Test from Command Prompt:

php -m | findstr /I "^xsl$"

A successful result includes:

xsl

If the website still fails, compare its phpinfo() output with the CLI output. They may be using different PHP executables or different php.ini files.

Fix 2: Correct a wrong extension_dir

A frequent mistake is editing the right-looking configuration file while PHP searches another directory.

Check the active value:

php -i | findstr /I "extension_dir"

Then check that the folder contains the extension:

dir "C:phpext"

You should see php_xsl.dll there.

In php.ini, use the full path when troubleshooting:

extension_dir = "C:phpext"
extension=xsl

Avoid relying on a relative path while diagnosing the problem. If the path contains spaces, keep the quotation marks.

Restart the relevant service and test again:

php -m

If the error still mentions a different directory, the failing process is not using the configuration you edited. Inspect the Apache PHP module, IIS FastCGI handler, application control panel, PATH, and phpinfo() output for the active PHP path.

Fix 3: Restore an incomplete PHP package

If php_xsl.dll is missing from the correct ext directory, do not obtain a replacement from a random DLL website.

Download the complete PHP for Windows package from the official PHP source, choosing a build that matches:

• the required PHP version;
• x64 or x86 architecture;
• Thread Safe or Non-Thread Safe mode;
• the compiler generation required by that release.

Extract it into a clean PHP directory, then configure the application to use that directory. Do not mix php_xsl.dll from one PHP release with php.exe, php-cgi.exe, or other extension DLLs from another.

Before replacing a bundled installation, back up its configuration and application data. If the error comes from XAMPP, WAMP, MAMP, a CMS package, or another application, use that product’s repair or reinstall process where available. Its PHP executable, extensions, configuration, and service settings are intended to work together.

After extraction, confirm:

dir "C:phpextphp_xsl.dll"
php -c "C:phpphp.ini" -m | findstr /I "^xsl$"

If the file exists but the command still fails, continue with the compatibility checks below.

Fix 4: Match x86, x64, TS, and NTS

A 64-bit Windows installation can run either 32-bit or 64-bit PHP. Match the PHP process, not merely the operating system.

Run:

php -i | findstr /I "Architecture Thread Safety"

Then compare the PHP executable with the extension package.

Architecture

• x86 PHP requires x86 extensions and the x86 Visual C++ runtime.
• x64 PHP requires x64 extensions and the x64 Visual C++ runtime.

A 32-bit PHP process cannot load a 64-bit php_xsl.dll, and a 64-bit process cannot load a 32-bit extension.

Thread safety

PHP Windows packages are commonly supplied as:

• Thread Safe (TS): generally used with Apache’s threaded module.
• Non-Thread Safe (NTS): generally used with IIS FastCGI and commonly used for CLI or FastCGI configurations.

Use extensions from the same TS or NTS build as the PHP executable. A file can have the correct name and still fail because it was built for the wrong PHP mode.

PHP version and compiler

The extension must match the PHP release and build characteristics. Do not copy an XSL DLL from a newer or older PHP folder simply because both files are named php_xsl.dll.

A loader message such as:

The specified procedure could not be found.

or:

The operating system cannot run %1.

often indicates a binary mismatch rather than a missing file.

Fix 5: Repair the Visual C++ dependency

PHP for Windows builds depend on Microsoft Visual C++ runtime files. Current PHP builds use the Microsoft Visual C++ Redistributable for Visual Studio 2015–2022, with the package matching the PHP architecture.

Install or repair the appropriate package from Microsoft’s official Visual C++ Redistributable page:

• x64 PHP requires the x64 redistributable.
• x86 PHP requires the x86 redistributable.

Older PHP releases can require older, release-specific runtimes. Installing the latest package is not a guaranteed fix for every legacy PHP build.

After installation:

1. Restart Windows or at least restart the affected PHP service.
2. Run:

bat
php -v
php -m

1. Test the application again.

If php.exe itself cannot start, the runtime problem affects PHP more broadly than XSL. If PHP starts but XSL alone fails, inspect the PHP package and extension compatibility as well.

Fix 6: Check antivirus quarantine

Security software can quarantine a legitimate PHP extension, but a detection should not automatically be dismissed as a false positive.

In Windows Security:

1. Open Start.
2. Type Windows Security and open it.
3. Select Virus & threat protection.
4. Choose Protection history.
5. Look for an event involving php_xsl.dll or the PHP directory.

Restore the file only when all of the following are true:

• PHP came from the official PHP source or a trusted application installer;
• the file is in the expected PHP ext directory;
• the surrounding PHP installation is intact;
• the detection is consistent with a mistaken quarantine rather than a modified package.

If the source is uncertain, do not restore the file. Remove the damaged installation and reinstall PHP from the official source. Then scan the new package before enabling it.

After restoration or reinstallation, check:

php -m | findstr /I "^xsl$"

Fix 7: Repair the application that bundles PHP

Many Windows programs carry their own PHP runtime. This includes development stacks, local web servers, CMS packages, and other server applications.

If the error appears only when launching one product:

1. Open Settings.
2. Select Apps.
3. Choose Installed apps.
4. Select the affected product.
5. Choose Advanced options if available.
6. Use Repair or Reset only after backing up application data.
7. If those options are unavailable, uninstall and reinstall the product from its official installer.

Do not edit C:php if the application actually uses a PHP folder inside its own installation. Confirm the path with the application’s configuration or with phpinfo().

A bundled PHP installation may intentionally use an older version for compatibility. Replacing only its php_xsl.dll with a file from standalone PHP can break other extensions and leave the application in a mixed, unsupported state.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 8: Investigate Windows component corruption only when evidence points there

php_xsl.dll is not a Windows system file, so SFC and DISM do not normally restore it. Use these commands when other Windows components are also failing or Windows itself reports corruption.

Open Start, type Command Prompt, right-click it, select Run as administrator, and run:

DISM.exe /Online /Cleanup-image /Restorehealth

Wait for it to finish. Then run:

sfc /scannow

Restart Windows and test PHP again.

These commands repair Windows components, not an incomplete PHP package. If php_xsl.dll is absent from the PHP ext folder, reinstall or re-extract PHP instead.

Repeatedly running SFC and DISM without checking which PHP installation is active usually does not solve this error. Outbyte PC Repair can show what is wrong before you repeat manual repair steps; its free scan identifies issues, while repair is performed by the full version.

Drivers and Windows Features are usually unrelated

php_xsl.dll is not a device driver. Reinstalling a graphics, chipset, printer, or network driver is not a normal solution, and enabling a random Windows Feature will not install PHP’s XSL extension.

Use Device Manager only if the same computer has a separate, clearly identified hardware problem:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant device category.
4. Right-click the device.
5. Select Update driver or Uninstall device only when the device itself is malfunctioning.
6. Restart Windows if prompted.

Do not expect this to restore php_xsl.dll. Outbyte Driver Updater can reduce the work of hunting through hardware vendors and stale driver versions; its free scan shows the detected issues, while driver installation is handled by the full version.

Do not use regsvr32 for this file

Do not run:

regsvr32 php_xsl.dll

PHP extensions are loaded by PHP through php.ini and extension_dir. They are not normally registered in the Windows registry as COM or ActiveX components.

regsvr32 can produce an error or give the impression that registration is the missing step. The correct repair is to make PHP load the matching extension from its own directory.

Verify the completed repair

Use the test that matches the failing environment.

CLI verification

php --ini
php -m | findstr /I "^xsl$"
php -i | findstr /I "PHP Version Architecture Thread Safety extension_dir libxslt"

Successful output includes xsl in the module list.

PHP script verification

Create a temporary file containing:

<?php
echo extension_loaded('xsl') ? "XSL loadedn" : "XSL not loadedn";
echo class_exists('XSLTProcessor') ? "XSLTProcessor availablen" : "XSLTProcessor unavailablen";

Run it with the same PHP binary used by the application:

php test-xsl.php

The expected output is:

XSL loaded
XSLTProcessor available

Delete the test file after use.

Web-server verification

Use phpinfo() through the affected site and confirm:

• the expected Loaded Configuration File;
• the expected extension_dir;
• the expected architecture and thread-safety mode;
• an XSL section.

If CLI succeeds but the site fails, correct the web server’s PHP handler rather than changing the working CLI installation.

Prevention

Keep each PHP installation self-contained and avoid copying individual extension DLLs between releases. Record which PHP executable, php.ini, architecture, and TS/NTS mode each application uses.

When upgrading PHP, replace the complete matching package and review the configuration instead of carrying DLLs forward manually. Keep bundled runtimes separate from standalone PHP. Finally, download PHP and its dependencies only from the official PHP or Microsoft sources, and treat any third-party replacement DLL as untrusted.

FAQ

Is php_xsl.dll a Windows file?

No. It is a PHP extension supplied by The PHP Group. It normally belongs in the ext directory of the PHP installation that runs the application.

Can I download php_xsl.dll by itself?

You should not use a random DLL download. Obtain the complete matching PHP package from the official PHP for Windows source, or repair the application that bundled PHP.

Why does the error say the module is missing when the file exists?

Windows may be reporting a missing dependency, an incompatible Visual C++ runtime, a wrong architecture, or a PHP build mismatch. The named DLL itself can be present while loading still fails.

Should I copy it to System32 or SysWOW64?

No. Copying a PHP extension into either Windows system directory is unsafe and normally ineffective. Set the correct extension_dir instead.

Do I need to enable XSL in Windows Features?

No. XSL is a PHP extension, not a Windows optional feature. Enable it in the active php.ini and restart PHP or the web server.

Why does php -m show XSL but my website still reports XSLTProcessor missing?

The command-line PHP and the web server are likely using different PHP installations or configuration files. Check phpinfo() and compare its loaded configuration path and extension directory with php --ini.

Does regsvr32 fix php_xsl.dll?

No. PHP loads this extension through its configuration. regsvr32 is not the normal repair.

What if the application requires an old PHP version?

Use the PHP release and dependencies required by that application. Do not mix a current php_xsl.dll with an older PHP executable, and recognize that old PHP releases may no longer receive support or use the same runtime requirements as current builds.

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.