What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The WordPress message “Installation failed: Destination folder already exists” means the installer found a non-empty directory with the same name as the plugin or theme you are uploading. It is a filesystem collision, not proof that the package is broken.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Read the full path in the error, check whether the plugin or theme is already listed in WordPress, and make a backup before changing files. If it is listed, activate, update, or use WordPress’s replacement option. If it is not listed, remove only the matching orphan directory under wp-content/plugins/ or wp-content/themes/, then install again.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the error means
WordPress installs packages into predictable directories. A plugin normally goes under wp-content/plugins/; a theme normally goes under wp-content/themes/. The final directory name is usually the package slug, such as wpbenchmark.
During installation, WordPress core’s WP_Upgrader::install_package() uses abort_if_destination_exists with a default value of true. When the destination directory already exists and contains files, the upgrader stops and returns the folder_exists error. That is what the dashboard displays as “Destination folder already exists.” The lower-level move_dir() operation has a corresponding destination_already_exists_move_dir result when a destination exists and overwriting is disabled.
In practical terms, one of three things is usually true:
- The plugin or theme is already installed, so reinstalling is unnecessary.
- An earlier installation or update stopped partway through and left its directory behind.
- WordPress removed the database or plugin listing but could not remove the directory itself.
The message does not tell you that the code is unusable. It only tells you that WordPress will not overwrite an existing, non-empty destination through the ordinary installation path.
Check these things before deleting a folder
- Read the complete path in the error. Note the directory name and whether the path contains
wp-content/plugins/orwp-content/themes/. That name is the folder you must investigate; do not guess from the product’s marketing name. - Open the relevant WordPress list. For a plugin, go to Plugins. For a theme, go to Appearance → Themes. Search for the item by name and inspect whether it is active, inactive, or awaiting an update.
- Create a backup or host snapshot. Save a current backup before deleting or replacing a directory. If your host provides a snapshot, take one; otherwise make a file and database backup using your normal backup process.
- Decide what you are trying to accomplish. Activation, a normal update, a clean reinstall, and replacement of damaged files are different jobs. The safest action depends on that goal.
- Confirm that you have a way back. You may need SFTP, FTP, cPanel File Manager, or another host file console. If you cannot access the directory, plan to ask the host rather than repeatedly retrying the dashboard upload.
Choose the remedy that matches your situation
| What you find | Your goal | Safest next action |
|---|---|---|
| The plugin is listed and appears healthy | Use it on the site | Activate it; do not reinstall. |
| The plugin is listed and an update is available | Update it | Use the normal update control, or use the replacement upload if WordPress offers it. |
| The plugin is not listed, but its matching folder exists | Clean reinstall | Back up, remove only that orphan directory, and install again. |
| The theme is listed | Keep or replace the theme | Activate or update it. Do not delete a theme merely because its directory exists. |
| The item is not listed and the directory cannot be removed | Any reinstall or replacement | Use the host’s file manager or request FTP/SFTP or file-removal help. |
| You have an installed plugin and the upload screen shows an overwrite choice | Replace its files | Choose Replace current with uploaded after confirming the package and keeping a backup. |
If the plugin or theme is already listed
Activate instead of reinstalling
If the plugin appears under Plugins, the existing directory is doing exactly what WordPress expects. Select Activate rather than uploading the package again. An installed plugin does not need a second copy in the same destination.
If activation produces a separate error, stop treating the folder-exists message as the cause. Record the new error and troubleshoot that issue independently. Deleting the directory while WordPress still recognizes the plugin can turn a recoverable activation problem into a missing-code problem.
Use the normal update control
When WordPress shows an update notification for the plugin or theme, use its built-in update action. That path is designed to replace the existing package while preserving the installation’s expected directory structure. Take the backup first, particularly on a production site.
Use the replacement upload when WordPress offers it
For a recognized installed plugin, the plugin installer can detect the folder_exists condition and present an overwrite action labeled Replace current with uploaded. Choose that option only when the uploaded package is the one you intend to use and you have a recoverable backup. This is preferable to manually deleting a working installation when your goal is simply to replace its files.
Recommended Free Tools
Be careful with themes
Apply the same logic under wp-content/themes/. A theme directory existing is normal. If it is listed, activate or update it instead of deleting it. Never remove the active theme as a first response: the site needs an available theme to render the front end and administrator screens. If you intend to replace an active theme, switch to another installed theme first and confirm that you have a copy of any custom changes.
Remove an orphan plugin directory
Use this procedure when the plugin is not listed in WordPress, the error path points to wp-content/plugins/, and you have confirmed that the directory is an abandoned or incomplete installation.
Rank #3
- Copy the directory before removal. Download it or duplicate it in the file manager. This gives you a chance to recover custom files or inspect what the failed installation left behind.
- Open the plugins directory. In SFTP, FTP, cPanel File Manager, or your host’s web file console, navigate to
wp-content/plugins/. - Match the exact folder name. If the error identifies
wpbenchmark, the expected location is/wp-content/plugins/wpbenchmark. Do not delete similarly named directories, the entirepluginsdirectory, or unrelated folders. - Inspect before deleting. Confirm that the directory name matches the slug in the error and that the plugin is not listed in the dashboard. If you see custom files or are unsure whether the folder is still used, stop and ask your host or developer.
- Delete only the matching orphan directory. Remove that directory and its contents after the backup. Do not use a broad wildcard or bulk-delete operation.
- Retry the installation. In WordPress, go to Plugins → Add New, upload or select the package, and run the installation again.
- Verify the result. Return to Plugins. The plugin should appear once, with no second folder created under a different name. Activate it only after checking that the installation completed.
Remove an orphan theme directory
The theme process is the same, but the location changes to wp-content/themes/.
- Read the exact theme slug from the error path.
- Back up the site and copy the existing theme directory before changing it.
- Open
wp-content/themes/with SFTP, FTP, cPanel File Manager, or the host’s file console. - Confirm that the directory matches the error and that the theme is not listed under Appearance → Themes.
- Delete only that orphan directory.
- Return to Appearance → Themes, choose Add New, and upload or install the theme package again.
- Activate the replacement only after checking the site and confirming that the intended theme is present.
If the directory belongs to the active theme, do not follow the deletion steps. Switch to a safe alternative first, or use a controlled replacement method with a backup.
Install manually when the dashboard still fails
A manual upload is useful when the dashboard installer continues to collide with a directory, when the package is supplied as a ZIP, or when you need to replace files directly.
- Obtain the package from its official source. Use the release that matches the plugin or theme you intend to run.
- Unzip it on your computer. The extracted top-level directory should be the expected slug. Avoid uploading a folder that contains another copy nested inside it, such as
plugin-name/plugin-name/. - Back up the existing site and directory. If an orphan or damaged directory is present, copy it before replacement.
- Upload to the correct parent directory. Put the plugin directory directly in
wp-content/plugins/or the theme directory directly inwp-content/themes/. - Replace only the intended directory. Remove or rename the old matching directory after the backup, then upload the extracted directory with the expected name.
- Check permissions and completeness. Let the transfer finish and confirm that the main plugin or theme files are present. An interrupted upload can recreate the same problem or leave a package that appears installed but is incomplete.
- Return to the dashboard. Refresh Plugins or Appearance → Themes. WordPress should discover the directory and allow activation.
Manual replacement changes files but does not automatically prove that the package is compatible with your WordPress version, PHP version, or other extensions. If the item appears but fails on activation, investigate that separate compatibility or configuration error rather than deleting folders repeatedly.
When the item disappeared from WordPress but the folder remains
This pattern often follows a failed update, a timeout, or cleanup that removed the database listing without removing every file. WordPress then sees a physical directory during the next installation attempt, even though the administrator screen looks as if the plugin or theme is absent.
Treat the directory as potentially valuable until you confirm it is orphaned. Copy it first, compare its name with the error path, and check the administrator list again. Once the backup exists and the item is genuinely absent, remove only that matching directory and retry the installation. Do not delete the entire plugins or themes directory to make the message disappear.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What to do when deletion or replacement fails
The file manager refuses to delete the directory
Do not keep retrying from the WordPress dashboard; the dashboard cannot remove a directory that the hosting account cannot modify. Use the host’s cPanel or web file manager, connect with FTP/SFTP, or ask support to remove the specific path. Give support the complete directory path and explain that you want only the matching orphan folder removed.
You cannot identify the right folder
Use the full path shown in the error, not a shortened plugin name. Slugs can differ from display names, and similarly named folders may belong to different packages. If the path is unclear, ask the host or the package publisher before deleting anything.
The upload creates a nested directory
WordPress expects the package’s plugin or theme directory directly under its parent. If you upload an extra wrapper folder, the files may end up one level too deep and the dashboard may not recognize them. Recheck the extracted ZIP structure and place the directory containing the main package files directly under wp-content/plugins/ or wp-content/themes/.
The theme is active or the plugin is still in use
Do not remove code that the site is currently using without a recovery plan. For a theme, switch themes before replacement. For a plugin, deactivate it through WordPress when possible and keep the backup directory. If the dashboard is inaccessible, request host assistance rather than making broad filesystem changes.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchConfirm that the fix worked
- The original error path no longer points to a leftover directory.
- The plugin appears once under Plugins, or the theme appears under Appearance → Themes.
- The package files are directly inside the expected slug directory.
- Activation or update completes without a new filesystem error.
- The site’s front end and administrator screens load as expected.
- Your backup or copied directory is retained until you are satisfied that the replacement works.
Prevent the collision next time
- Keep a current backup or host snapshot before updates and manual replacements.
- When WordPress lists a plugin or theme, activate or update that existing installation instead of uploading a duplicate.
- After an interrupted install, inspect the exact destination path before starting another attempt.
- Use the overwrite or replacement flow when WordPress recognizes an installed plugin.
- Keep FTP/SFTP or host file-manager access available for cases the dashboard cannot clean up.
- Preserve the package’s expected directory name and avoid nested extraction folders.
The reliable sequence is simple: identify the exact destination, check the WordPress list, back up, and then choose activation, replacement, or targeted orphan-folder removal. That prevents a harmless directory collision from becoming an unnecessary outage.
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.
