Annoying Windows Security Alert

[Matilda]

I just allowed Microsoft to update my Outlook Mail program – I wish I hadn’t, but it kept pestering me so much, I finally allowed it.

Now, it won’t allow me to open or send mail without putting in my password – I’ve never bothered using a password for Outlook and have no idea what it might be. I can’t even email my IT guy, because it won’t let me! I’d like to get rid of this Security Alert, but I’ve tried Googling information and there’s nothing useful there.

Can somebody tell me what I should do about it? Because I can’t go on with my work until I do; it won’t let me.

[Egnever]

1. What operating system are you using

And what version of outlook?

[Matilda]

2. Oops, should have put that.

I have Windows 7, and I just installed a new version of Outlook 2016 (because it kept prompting me).

What I have done now is tried System Restore - it says it's taken the computer back successfully, but now the mail program won't open at all. I can use everything else, but I can't get into the mail.

Edit to add: Now that's supposed to have gone back, I think the Outlook might be called 365 - does that make sense?

[Egnever]

3. oof

well at this point go to control panel then programs and features and find office click on it and hit change at the top.

Then have it run a repair and it should at least open again. If you still have issues let us know.

[Matilda]

4. Thanks - I'll try that.

[Matilda]

5. No luck.

It said it had encountered a problem, and directed me to a website which said to uninstall Office (it is 365), and reinstall. It makes me nervous, but is that the best thing to do?

[Egnever]

6. Thought you said 2016?

office 365 has two models. A subscription where you pay by the month or a full licsense where you buy it in one shot.

Do you know which you have?

[Matilda]

7. I have the full licence.

I think the problem started because I was being prompted by Microsoft to upgrade my Office 2016, and being clueless, I tried it.
So it was the wrong program, I guess. Why it was prompting me, I wouldn't know.Definitely 365 - it said so in the Control Panel.

[Egnever]

8. ok next question

is 2016 still listed in the control panel?

If so removing the 365 should be fine. If not then I get a little concerned about contacts and emails you have stored on your machine.

Uninstalling the 365 and reinstalling the 2016 should be fine but stuff happens. If it were me I would back up the outlook folder to be on the safe side.

Some info on how to find them.

Outlook Data Files (.pst) created by using Outlook 2013 or Outlook 2016 are saved on your computer in the DocumentsOutlook Files folder. If you upgraded to Outlook on a computer that already had data files that were created in Microsoft Office Outlook 2007 or earlier, these files are saved in a different location in a hidden folder at drive:UsersuserAppDataLocalMicrosoftOutlook.

The offline Outlook Data File (.ost) is also saved at drive:UsersuserAppDataLocalMicrosoftOutlook. Most data remains on the server; however, any items that are saved locally should be backed up. For example, Calendar, Contacts, Tasks, and any folders marked Local only.

I would just make a copy of the whole folder and put it somewhere you can find it. Then do the uninstall and reinstall. If all goes well it should just come back with everything as it was. If your stuff is missing you can import from the backup copy you made to get it back.

[Matilda]

9. Thank you for your advice.

Turned out to be not so easy, and I had to call on my IT guy. Seems the glitches were caused by the fact that all my Office programs are 32 bits, except for one that’s 64, and that’s why it kept aborting every attempt. The program is something I need for work, and the IT guy had to install it from my old computer when he set this one up, and so he knew his way to get around it.

Only took him an hour!

But thank you for your efforts – now I have to try to work my way around what is now an unfamiliar Office program

[Egnever]

10. Never even occurred to me you would have a 32 bit version

Never would have figured that out on my end. Glad you called him.