How to: circumvent the error “The authenticity of could not be verified as no signature was found” when trying to update your WordPress version

It’s been some time since I last logged on my blog (yeah, I know) and when I tried to update my WordPress version, I was not able to.

What was the issue

According to the installer, the problem was that the zip file that was being installed could not be verified because there was not signature. That was so bizarre. What did I have to do with the WordPress zip file signature? Nothing. Similarly, what could I do to fix it? Nothing.

What was the solution

Turns out that in order to overcome that issue, I had to manually download the WordPress zip file from the WordPress Releases page and then use an FTP client to install it on my server. It’s really nothing too complicated, as long as you have FTP access to your site (I.e. an FTP account) and an FTP client. I almost always use FileZilla, which you can get here. Before downloading, make sure that you select the appropriate version as that page has versions for different architectures, different operating systems and also versions bundled with other software that you will possible want to avoid.

Once the WordPress zip file has been downloaded, extract the files on your machine and you should have a WordPress folder with all the necessary files. Run FileZilla and upload the entire contents of the WordPress folder into your blog folder. You’re looking for a folder on your website with the following subfolders: wp-admin, wp-content, wp-includes. When you’re in the right place, select the contents of the extracted zip file and upload and overwrite the existing files on your server. It is always advisable to first take a backup of your existing files, in case you need to revert back to them.


  1. Could not be verified as no signature was found
MGR: the Intelogist

About MGR: the Intelogist

SharePoint Server developer, turned Sitefinity developer, turned Angular developer, turned SharePoint Online consultant, turned Unily consultant, turned O365 consultant... Never a dull moment!

One thought on “How to: circumvent the error “The authenticity of could not be verified as no signature was found” when trying to update your WordPress version

  1. пластиковые окна

    My brother recommended I would possibly like this website.
    He was entirely right. This submit actually made
    my day. You cann’t believe just how so much time I had spent for this info!

    Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> 

This site uses Akismet to reduce spam. Learn how your comment data is processed.