To install a particular WordPress core release instead of the newest one, run wp core update --version=<version> from the site’s WordPress directory. If the requested release is older than the version already installed, add --force: wp core update --version=<version> --force. Back up both the database and site files first, confirm that your plugins and theme can run on the target release, and test the site immediately afterward.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What updating to a specific version means
This procedure changes WordPress core: the files and database code that make up WordPress itself. It does not update plugins or themes. Those components have separate WP-CLI commands and separate compatibility risks.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress Multisite Administration | $34.38 | Buy on Amazon |
| 2 |
|
Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition) | $9.90 | Buy on Amazon |
| 3 |
|
WordPress 24-Hour Trainer | $3.95 | Buy on Amazon |
| 4 |
|
Teacher Record Book | $4.89 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
A version pin can be useful when a deployment has been tested against one release, when a hosting environment requires a controlled change, or when you must return to an earlier release after a failed upgrade. It is not a maintenance strategy by itself. WordPress.org recommends keeping sites on the latest release, and its supported-version policy says that only the last major release is currently officially supported. Older branches may receive security fixes as a courtesy, but there is no guaranteed schedule and WordPress has no long-term-support branch.
Choose the method before you touch the site
WordPress documents three broad ways to change core. The right choice depends on the access you have and whether the target is newer or older than your current installation.
#1 Best Overall
| Method | When it fits | Specific-version control | Access required |
|---|---|---|---|
| WP-CLI | A shell is available and you want an explicit version | Use --version=<version>; use --force for a lower target |
Shell access in the correct WordPress installation |
| Dashboard one-click update | A routine update with administrator access | WordPress documents the one-click path, but the specific-version command is documented through WP-CLI | WordPress administration access |
| Manual file replacement | You need a controlled file-level change or cannot use WP-CLI | Use the release archive for the version you selected | Hosting file access and a way to work with the database backup |
The official updating guide covers one-click and manual procedures and directs shell-capable operators to WP-CLI. For an explicitly chosen release, WP-CLI is the least ambiguous documented route.
Before changing core: make the operation reversible
Record what is installed
From the site directory, run wp core version and save the output with the date, target version, active theme, and enabled plugins. Knowing the starting version makes it possible to distinguish an upgrade from a downgrade and gives you a reference when checking logs or restoring files.
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 matchCreate and verify a backup
Make a restorable backup before running any update. WordPress’s update documentation recommends backing up before updating and explains that a failed change can be recovered by restoring the backup and using files from the previous release archive. Its auto-update guidance gives the same rollback rationale.
Cover both sides of the site:
- Database: posts, pages, settings, users, and other data stored in MySQL or MariaDB.
- Files: WordPress core, the
wp-contentdirectory, configuration, uploads, and any custom files your deployment needs.
Do not treat a downloaded copy of one directory as a complete backup. Confirm where the backup is stored, that it completed, and that you know the restoration procedure before proceeding. If your host or backup service offers a restore test, perform it on a staging copy rather than assuming the archive is usable.
Check extensions and the theme
Review every active plugin and the active theme against the target core release. WordPress notes in Manage Plugins that a plugin not updated since the most recent core release may be incompatible or have unknown compatibility; the administration interface exposes available compatibility information. A core downgrade can expose the same problem in reverse, so check extensions even when you are returning to a version that worked previously.
Decide whether the target is newer or older
Compare the value from wp core version with the release you intend to install. A higher target is a normal upgrade. A lower target is a downgrade or rollback and requires the explicit force flag described below. Write the target exactly, including all three version components when they are shown by the release.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →WP-CLI: install a newer specific release
WP-CLI’s core update reference documents the --version=<version> option for selecting a release rather than accepting the latest available version.
- Open a shell in the directory that contains this WordPress installation. If the server hosts several sites, make sure the current path and configured environment belong to the intended site.
- Confirm the starting release with
wp core version. - Check your backup and compatibility notes before changing anything.
- Run
wp core update --version=<version>, replacing the placeholder with the chosen release, for examplewp core update --version=6.6.2. Use a release that actually exists in the WordPress distribution history; do not add a leadingvunless the command reference for your environment requires it. - Read the command output for download, extraction, and completion errors. A successful command is not the same as a validated site, so continue with the checks in the verification section.
The command changes core only. It does not select new plugin or theme versions and does not make those components compatible automatically.
WP-CLI: return to an older release
When the target is older than the installed core, WP-CLI normally refuses to replace the newer files unless you explicitly allow it. Add --force:
wp core update --version=<version> --forceWordPress’s developer guidance shows the same pattern with wp core update --version=6.5.4 --force as an illustrative rollback command; that number is an example, not a recommendation for a current site. The --force option means you are deliberately allowing a version change even though the installed release is greater than the requested one.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Confirm that the backup contains both database and files from a known-good point.
- Record the currently installed version and the reason for returning to an earlier release.
- Run the version-specific command with
--force. - Check the site and its important workflows immediately. WordPress specifically advises checking that the site works as expected after an update.
- If the result is not usable, stop trying random combinations of releases. Restore the verified backup and, where necessary, restore the previous version’s files from its release archive as described in the WordPress update instructions.
A downgrade can leave the database at a state created by a newer core release. That is another reason to use a backup from before the failed change and to avoid treating --force as a harmless switch.
Using a distribution ZIP with WP-CLI
The WP-CLI core update command also accepts a ZIP-file argument. This is useful when your deployment process already has the exact WordPress distribution archive and you want to install that artifact rather than have WP-CLI obtain a release by version name. Follow the command syntax in the reference and provide the path to the archive, for example:
wp core update /path/to/wordpress.zipKeep the archive with your deployment records and verify that it corresponds to the intended release. A ZIP path does not remove the need for a backup, compatibility review, or post-update testing. If the archive represents an older release, treat the operation as a rollback and use the force behavior required by the command.
Verify the result instead of trusting the command output
Confirm the installed core version
Run wp core version again and compare the result with the target. This confirms which core version the command-line environment sees; it does not prove that visitors can load the site.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
Open the site and administration area
Visit the front end and sign in to /wp-admin/. Check the home page, a representative post, media uploads, search, forms, checkout or membership flows if the site uses them, and any custom endpoint that matters to your operation. Look for PHP errors, database errors, broken layouts, redirect loops, and missing assets.
Review plugins and theme behavior
Open the Plugins screen and review compatibility notices and update status. WordPress’s plugin-management documentation explains where compatibility information appears. Test the active theme and any plugin that controls authentication, caching, ecommerce, forms, or editorial publishing before declaring the deployment complete.
Check scheduled and background work
Allow enough time for the site’s normal scheduled tasks to run, then verify that expected jobs, notifications, feeds, and integrations still operate. A page load can look normal while a background workflow is failing, so include those checks in a controlled deployment checklist.
Core, plugin, and theme updates are different operations
Do not substitute a plugin or theme command for a core change. WP-CLI documents separate commands:
- Core:
wp core update --version=<version> - Plugin:
wp plugin update <plugin> --version=<version>, documented at wp plugin update - Theme:
wp theme update <theme> --version=<version>, documented at wp theme update
The component commands target their respective extensions; they do not change WordPress core. Plan their versions independently, and test combinations rather than assuming that a plugin version that worked with one core release will work with every other release.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Dashboard and manual alternatives
Dashboard one-click updates
The dashboard is appropriate when you have administrator access but no shell access and are accepting WordPress’s normal update path. Use the Updates screen, read the available release information, and follow the backup and testing requirements in the official guide. The dashboard workflow is designed around routine updates; for an exact, non-latest version, WP-CLI supplies the clearest documented selector.
Manual file replacement
Manual updating is an option when your host requires file management or your deployment process supplies a release archive. Download the selected WordPress release from an authoritative WordPress distribution source, preserve your backup, and follow WordPress’s manual update sequence rather than deleting files indiscriminately. The objective is to replace core files while retaining site-specific content and configuration, then complete any database update presented in the administration area.
Rank #4
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Because a manual operation can leave a mixture of old and new files if interrupted, work from a maintenance window and keep the previous files available for restoration. Afterward, perform the same version, front-end, administration, extension, and workflow checks used for a WP-CLI update.
Support and security implications of older releases
Installing an older release is technically possible, but it changes your risk profile. According to WordPress.org’s Supported Versions page, the last major release is the only version currently officially supported. Older branches can receive security backports at the project’s discretion, with no guarantee or fixed timeframe, and WordPress does not publish an LTS promise.
Before pinning or reverting, write down the concrete reason: a tested application dependency, a vendor requirement, a staged rollout, or recovery from a regression. Set a review date and an exit plan. A version pin should not become an unnoticed permanent exception; remove it when the compatibility constraint is resolved and retest the move to a supported release.
Troubleshooting specific-version updates
The command says the requested version is older
This is the expected protection against an accidental downgrade. Recheck the target and backup, then rerun with --force only when the rollback is intentional: wp core update --version=<version> --force.
The reported version did not change
Run wp core version from the site directory again. A shell session pointed at another installation can produce a perfectly valid result for the wrong site. Confirm the path, hosting account, and environment before repeating the operation.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The command cannot obtain or unpack the release
Use the ZIP-file form of the command when your deployment already has the correct distribution archive, and inspect the command output for the failing path or permission. Do not continue by mixing files from unrelated releases; restore the prior state or correct the deployment environment first.
The site fails after the change
Capture the symptom and stop further updates. Check the active theme and plugins for compatibility information, then use the verified backup and previous release archive to restore the known-good state if the site’s key workflows cannot run. Once restored, reproduce the problem on a staging copy and test the target release with the extension set before trying again.
The site works but a workflow is broken
Test the affected plugin or theme against the selected core release, review its compatibility notice in the administration interface, and isolate the failing component on a staging copy. Keep core, plugin, and theme version changes separate so that the next test identifies which change corrected or caused the behavior.
Operational checklist
- Write down the current core version with
wp core version. - Specify the exact target release and whether it is an upgrade or downgrade.
- Back up the database and all required site files, and confirm the restore path.
- Review plugin and theme compatibility information.
- Use
wp core update --version=<version>for a newer target. - Add
--forceonly for an intentional move to an older target. - Use the documented ZIP argument when installing a verified distribution archive.
- Run
wp core versionafter the change. - Test the front end,
/wp-admin/, critical extensions, scheduled work, and custom workflows. - Restore the backup and previous release files if the site cannot be returned to a working state.
- Record why an older release is pinned and schedule a review because older branches are outside the current official support baseline.
Bottom line
For a controlled WordPress core change, WP-CLI is the clearest method: select the release with --version, use --force only when deliberately downgrading, and keep a verified database-and-files backup ready before you begin. Treat plugin and theme versions as separate decisions, test the site’s real workflows afterward, and regard an older core release as a temporary, documented exception rather than a substitute for ongoing updates.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
