Solved: Save encoded certificate to store failed = 0x5 (5)

by | Aug 4, 2013 | Technology | 22 comments

I was recently trying to create a certificate for Azure / Windows Server 2012 essentials integration and had problems with a certificate. You have to have a certificate for connecting to Microsoft Azure backups and not realizing that the server already had a self signed cert, I set about following the instructinos to create my own.

If you’re trying to make a certificate using Microsoft’s MakeCert.exe tool, you may find that after typing a very long command into the command prompt that it kindly tells you it failed and gives you the following message:

Error: Save encoded certificate to store failed => 0x5 (5)
Failed

Microsoft has kindly given you another awesome error message that means next to nothing to a human being. The good news is this. It’s SUPER easy to fix. Simply run the same command again in an elevated command prompt (read Run As Administrator) and it should work perfectly!

22 Comments

  1. marco on July 17, 2014 at 4:00 AM

    thank you! 🙂

    Reply
  2. vlad on October 24, 2014 at 9:10 AM

    Good thing you showed up in my google results 🙂 Thanks!

    Reply
    • Joseph Turley on October 24, 2014 at 9:14 AM

      You bet! Glad this article actually helped someone.

      Reply
  3. Bill Sorensen on April 20, 2015 at 3:36 PM

    Thanks – that just fixed my issue with importing a certificate with winhttpcertcfg (similar error message).

    Reply
  4. Eoin on November 5, 2015 at 2:53 AM

    Worked a treat, much appreciated!

    Reply
  5. Caleb on November 10, 2015 at 2:48 PM

    I’m glad I searched for a solution (and found your link) rather than trying to solve the issue, myself. I wouldn’a thunk it was a rights issue, especially since I had just used makecert for something else and that had succeeded! Thanks, Joseph.

    Reply
    • Joseph Turley on November 10, 2015 at 5:31 PM

      It’s the small things, isn’t it? Glad I could help!

      Reply
  6. Freddy on November 30, 2015 at 9:23 PM

    Thank you for this!

    (No thanks for your milkshake post…see comment there)

    Reply
  7. Amelie on April 2, 2016 at 5:12 PM

    simply great thanks ! saved me some time. merci 😉

    Reply
  8. Farooq on July 6, 2016 at 4:04 AM

    Thanks a ton. Saved me a few hours 🙂

    Reply
  9. Milad on January 16, 2017 at 11:48 PM

    Thank you

    Reply
  10. susan on February 23, 2017 at 11:30 PM

    thank u 🙂

    Reply
  11. Sia on January 5, 2018 at 1:44 AM

    Thank you so much…i spent an hour trying to find the problem and then stumbled on your page. And loved your comment “Microsoft has kindly given you another awesome error message that means next to nothing to a human being.”

    So true!!!

    Reply
    • Joseph Turley on January 5, 2018 at 2:15 AM

      Glad I could not only help you solve this, but also make you smile. 🙂

      Reply
  12. Ki Li on February 22, 2018 at 4:44 AM

    Nice ! x.x

    Reply
  13. Abhinav on March 31, 2018 at 4:42 AM

    Good One, Save my day

    Reply
  14. Kurt A. Hinds on June 22, 2018 at 3:05 AM

    Perfect! Thanks!
    When will they let error’s also tell you what to do….

    Reply
  15. Julian Restrepo on September 11, 2018 at 1:59 PM

    Glad I found your solution, replying here just to say a big thank you!

    Reply
    • Joseph Turley on September 11, 2018 at 2:00 PM

      Glad it worked out for you. 🙂 Have a great day.

      Reply
  16. Ram on November 6, 2019 at 5:45 AM

    Thanks , It worked ..

    Reply
  17. netnavi on April 14, 2020 at 8:26 PM

    thanks its worked

    Reply
  18. Bob on February 5, 2021 at 8:10 AM

    Thanks!

    Reply

Submit a Comment

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