Ok been asked a thousand times DEP XP pro

Question

DEP on XP Pro
has lock iTunes, done re-install turned on/of and on again in DEP, tried numorus times inc.. re-boots.
its almost like DEP HAS LOCKED and wont except new settings. happend after update 10.4 can only update my iPhone4 via WiFi, havent been able to chage my music for over 6 months!!
virus checked nothing found
i have no partion drive so no reinstall of windows is possable [ have no copy of original disc ]
as usual microsoft wont answer emails etc.. or help out
any other pointers or clues
thanks in advance

Answer 1

Excellent news.
wonder why itunes didnt install in the first place? it used to
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.