php_pspell.dll Missing: Safe PHP and Aspell Fixes on Windows

php_pspell.dll is a PHP extension for spelling checks, not a Windows system file. If Windows reports that php_pspell.dll is missing or could not be loaded, the real problem may be the extension, its aspell-15.dll dependency, the active PHP configuration, or an incompatible PHP build.

Identify the file before repairing anything

Item	Correct identification
File	php_pspell.dll
Internal name	Pspell
Publisher	The PHP Group
Belongs to	A PHP installation
Normal location	PHP’s ext directory
Main dependency	aspell-15.dll
Required for Windows	No
Registered with regsvr32	No

Do not copy this file into C:WindowsSystem32 or C:WindowsSysWOW64. PHP loads extensions through php.ini; it does not normally load them as COM or ActiveX components.

As an Amazon Associate I earn from qualifying purchases.

Pspell provides spelling functions and suggestions. An Aspell dictionary is also needed for actual language checking. The extension can load successfully while dictionary-based functions still fail because no usable dictionary is installed.

The fastest fix: disable Pspell if you do not use it

Many PHP users encounter this warning after enabling an extension that their application never needs. If the application does not call functions such as pspell_new(), disabling Pspell is the cleanest repair.

A typical warning looks like this:

PHP Startup: Unable to load dynamic library '...php_pspell.dll' - The specified module could not be found.

Follow these steps:

1. Open Command Prompt.
2. Run:

php --ini

1. Note the path shown beside Loaded Configuration File.
2. Open that php.ini file in Notepad as administrator.
3. Search for:

extension=php_pspell.dll

1. Comment it out:

;extension=php_pspell.dll

1. Save the file.
2. Restart Apache, IIS, XAMPP, or the PHP service that runs your application.

If the configuration uses the shorter form, comment out this line instead:

;extension=pspell

For PHP 7.2 and later, both forms are supported, although extension=pspell is the preferred operating-system-independent form.

Test the result with:

php -m | findstr /I pspell

If nothing is returned and the startup warning has disappeared, Pspell is no longer being loaded. That is a successful repair when spell-checking is not required.

Why this fix often works

PHP’s command line and web server may use different PHP installations. You might disable Pspell in one php.ini while Apache or IIS continues loading another copy.

Check the web server’s PHP configuration separately. Create a temporary PHP diagnostic page containing:

<?php phpinfo();

Open it through the affected website and check:

• Loaded Configuration File
• Scan this dir for additional .ini files
• extension_dir
• PHP Version
• Architecture
• Thread Safety

Delete the diagnostic page after checking it because it exposes configuration details.

Find out whether the DLL or its dependency is missing

The message “specified module could not be found” does not prove that php_pspell.dll itself is absent. Windows can show the same message when a dependency required by that extension cannot be found.

First check the expected extension directory:

php -i | findstr /I extension_dir

Open the displayed directory in File Explorer and check whether php_pspell.dll is present.

Then check the PHP installation and environment:

php -i | findstr /I "PHP Version Architecture Thread Safety extension_dir Loaded Configuration File"

If the file exists, focus on these possibilities:

• aspell-15.dll is missing.
• Aspell’s directory is not on the PHP process’s PATH.
• The PHP extension does not match the PHP executable.
• Apache or IIS is using a different PHP installation.
• Antivirus software quarantined part of the installation.
• The PHP installation is incomplete or damaged.

Do not assume that replacing the visible DLL will solve the problem.

Repair Aspell and its PATH entry

Pspell uses the Aspell library underneath. On Windows, aspell-15.dll must be available through the process PATH, and an Aspell dictionary must be installed for real spell-checking.

Use a compatible Aspell Windows package from the project or package source used by your PHP installation. Avoid mixing random DLLs with a PHP installation.

After installing Aspell:

1. Locate the Aspell bin directory containing aspell-15.dll.
2. Press Windows and search for environment variables.
3. Select Edit the system environment variables.
4. In System Properties, select Environment Variables.
5. Under System variables, select Path.
6. Select Edit.
7. Select New.
8. Add the full path to Aspell’s bin directory.
9. Select OK on each dialog.
10. Restart Apache, IIS, XAMPP, or the relevant PHP service.

A service started before the PATH change will not necessarily inherit the new value.

For a quick check in a new Command Prompt, run:

where aspell-15.dll

If Windows finds the file, the PATH entry is visible to that command session. It does not prove that a service account has the same environment, so restart the service and test the affected application as well.

If Pspell loads but pspell_new() still cannot create a spelling checker, install a dictionary compatible with the Aspell installation and confirm that the requested language is available.

Check the PHP version and extension build

A PHP extension must match the PHP process that loads it. Confirm all of the following:

• PHP major and minor version
• x86 or x64 architecture
• Thread Safe or Non-Thread Safe build
• Compiler generation
• Debug or non-debug build

Run:

php -i | findstr /I "PHP Version Architecture Thread Safety Compiler Debug Build"

The extension must match the PHP executable, not merely the Windows edition.

For example, a 32-bit extension will not load into a 64-bit PHP process, and a 64-bit extension will not load into 32-bit PHP. Apache loaded as a module generally requires a Thread Safe PHP build. IIS with FastCGI normally uses a Non-Thread Safe build.

If the error says “The specified procedure could not be found,” “invalid Win32 application,” or a similar loader error, an incompatible build is a strong possibility.

The safe repair is to obtain the matching extension from the same PHP distribution or build it for the exact PHP configuration. Do not take php_pspell.dll from another PHP version simply because the filename is identical.

Check the PHP extension directory:

php -i | findstr /I extension_dir

Then confirm that php.ini points to that directory:

extension_dir = "C:pathtophpext"

Use the actual path reported by your PHP installation. There is no universal PHP or XAMPP directory.

Understand the PHP 8.4 change

Pspell was bundled with PHP builds before PHP 8.4 when PHP was built with Pspell support. Beginning with PHP 8.4, Pspell moved to PECL and is no longer bundled with PHP itself.

This means an older configuration containing:

extension=php_pspell.dll

may continue to be present after a PHP upgrade even though the new PHP installation does not contain that file.

If the application does not use Pspell, comment out the directive and restart the service.

If the application does require Pspell, verify that a package or build exists for the exact PHP version, architecture, compiler generation, and TS/NTS mode. Do not assume that a source package automatically provides a ready-to-use Windows DLL for every current PHP build.

After installing a matching extension, enable it in the active php.ini:

extension=pspell

Then restart the PHP host and test:

php -m | findstr /I pspell

A successful result lists pspell. You can also test the function:

php -r "var_dump(function_exists('pspell_new'));"

bool(true) confirms that PHP exposes the function. It does not by itself prove that a dictionary is installed.

Install the required Microsoft runtime

Current PHP Windows builds require the appropriate Microsoft Visual C++ Redistributable. The architecture must match PHP, not necessarily the architecture of Windows.

Check PHP’s architecture:

php -i | findstr /I Architecture

Then install the corresponding Microsoft Visual C++ Redistributable from Microsoft’s official download page. A 32-bit PHP process requires the x86 runtime even on 64-bit Windows.

Restart the PHP service after installing the runtime and test again:

php -m | findstr /I pspell

If the extension still fails, return to the PHP version, architecture, TS/NTS, and Aspell checks. Installing the runtime cannot correct an extension built for the wrong PHP configuration.

Repair a damaged PHP, XAMPP, or hosting installation

If php_pspell.dll was deleted, the PHP directory contains mixed files, or an upgrade was interrupted, repair the complete PHP package.

1. Back up the application files, virtual-host configuration, and php.ini.
2. Check the antivirus quarantine.
3. Download the correct PHP package from the official PHP distribution or use the repair procedure supplied by your PHP package vendor.
4. Match the package to the existing PHP version, architecture, and TS/NTS requirements.
5. Replace or reinstall the complete PHP installation rather than one unexplained DLL.
6. Restore only verified configuration changes.
7. Confirm extension_dir.
8. Restart the web server or PHP service.
9. Run the diagnostic commands again.

For older PHP installations, use the corresponding official release archive rather than combining files from different releases.

If the application is bundled with XAMPP, Plesk, or another control panel, check which PHP executable that product actually uses. Replacing a standalone PHP directory may have no effect if the service points elsewhere.

Check antivirus quarantine

Security software can quarantine a PHP extension or an Aspell dependency. This is especially likely when the file was recently restored, updated, or copied into a new PHP directory.

Open your security product and inspect:

1. Protection history, Quarantine, or the equivalent section.
2. Entries for php_pspell.dll, aspell-15.dll, or the PHP directory.
3. The file path and detection details.
4. Whether the file belongs to the expected PHP installation.

Restore a file only after confirming its source and scanning the installation. Then repair or reinstall PHP from an official source and run a full security scan. Do not download a replacement from a random DLL website.

Repair Windows components only when Windows has broader problems

php_pspell.dll is not a Windows component, so SFC and DISM will not normally restore it. Use them when Windows itself has broader symptoms, such as damaged built-in applications, update failures, corrupted system files, or repeated servicing errors.

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

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

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

sfc /scannow

1. Restart Windows.
2. Test PHP again.

Outbyte PC Repair can reduce the manual work of repeating SFC and DISM while trying to identify which Windows components are damaged; its free scan shows the reported issues, while repair features require the full version. It is optional, and reinstalling the correct PHP and Aspell packages remains the definitive fix for this extension.

If SFC reports that it repaired files but the PHP warning remains, continue with the PHP-specific checks. Windows repair tools do not install php_pspell.dll or aspell-15.dll.

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

Drivers, Windows Features, and Device Manager

A graphics, printer, chipset, or network driver does not provide php_pspell.dll. Updating a driver is not a normal solution for a PHP extension startup warning.

Likewise, enabling a random item in Turn Windows features on or off will not install Pspell. PHP, Aspell, and their dictionaries must be installed separately.

If the PHP application also has an unrelated hardware error, update that device separately:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if prompted.

Outbyte Driver Updater can show which drivers are stale instead of making you inspect many devices manually; its free scan identifies updates, while driver installation features require the full version. It is not a substitute for matching PHP, Aspell, or the correct php.ini.

What not to do

Do not copy the file into System32

System32 and SysWOW64 are not general-purpose storage locations for application DLLs. Copying php_pspell.dll there can create conflicts and still will not provide the missing Aspell dependency.

Keep the extension in the PHP installation’s ext directory.

Do not run regsvr32

Do not use:

regsvr32 php_pspell.dll

PHP extensions are loaded by PHP through php.ini. They are not normally registered with Windows as COM or ActiveX components. regsvr32 will not repair a missing aspell-15.dll, an incorrect PATH, or a mismatched PHP build.

Do not download a replacement from a DLL website

Random DLL download sites can provide malware, the wrong PHP version, the wrong architecture, or an unrelated build. Even a genuine-looking file may not fix the dependency or configuration problem.

Use the PHP distribution or package vendor, the appropriate Aspell source, and Microsoft for the Visual C++ runtime. Restore quarantined files only after verifying their origin.

Do not keep adding duplicate extension lines

Multiple entries such as these can produce confusing startup behavior:

extension=pspell
extension=php_pspell.dll

Use one appropriate directive in the active configuration, and remove or comment out duplicate entries.

Verify the final repair

Run these commands with the same PHP executable used by the affected service:

php --ini
php -i | findstr /I "PHP Version Architecture Thread Safety extension_dir Loaded Configuration File"
php -m | findstr /I pspell
php -r "var_dump(function_exists('pspell_new'));"

A successful repair normally shows:

• The expected php.ini path.
• The expected PHP version and architecture.
• The correct extension_dir.
• pspell listed in the loaded modules.
• bool(true) for function_exists('pspell_new').

If the command-line test succeeds but the website still fails, the web server is using a different PHP executable, configuration file, PATH, or service account. Check the web server’s phpinfo() output and restart the service after every configuration or environment change.

FAQ

Is php_pspell.dll safe?

It is a legitimate PHP extension associated with the PHP Group when it comes from the expected PHP installation. Its name alone does not prove that a file is safe or malicious. Check the location, source, antivirus history, and PHP package before restoring it.

Is it part of Windows?

No. Windows does not supply php_pspell.dll, and it should not be placed in a Windows system directory.

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

The loader may be unable to find aspell-15.dll or another dependency. An incompatible architecture or PHP build can also prevent loading.

Do I need Pspell?

Only if the application uses PHP spelling functions. If it does not, comment out the Pspell extension in the active php.ini and restart the PHP host.

Can PHP 8.4 load the old bundled DLL?

Not automatically. Pspell moved out of the bundled PHP distribution in PHP 8.4 and became a PECL extension. Verify a compatible build before enabling it.

Why does CLI PHP work while Apache or IIS fails?

They may use different PHP installations, php.ini files, PATH values, or architectures. Compare php --ini with the web server’s phpinfo() output.

Will reinstalling Windows fix this error?

Usually not. This is normally a PHP or Aspell installation problem. Repair Windows with DISM and SFC only when there are separate signs of Windows system corruption.

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.