Outlook 2016 not saving digital certificate with macro project file.

[harleygnuya]

I have an Office 365 subscription that is up to date and I'm running Windows 10 Pro 64-bit.



Yesterday, my macros were running fine. This morning, they did not run when I clicked on the ribbon button I had set up for them. I went to Developer, dropped down Macros and clicked on the macro I wanted to run, and, again, nothing happened. I then dropped down Macros, clicked on Macros, which brought up the Macros dialog, from which I selected the macro and clicked on Step into. I then got an error message that reads:

The macros in this project are disabled. Please refer to the online help or documentation of the host application to determine how to enable macros.

I then checked my self-signed digital certificate (Visual Basic->Tools->Digital Signature) and the one I've been using for months was still selected. I then checked my macro security, which was set to "Notifications for digitally signed macros, all other macros disabled". I changed this to "Enable all macros", exited and restarted Outlook, and the macro ran just fine. So, I changed the setting back to allow only signed macros and continued to try to find the problem.

I tried to remove and rechoose my digital certificate. When I tried to save my project file, I got the following error message:

There was a problem with the digital certificate. The VBA project could not be signed. The signature will be discarded.

Sure enough, upon exiting and restarting Outlook, the certificate was no longer active.

I then created a new self-signed certificate using Microsoft Office->Digital Certificates for VBA projects in the start menu. I selected it in the Visual Basic editor, but again, when I saved it, I got the same error message.

I tried deleting all my code from the project files and removing all the files from the project, but even then I was unable to save the certificate with the project file.

Office 365 updated two days ago, and I'm not sure if I've run the macro since then, so it may be related to this most recent Office update. That's just a thought - again, I'm not sure if I ran the macro since then until I tried to run it today.

For the time being, I'm allowing all macros to run in Outlook, but I certainly do not want to continue this for very long.

Why am I having this problem and what can I do to fix it?

Thanks