I have just tried to upgrade from 3.6.1 to 3.6.2 without any issues. Everything functions normally for me.

Fine for me too. I think you mean 3.6.1 to 3.6.2 as well @gunjanpatel :)

PHP 5.3 is now to old. Thank you Joomla Developers :) how needs a warning for that?

You can login in /administrator and see the menu but nothing works anymore, 5.3 is the problem.

aah yes Thanks @DavidBoggitt. Corrected in my above comment.

@RoterNagel what makes you say 5.3 doesnt work - it should work fine

Yes it is VERY old and not supported and insecure but it should still be supported by Joomla

3.6.1 didn't work (/plugins/user/joomla/joomla.php => Line 217 and 225-236)
But I have to apologies with 3.6.2 it works again.

Pops up alert box with "ERROR: Invalid Login"

This is _not_ meaning a Joomla login, this is meaning the restoration script "password" is incorrect. This is a generated, stored, and consumed password you never see, and protects your site during the tiny window of opportunity when the upgrade (restoration from zip file) is taking place.

see

This is part of the restore process, it means the restore ini file was not created or corrupt or other... just starting the process from scratch again should be enough to fix this issue

It can also alert like this if you click the back button AFTER a successful upgrade. Don't click the back button in the browser.

I have tried to upgrade from 3.6.1 to 3.6.2 several times now and I get an error saying "The most recent request was denied because it contained an invalid security token. Please refresh the page and try again." I have manually downloaded the upgrade patch and tried to manually install that as well. At that time I noticed that it came back with my login credentials before starting the backup process. However I use 2 factor authentication on my server and it never asked for the token to be put in. Is there a way to get around this issue.

have you updated com_joomlaupdate? Search for it as an Extension Update and apply it before upgrading

Are you using Akeeba backup on update and have not updated akeeba backup today? There was a fix in Akeeba backup also released today

Thank I noticed after a submitted the ticket that there were extension updates for Akeeba and Joomla updater. I have updated them both and now the upgrade is working properly.

Excellent - please click close on this issue then :)

Closed

I see this is closed, but I am experiencing this in a number of sites, that are updating from 3.6.2 to 3.6.4
Also sites that are already at 3.6.4, if I choose to reinstall Joomla core files I see this message too.
I cleared all cache, cleared update cache, checked everything else is updated first, etc?

Just wandering wether to create a new issue & refer/link back to this?

Please show your screento be sure you have the same issue and not another.

I have just saw this closed. Please open a new issue with the screenshot.

if the following file exists - delete it and then try again

/administrator/components/com_joomlaupdate/restoration.php

Thanks Phil.
That file exists.
I deleted it, tried again with same problem. Also the file is added again?
https://www.dropbox.com/s/75tblxi5800xed3/Screenshot%202016-11-07%2015.08.31.png?dl=0

what is the content of that file now - does it have any content ?

Same filesize
I hadnt looked inside it before, but all seems to be relating to Akeeba.

<?php
defined('_AKEEBA_RESTORATION') or die('Restricted access');
$restoration_setup = array(
    'kickstart.security.password' => 'REMOVED',
    'kickstart.tuning.max_exec_time' => '5',
    'kickstart.tuning.run_time_bias' => '75',
    'kickstart.tuning.min_exec_time' => '0',
    'kickstart.procengine' => 'direct',
    'kickstart.setup.sourcefile' => '/home/lowenerg/public_html/tmp/joomla_3-6-4-stable-update_package-zip?format=zip&jcompat=my.zip',
    'kickstart.setup.destdir' => '/home/lowenerg/public_html',
    'kickstart.setup.restoreperms' => '0',
    'kickstart.setup.filetype' => 'zip',
    'kickstart.setup.dryrun' => '0');

looks good to me. Have you updated the Joomla Update component to the very latest? (it has a separate release to the joomla release now)

Install this https://github.com/joomla/joomla-cms/releases/download/3.6.1/com_joomlaupdate-3.6.1.zip and try again after deleting restoration.php

The Akeeba references are expected, the update component uses some of the same code used in the Akeeba Kickstart engine.

Thanks Phil I'll try this & report back, but its happening on a number of sites.
The one in the screenshot & with the copied restoration.php file is already running 3.6.4 , but other sites that I have at 3.6.2 are not updating, with this same issue.

I updated with com_joomlaupdate 3.6.1 from the link you provided.
Deleted the restoration.php file & tried the Joomla Update > Reinstall Core Joomla Files again & get the same Invalid login popup message.

Than please move this to an new issue else it got missed fast

there is a PHP error log in administrator>components>com_joomlaupdate with this
[07-Nov-2016 09:34:20 CST6CDT] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Akeeba_Services_JSON_Error has a deprecated constructor in /home/lowenerg/staging/2/administrator/components/com_joomlaupdate/restore.php on line 925
But I tested this already with PHP7.0.12 & PHP5.6

Don't worry about that. FWIW #12385 fixes that but that alone isn't an issue yet.

FWIW, I was seeing this same error message when trying to update some sites and turns out the issue was the hosting account was out of disk space - so the update file couldn't be downloaded and extracted.

Joomla Update at 3.6.2
Joomla at 3.7.2
Trying to go to 3.7.3

Invalid Login.
I had previously updated the admin password (a few weeks ago). moved it back to original, but still same error. "Invalid Login" in popup box. Can't complete the upgrade.

Thinking that I probably need to do a manual upgrade. For some reason I have been needing to do manual upgrades "on occasion" recently with Joomla. Running 2 sites and likely an issue on one of them, and not the other.

BUT, NO. I upload it, then get a dialog to Login with My Admin Password, and I get the error "invalid login" on the same site giving problems on the Auto Update.

Second site works fine.
Where is this Akeba (IE) Kickstart Security Password is referenced that is referenced in the restoration.php file? (seems to be hashed which is always fun)

Invalid Login.

This is NOTHING to do with the users/admins passwords at all.

This pop up is about the internal secret login details that the Joomla update process creates before it starts an upgrade, and uses to authenticate requests during the upgrade process.

restoration.php is normally located (and should be deleted if found) at /administrator/components/com_joomlaupdate/restoration.php

I've done that a few times, but error persists so wondering what is setting the PW itself. It rebuilds the file each time and PW changes each time.

manually upgrade this time - this will fix the issue - and it will be fine for the future.

Thanks Phil!

Last week a 3.74 update went well. Today however, I had to do another manual update (3.74 to 3.75)... It is a strange thing. Not quite sure why. Another site is working fine. Not sure why this is toggling in and out.
I realize this should not be a support site but thinking some correlation between the "admin" login and the "admin" login during an update would actually work. Perhaps there is some XML password that is not matching current that perhaps I used a week ago. Doesn't seem that I would have.

I had this issue with upgrading Joomla 3.7.1 to 3.7.5 and I was able to install successfully it by doing the following:

1. The first thing I noticed was a warning about my php.ini not having a temp directory set.. So I found the INI file and enabled the temporary directories in it (I set it to "/tmp") Then I restarted my Apache server.

To do this, you can look up the location of the php.ini file in Joobla by:

• A. Select "System Information"
  
• B. Click on the "PHP Information" tab.
  
• C. Look at the "Loaded Configuration File" section. This was the 5th field down.
  
• D. Then I just used nano to edit the file.
  sudo nano /etc/php/7.0/apache2/php.ini
  While editing it, I pressed CTRL + "w" to open a search, typed "temp" and press enter till I found the right variables. There were two values that seemed to pertain to temporary files, so I set them both to = "/tmp".
• E. I saved the file and restarted my apache webserver.
  On Ubuntu: sudo /etc/init.d/apache2 restart

The update was still failing with the same "invalid login" message. Grr.

2. So I tried manually downloading the update file and unpacking it over my Joomla install directory.

However, this seemed to do nothing. I still got the same error. (This might be a necessary step, I don't know, so I am including it)

3. In an act of desperation, I tried setting 777 permission level to all directories in the Joomla installation folder.
find /var/www/html/MyJoomlaInstall -type d -exec sudo chmod 777 {} \;
This made the "invalid login" error go away! Whaa! GREAT!
Note: change the "/var/www/html/MyJoomlaInstall" part to point to YOUR Joomla install directory.

..But then it got an error stating that it could not replace a file and failed..

4. So then I tried setting all files in the Joomla install directory to 777 permission..
find /var/www/html/MyJoomlaInstall -type f -exec sudo chmod 777 {} \;
Note: change the "/var/www/html/MyJoomlaInstall" part to point to YOUR Joomla install directory.

And when I tried again.. Success!

Why this worked, I have no idea, but it did. When done, you may want to rerun those permissions settings commands with 755 or whatever level you prefer.

Edit: It is quite possible that the "www-data" user that PHP uses to write files wasn't able to write to directories in the folder because I had unzipped all the files as a different user. If this was the case, then instead, running the following may have also fixed the problem and would be safer:
sudo chown -R www-data /var/www/html/MyJoomlaInstall

Explanation: This sets all the files and folders in "MyJoomlaInstall" to be owned by the user, "www-data". This is the user my php runs under. I looked it up by using one of the solutions from here: https://stackoverflow.com/questions/7771586/how-to-check-what-user-php-is-running-as
First I created a temporary file "test.php" and added the following to it:
<?php echo exec('whoami'); ?>
Then I saved it and stuck it into a web folder and accessed it via my browser. This then gave me "www-data" as the user. So I was finally able to use chown to set the ownership of all the Joomla install files and folders to be owned by the same user that PHP would use to write the install files for the update. After doing this, set the permissions to 755, then tested installing a plugin in Joomla and I had no issues.

I have upgrade the site from joomla 2.5.8 to 3.5.1

Now I am trying to upgrade from joomla 3.5.1 to 3.6.5 and I am facing the same issue
ERROR:
Invalid login

And restoration.php file gets created again and again even if I delete it.

I have upgraded my com_joomlaupdate to the com_joomlaupdate-3.6.1 as well.

I also tried by using update package Joomla_3.6.5-Stable-Update_Package, but no luck, can any one please help me?

@bhaumikkotak Please ask help on the forums - Migrating and Upgrading to Joomla! 3.x. This repository concerns in first Place Joomla coding.