HT1222 "Data Execution Prevention" not letting ITunes launch. How do I remove DEP?

Question

How do I get rid of Data Execution Prevention!!!??? All of a sudden this annoying little program wont allow me to open Itunes!! I tried turning it off the way they said to but it still blocks itunes. I even reinstalled Itunes No luck  I still cant use Itunes  HELP!!!

Answer 1

And no problem for "barging in"; your expertise in solving Windows issues is always welcome. Cheers.
Thank you.
The situation with these changed up a bit with the introduction of the iTunes 10.5.x versions and above. (A "new problem wearing old trousers" event.) I have a note in the Full Host Bar about it, though it's speculative. Here's the content of the post there:
There's various possible causes for DEP errors when launching iTunes for Windows. But in recent times we've been able to get past a number of them by updating folk's QuickTime Player to the latest version. For example:
Re: When I tried to update to 10.6.3 it failed
The interesting thing about that is that since iTunes for Windows 10.5.x, you aren't supposed to need QuickTime for Windows componentry to be installed in order for iTunes for Windows to launch. So it's not likely that the DEP errors are being caused purely by the lack of QuickTime componentry on the PCs in question (or by the lack of new-enough versions of QuickTime componentry on the PCs in question).
One putative mechanism for what's going on.
I've noticed (in the course of other experimentation) that if the QuickTime Player is uninstalled on an XP system and iTunes for Windows (some version post 10.5.x) is launching, I can get a message saying that certain kinds of content can't be played because QuickTime isn't installed.
So there's a task performed by iTfW when launched to check on the presence of certain types of QTfW componentry. If the answer is "that componentry is not present", a routine is run that shows the dialog saying that certain content can't be played.
It's plausible that Data Execution Prevention is interpreting the routine that produces the dialog as being a malicious act on some systems, and throwing the DEP error when the routine is run.
That would explain why updating (or possibly installing) the latest version of the QuickTime Player is getting people past the DEP errors. The check for QTfW componentry is run when itunes launches, but it determines that the componentry is present. So the routine that produces the dialog isn't run, and Data Execution Prevention doesn't feel compelled to throw the DEP error.