I am running Windows 10 with Office 2010 and McAfee LiveSafe and suddenly I find today that I need to disable Data Execution Protection (DEP) mode in Outlook 2010 in order to enable Outlook 2010 to start with the mskoladd.dll add-in enabled. I don't regard this as a satisfactory long-term solution. Hitherto it has not been necessary. I don't think this can be a result of a Windows or Office update, because Update History shows that the last such update was a week ago, and I have accessed emails every day since then without problem until today. So I presume it's because of a LiveSafe update.
Is anybody else having this problem?
The answer is yes it always has been compatible with DEP.
Turning off DEP is NOT recommended as it is one of W10's ways of protecting itself (& you). (Also applies to Windows Vista, 7 and 8/8.1, for anyone reading this).
That add-on should not be asking you to do that and should offer an alternative way of installing. However you can turn off DEP if you wish - it's your computer after all.
Turning it off gives anything full Administrative rights to run on your machine and that would include malware.
This has nothing to do with McAfee other than hopefully the software would stop whatever malware that is, should it occur.
I would strongly recommend turning it back on after the programme or add-on is installed.
Thanks Peter. I only disabled DEP mode yesterday because when I started Outlook 2010 I got a message saying that the McAfee add-in for Outlook 2010 (mskoladd.dll) was incompatible with Data Execution Protection mode. I was then asked if I wanted to carry on loading the McAfee add-in or not. If I said Yes, Outlook immediately shut down, so next time I answered No, then disabled DEP mode from the Settings inside Outlook 2010 and re-enabled the mskoladd.dll add-in. Now Outlook started OK and I left things like that while I posted yesterday's message.
Today I find I can enable DEP without getting the incompatibility message, which is great, but I can't understand what has changed to bring about this happy outcome.
Maybe all it needed was a reboot? That's good news though.
I guess you could mark your last answer as the solution?
The problem has recurred again today.
It may be helpful if I show the exact text of the error message that is shown when I try to start Outlook 2010:
Outlook experienced a serious problem with the 'mcaffee addin' add-in. This add-in is incompatible with Data Execution Prevention mode and should be disabled or upgraded to the latest version. Do you wish to disable this add-in from loading?
This message is followed by two buttons Yes (the default) and No. As I explained before, I have to say Yes, at which point Outlook starts OK. But now even after disabling Data Execution Prevention mode inside Outlook 2010, when I re-enable the mcaffee add-in and try to re-start Outlook, it shuts down with the "Microsoft Outlook has stopped working" message.
So the situation is now that the mcaffee addin is incompatible with Outlook 2010 (on Windows 10) whether DEP mode is enabled or not.
I've been thinking further about this, and I'm beginning to think that this is a Microsoft problem rather than a McAfee problem, so I apologise for having posted in this forum.
After my post earlier today, I ran the "repair" option on Office 2010 installation, and after doing that (plus the compulsory reboot), I am able to open Outlook 2010 with both the McAfee add-in enabled and DEP mode enabled. I have been through this cycle several times in the last month or so, and each time after a week or two Outlook 2010 stops working. Sometimes I get the message about the McAfee addin being incompatible and sometimes not, but eventually I always have to "repair" Office 2010 again. I'm inclined to think therefore that the basic problem is an unresolved incompatibility between recent Windows 10 updates and Outlook 2010, such that each time I repair Office 2010, Windows Update eventually overwrites the repair with changes which prevent Outlook from starting. It's infuriating but manageable, and I think the message about the McAfee addin is probably a symptom not a cause.
Thank you for your input I hope the issue eventually resolves itself.
All the Best,