A WordPress critical error after update is rarely a mystery for long, but the screen itself tells you nothing. Since WordPress 5.2 the core fatal error handler catches the PHP crash, prints a polite white page, and emails the admin a recovery link, deliberately withholding the file and line that would identify the culprit. This tutorial compares the three realistic recovery routes, then implements the one worth keeping: read the fatal from wp-content/debug.log , get back into wp-admin through recovery mode, and roll the offending plugin or theme back with WP-CLI. It finishes with a small mu-plugin that emails you the file and line the moment the next update fails.
You need file or SSH access to the install (SFTP covers the first half), WP-CLI 2.7 or newer for the rollback, and access to the admin email inbox on that site.
The critical error screen is a symptom, not a diagnosis
When PHP hits an uncaught fatal, WordPress runs WP_Fatal_Error_Handler on shutdown.…