PHP 7.2: Can update WP core in wp-cli but not admin GUI

[danicholls]

When we attempt to update WordPress core from the admin area, it gets a critical error, but when we update it with wp-cli, it updates successfully, with the following output (warnings):

$ vendor/bin/wp core update
Updating to version 5.7.2 (en_US)...
Warning: Declaration of WP_CLI\CoreUpgrader::download_package($package) should be compatible with WP_Upgrader::download_package($package, $check_signatures = false, $hook_extra = Ar
ray) in C:\inetpub\[...]\vendor\wp-cli\wp-cli\php\WP_CLI\CoreUpgrader.php on line 14
Warning: Declaration of WP_CLI\UpgraderSkin::feedback($string) should be compatible with WP_Upgrader_Skin::feedback($string, ...$args) in C:\inetpub\[...]\vendor\wp-cli\wp-
cli\php\WP_CLI\UpgraderSkin.php on line 30
Downloading update from https://downloads.wordpress.org/release/wordpress-5.7.2-no-content.zip...
Unpacking the update...
Success: WordPress updated successfully.

To reproduce the GUI issue:

1. Go to Dashboard > Updates
2. Click 'Update Now' or 'Reinstall...'

Using the Health Check plugin's 'troubleshooting mode', I get a slightly more verbose error (but otherwise it's missing the line beginning "Fatal Error"):

Downloading update from ​https://downloads.wordpress.org/release/wordpress-5.7.2-no-content.zip…
The authenticity of wordpress-5.7.2-no-content.zip could not be verified as no signature was found.
Unpacking the update…
Fatal error: Maximum execution time of 30 seconds exceeded in C:\inetpub\[...]\wp-admin\includes\class-wp-filesystem-direct.php on line 82
There has been a critical error on this website. Please check your site admin email inbox for instructions.

Using a Windows server, but not sure if that matters.

[SergeyBiryukov]

Hi there, welcome to WordPress Trac! Thanks for the report.

Looking at the fatal error text, it looks like the default PHP timeout of 30 seconds is simply not enough for the download to complete on your install. Increasing the max_execution_time execution time in php.ini should resolve the issue.

WP-CLI does not have that time limit due to running from a command line.