same problem was reported from a user/supporter from switzerland. i think, the problem was there: a missing file write permission (chmod444 instead of chmod644) for the config.php, but not possible to say with garanty from my place. If i look into the function to rewrite the config-file, i see only 3 possible errors.
#1: the upgrade-script didn't read the "old" config.php,
#2: the permissions for the config.php and
#3: write permission for a temporary file unter /temp, called ~config
to #1
file_get_contents() is the savest method to read the content. The config.php must be there, otherwhise WB doesn't work. the function works with the minimal read-permission for the config, from my point, i see no option for a empty result of file_get_contents()
to #2
protect the index.php and the config.php in WB-Root-Folder with chmod444 was a tip in the past here in the forum.
The upgrad-script check the write_permissions with \is_writable() and set an error in the error.log and exit the script, before anything happend
P.S.: if somebody use the method with chmod444, please remember, that the server use a intern cache for this and sometime, it needs a couple of minutes to see the new chmod-value
to #3
WB check the write permission for the /temp-Folder in every step, because, it need this folder for the translation-cache. WB stops immediately, if there is a problem with this folder
since the last wb-version in december 2023 every tester makes hundred of upgrade and nobody has change the upgrade script in this part of code and i cannot remember, that we get some reports like this in the past. the method, to rewrite the config.php is nearly the same like WB 2.10
i 've to say (and sorry for that): i dont know, whats happend

the way is simple: read the old config, write it into a temporary file with some changes (if needed), include this content from the temporary file and set the values for the new file - and here is the problem
Last step: write the new content into the original config.php
Only solution (at the moment) - fill the config with the missing datas from a backup and start the upgrade-script again
I've some question about this
1. the first (crashed) Upgrade - do you start it from the backend and if YES, from the link with the redirect or from the info-windows (link in the last line)
2. do you the the white screen with the message "Restart Program (or press F5)"?