Outlook 2016 64bit Error Message

[hlewton]

Long Story Short MS had to update my Office 365 to the 64 bit version today. When opening Outlook I get the error message I will attach below. It is there every time I open Outlook even though I choose the Disable button. Any idea how I can get rid of it?

Thanks

Outlook.jpg

[HansV]

Did you ever create a digital signature for your Outlook macros using SelfCert.exe?

[hlewton]

Did you ever create a digital signature for your Outlook macros using SelfCert.exe?

Honestly I have no idea. How can I check and disable it?

[HansV]

Once in Outlook, press Alt+F11 to activate the Visual Basic Editor.
Select Tools > Digital Signature...

S1903.png

If the Remove button is active, click it and confirm.
Then OK your way out, and close the Visual Basic Editor.
Restart Outlook. What happens?

[hlewton]

Hans I do not see any option for Tools. What I see I'll attach below.

Macros.jpg

[HansV]

I meant the Tools menu in the menu bar.

[hlewton]

Sorry I see what you were talking about not but I have tried it 3 times and each time it says Outlook has stopped working, it tries to repair it but has no success.

[hlewton]

Not sure if you saw my other post but I figured out what you wanted me to do but it crashes Outlook every time I try it.

[HansV]

I'd go back to 32-bit Office if I were you.

[hlewton]

I'd go back to 32-bit Office if I were you.

I can't do that. Was on phone for over 4 hours with MS today and they are "supposed" to call me tomorrow to see how this is working. He tried uninstalling and reinstalling the 32 bit version and it had so many problems trying to open attached files in Outlook and could even open them on my ISP's server. The 64 bit version took care of those problems, at least so far, and if I have to live with that 1 extra click to have everything else work I may have to do that. The MS technician knows about the error message and said the fellow tomorrow would try to fix that but I doubt he will be able to. Thanks for trying.

[HansV]

The 64-bit version has many more problems than the 32-bit version in my opinion. Good luck...

[hlewton]

Thanks Hans I may need the good luck but unfortunately, at least for now, I am stuck with the 64 bit version since they cannot make the 32 bit version work.

I was wondering, while I am waiting for my call back from MS today if you thought it may be worth a try to open Outlook in the safe mode and then try the editing you suggested above. I have never used Outlook's safe mode and all except that error message seems to be working fine now so I thought this may be worth a try if you think it would not damage anything else in Outlook. If I can try that I could not find anything on the WEB that specifically mentioned Outlook 2016 but I assume to open it in the safe more I would type "outlook.exe /safe" in the run command line. Is that correct?

[HansV]

It's worth a try. There are two methods to open Outlook in safe mode. You can use either.

1) The method that you describe.
2) Hold down Ctrl while starting Outlook. It will ask you whether you want to start Outlook in safe mode; answer Yes.

[hlewton]

Thanks.

[hlewton]

Outlook in the safe mode displayed the same error message and also crashed the same as it did when opening it regularly when trying to check for that digital signature. So this may be a dumb question but the error message I get as seen in the first post has a button to click to disable macros. In the 4th post I attached a screenshot of what I see when using Alt + F11. Is that a macro and could it be what the error message is checking? If so, is it something I could delete and possibly that could stop the error message from showing each time Outlook is opened?

[HansV]

Yes, that is a macro. When a reminder of an appointment occurs, it automatically sends a message to the location (meeting room or similar) of the appointment.

You could clear that entire code window. You may want to copy the code into a text file first.
When you quit Outlook, it will ask if you want to save changes to VBAProject.OTM; answer Yes.
But I doubt that this will get rid of the error message.

[hlewton]

OK thank you. I may have to try that if MS cannot get this figured out.