To install a particular WordPress core release instead of the newest one, run WP-CLI from the site’s WordPress environment:
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
wp core update --version=<version>
For example, wp core update --version=6.5.4 --force deliberately moves a site back to 6.5.4 when its installed version is newer. Back up the database and files first, check plugin and theme compatibility, and confirm the target’s support status. The command changes WordPress core only; plugin and theme updates use separate commands.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What “update to a specific version” means
WordPress normally encourages updating to the latest available release. A controlled deployment, staging test, compatibility investigation, or recovery may instead require an exact core version. That is a version pin or rollback decision, not a general replacement for maintenance.
The clearest documented way to select an exact core release is the WP-CLI wp core update command. It accepts a version value rather than assuming the latest release. The command operates on WordPress core files and does not update installed plugins or themes.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Prepare before changing WordPress core
Choose and document the target
Write down the exact version, why the site needs it, and whether the move is forward or backward. A forward move installs a chosen newer release. A backward move is a rollback and should have a specific recovery or compatibility reason. Keep the target release archive or download location available if you need to restore the same files later.
Record the change owner, the planned maintenance window, the site URL, and the success criteria. If several people administer the site, tell them which core version is being installed and which components are intentionally not being changed. A clear record prevents someone from “fixing” the pinned version by running an unrelated latest-version update during the same window.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCreate a restorable backup
WordPress recommends backing up before an update and being able to restore that backup if the change causes trouble. Cover both parts of the site:
- The WordPress database, including posts, pages, settings, users, and plugin data.
- The site files, including
wp-content, uploads, themes, plugins, and configuration files.
Store the backup where it will survive a failed deployment, and verify that you know the restoration procedure before starting. WordPress’s update guidance explains the backup and recovery workflow at Updating WordPress; its auto-update guidance also stresses backups at Plugin and themes auto-updates.
An external hard drive can be useful as optional local storage for backup files you have downloaded, but the drive does not create a backup or guarantee that a restore will work. A backup service or managed host with backup capability is another category to evaluate. Whichever approach you use, confirm that it covers both the database and site files and that you can retrieve the files before changing core.
Check extensions and the theme
Review every active plugin and the active theme against the target core release. WordPress notes that a plugin not updated since the most recent core release may be incompatible or have unknown compatibility, and compatibility information is surfaced in the administration interface. Record any extension that is essential to publishing, checkout, forms, authentication, caching, or scheduled jobs so you can test those workflows after the change.
Recommended Free Tools
Do not assume that a plugin’s current version is appropriate for every historical core release. Note the versions currently installed, read the compatibility notices in the administration area, and identify a known-good theme and plugin configuration that can be restored if testing exposes a conflict. Keep plugin and theme changes separate from the core change whenever possible so the cause of a failure remains identifiable.
Consider support and security
WordPress.org states that the last major release is the only currently officially supported version. Older branches may receive security backports as a courtesy, but there is no guarantee or fixed timeframe, and WordPress does not provide an LTS version. Read the current policy at Supported Versions before pinning or reverting to an older release. A version lock should have an owner, a review date, and a plan to return to supported software.
Pinning a release for a short, documented compatibility test is different from leaving a production site on an old branch indefinitely. The official update instructions recommend using the latest version. If you must hold an older release, document the reason, monitor the site, and schedule a reassessment rather than treating the pin as permanent security policy.
Plan a maintenance window
Choose a period when you can monitor the site and, if necessary, restore it. Notify editors or administrators so they do not publish changes while files or the database are being changed. Capture the current configuration, active theme, active plugins, and core version before beginning. Keep the backup, the target version, and the restoration instructions accessible from the same operational workspace.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Method 1: Use WP-CLI for an exact core version
1. Confirm shell access and the site path
WP-CLI assumes shell or hosting access and must run in the correct WordPress installation. Change to the directory containing wp-config.php, or supply the site path with WP-CLI’s normal path option. On a server hosting multiple sites, verify the path before executing an update so you do not modify the wrong installation.
Use the same operating-system account and hosting context normally used to manage that installation. A command run against a staging directory, a different container, or another customer’s document root can succeed while leaving the intended site unchanged. Confirm the site identity and path before allowing the command to replace files.
2. Record the installed state
Record the current core version, PHP and database environment used by the site, active theme, active plugins, and any local modifications. Keep the output with the backup. This gives you a known comparison point if you need to restore or explain a compatibility failure.
Also note whether the site has custom core edits. Core files modified locally can be overwritten by an update, so preserve those changes separately and do not expect them to survive a replacement. The purpose of this inventory is to make the before-and-after comparison unambiguous.
3. Install a chosen version that is newer than the current one
Run:
wp core update --version=<version>Replace <version> with the release you selected, such as:
wp core update --version=6.6.2The WP-CLI reference documents the --version option for selecting a particular WordPress release instead of the latest one. Follow the command’s output and do not interrupt the process while core files are being replaced.
Use the complete release identifier you intend to deploy, including its patch number. Do not substitute a plugin version, a theme version, or a branch name. The command is for WordPress core; the other component commands have their own version-selection behavior.
4. Use --force for a downgrade or rollback
When the installed version is greater than the requested version, WP-CLI normally prevents the change. Add --force to explicitly allow the older target:
wp core update --version=<older-version> --forceFor example, the WordPress Developer Blog shows this rollback form:
wp core update --version=6.5.4 --forceThe 6.5.4 value is an illustrative example, not a current recommendation. Treat --force as a deliberate downgrade control: confirm the backup, target, and compatibility plan before running it.
A rollback can involve more than replacing PHP files. The previous release may expect different database behavior or extension combinations, which is why a restorable database and files backup matters. If the older release is only being tested, use a controlled environment where you can observe the result before applying the same operation to production.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
5. Install from a distribution ZIP when you already have one
The core update command also accepts a WordPress distribution ZIP as its argument. This is useful when deployment policy requires a vetted archive rather than a version lookup:
wp core update /path/to/wordpress-<version>.zipUse the archive supplied by a trusted WordPress distribution source, confirm that it is the intended release, and keep a copy with the deployment record. The ZIP method still requires the same backup, compatibility, and post-update checks.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Keep the archive until validation and any rollback decision are complete. An archive identifies the files you intended to deploy, while the version record identifies the release selected. Neither replaces a database backup or a test of the running site.
6. Check the result and the site
After WP-CLI finishes, verify the installed core version and inspect the command output for errors. Then test the site as a user and administrator:
- Load the homepage, representative posts or pages, and the login and dashboard screens.
- Submit important forms and test publishing, media uploads, search, comments, or commerce workflows that apply to the site.
- Check scheduled tasks, external integrations, caching, redirects, and error logs.
- Confirm that the active theme and critical plugins still activate and behave normally.
WordPress’s developer guidance specifically says to check that the site works as expected after an update. If the site is broken and the cause cannot be fixed safely, stop making unrelated changes and restore the verified backup or reinstall the previous core release from its archive.
Test both anonymous and authenticated paths. A public homepage can work while the editor, account area, payment process, form notification, or scheduled task fails. Write down each test result, including failures that were present before the change, so the deployment record is useful for the next decision.
Choosing the appropriate method
| Situation | Practical choice | Trade-off |
|---|---|---|
| You need an exact release and have shell or hosting access | WP-CLI with --version |
Requires correct command-line access and site path |
| You intentionally return to an older release | WP-CLI with --version and --force |
Higher recovery and compatibility risk; use a verified backup |
| You have a vetted distribution archive | WP-CLI ZIP argument | You must manage and identify the archive correctly |
| You have administrator access but no shell access | Dashboard update for supported updates | Convenient, but not designed for arbitrary historical version selection |
| Hosting constraints prevent WP-CLI | Documented manual file replacement | More opportunity for permissions, incomplete uploads, or mixed files |
All methods share the same prerequisites: a restorable backup, a compatibility review, a support-status decision, and post-change testing. Convenience does not remove the need for recovery preparation.
Dashboard and manual alternatives
Dashboard one-click update
The WordPress administration area provides the one-click update workflow for supported updates. It is convenient when you have administrator access but no shell access. It is not the clearest route for selecting an arbitrary historical core version; use WP-CLI when exact version selection is the requirement. Regardless of method, make the backup first and test the site afterward.
The dashboard can also show compatibility information and available updates for extensions. Treat those notices as input to your plan, not as proof that every workflow has been tested. A one-click core update does not update every plugin and theme as part of the same deliberate version pin.
Manual file replacement
WordPress documents a manual update path for operators who can download and replace files on the server. In broad terms, it involves obtaining the intended release archive, putting the site in a safe maintenance state, replacing the core files while preserving site-specific content and configuration, and completing the database update when prompted. Follow the current procedure in WordPress’s Updating WordPress documentation rather than deleting or overwriting wp-content or wp-config.php blindly.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Manual replacement is more error-prone than WP-CLI because file ownership, permissions, incomplete uploads, and leftover files can leave a mixed installation. Use it when hosting constraints prevent WP-CLI, and keep the backup and release archive available for recovery.
Do not confuse core, plugin, and theme updates
WordPress treats core, plugins, and themes as separate components. Running the wrong command can leave the core unchanged or update a component you did not intend to touch.
| Component | WP-CLI command | Version selection |
|---|---|---|
| WordPress core | wp core update |
--version=<version> |
| Plugin | wp plugin update |
The plugin command has its own --version option |
| Theme | wp theme update |
The theme command has its own --version option |
Use the component-specific references for those operations: WP-CLI plugin update and WP-CLI theme update. Updating a plugin or theme does not change WordPress core, and changing core does not automatically make every extension compatible.
If an extension must also change, schedule and test that as a separate operation. Changing core, a plugin, and a theme simultaneously makes it difficult to determine which change caused a regression and complicates rollback.
Compatibility checks after the version change
Start with the site’s highest-value workflows rather than only checking whether the homepage loads. A site can appear normal while an editor, form handler, payment flow, REST integration, or scheduled task is failing.
- Sign in as an administrator and open the Updates and Plugins screens.
- Check for plugin or theme notices about tested or unknown compatibility.
- Publish and edit representative content.
- Test media handling, navigation, search, forms, and any logged-in customer path.
- Review server, PHP, web-server, and WordPress error logs.
- Clear relevant caches only after recording the pre-change state, then retest.
If one extension fails, isolate it rather than immediately changing several versions. Temporarily disabling the suspected plugin or switching to a known-compatible theme can identify the cause, but do so during a controlled maintenance window and restore the intended configuration after testing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure modes and recovery
“The requested version is older than the installed version”
This is the expected guard against an accidental downgrade. Recheck the target and backup, then rerun the command with --force only when you intentionally want the older release.
The command ran in the wrong directory
WP-CLI may report that it cannot find WordPress, or it may target another installation. Stop, identify the directory containing the correct configuration, and rerun with the proper path. Confirm the site URL and version before changing files.
Outdated 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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFiles updated but the site fails
Check PHP and web-server logs, maintenance-mode output, permissions, and the active plugin and theme. If the failure blocks administration or publishing, restore the database and files from the verified backup, then document the failing workflow before attempting another version.
The dashboard still reports an update
Confirm the installed core version, clear stale caches, and check whether the dashboard is reporting a different available release. Do not repeatedly run updates without first comparing the reported and installed versions.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
A plugin or theme breaks after core changes
Use the compatibility information in the administration interface and the extension’s documented release notes. Roll back the core only when that is the approved recovery path; otherwise update or replace the incompatible extension in a separate, tested change.
Manual files appear mixed
Stop adding more changes. Mixed files can result from an incomplete upload, incorrect permissions, or an archive being unpacked over the wrong directory. Compare the intended release and installation path, then use the documented manual procedure or restore the verified backup instead of deleting configuration and content blindly.
A safe decision checklist
- Define the exact core version and the reason for selecting it.
- Confirm shell access and the correct WordPress path, or choose the documented manual route.
- Back up both database and files, and verify restoration.
- Check active plugins, the theme, and the target release’s support status.
- Run
wp core update --version=<version>for a chosen newer release. - For an intentional rollback, add
--forceand use the exact older version. - Verify the installed version, then test administrative and visitor workflows.
- Record the result and set a date to reassess an older, unsupported release.
Why version pinning should be temporary
An exact version can make a deployment reproducible or provide a controlled recovery point, but it also freezes core fixes and can leave extensions outside their tested combinations. Because WordPress officially supports only the last major release and does not promise ongoing backports for older branches, the safest long-term plan is to return to a supported release after the compatibility or recovery issue is resolved.
Frequently Asked Questions
Can I update WordPress core to an older version?
Yes. Use wp core update --version=<older-version> --force after confirming the target, backup, and compatibility plan. The --force flag explicitly permits replacing a newer installed version with an older one.
Does wp core update update my plugins or theme?
No. It changes WordPress core only. Plugins and themes use separate WP-CLI commands, each with its own version option and compatibility considerations.
What should I back up before changing core?
Back up both the database and site files. Include wp-content, uploads, plugins, themes, and configuration files, and verify that you know how to restore them before starting.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is the dashboard suitable for installing any historical WordPress version?
The dashboard is convenient for supported updates when you have administrator access, but it is not the clearest method for selecting an arbitrary historical release. WP-CLI is the documented route for explicit version selection.
What if I already have a WordPress ZIP file?
Pass the distribution archive to the core update command, for example wp core update /path/to/wordpress-<version>.zip. Confirm the archive is the intended release and retain it with the deployment record.
Are older WordPress releases supported?
WordPress.org says the last major release is the only currently officially supported version. Older branches may receive security backports as a courtesy, but there is no guarantee or fixed timeframe, and WordPress has no LTS version.
How do I know the update worked?
Verify the installed core version, inspect WP-CLI output, then test the homepage, dashboard, publishing, media, forms, commerce or account workflows, integrations, scheduled tasks, caches, and relevant logs.
What should I do if the site breaks after the update?
Stop unrelated changes, review logs and the active extensions, and restore the verified database and files backup if the issue cannot be resolved safely. You can also reinstall the previous core release from its archive when that is the approved recovery path.
The Bottom Line
For an exact WordPress core release, use wp core update --version=<version> from the correct site directory. Add --force only for an intentional rollback, and consider the ZIP form when deploying a vetted archive. Back up the database and files, review plugin and theme compatibility, test critical workflows, and plan to return to the currently supported release when the compatibility or recovery need ends.
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.
