This relates to my post titled: Autopatcher will not run (No errors, running autopatcher.exe does nothing)
in the "AutoPatcher for Windows XP SP3 (32-bit)" Forum
http://www.autopatch...r-will-not-run/
This problem seemed to be caused by some kind of conflict with DEP (Data Execute Prevention)
anyways here are my last two posts from that thread..
piemai, on 06 August 2009 - 11:32 AM, said:
Problem solved....
I have DEP (Data Execute Prevention) set to opt out...
For some reason autopatcher seems to conflict with DEP...
Autopatcher.exe runs just fine after adding it to the exceptions list.
If anybody has any questions, or if i can be of any assistance to help solve this DEP conflict just let me know how i can help..
I have been a user of autopatcher for years now and i simply love it. No other tool has saved me more time, energy, downloads and allowed me to ensure an up to date operating environment right from the start.
Again, thank you to everybody that gave me ideas and input... I really appreciate it.
I have DEP (Data Execute Prevention) set to opt out...
For some reason autopatcher seems to conflict with DEP...
Autopatcher.exe runs just fine after adding it to the exceptions list.
If anybody has any questions, or if i can be of any assistance to help solve this DEP conflict just let me know how i can help..
I have been a user of autopatcher for years now and i simply love it. No other tool has saved me more time, energy, downloads and allowed me to ensure an up to date operating environment right from the start.
Again, thank you to everybody that gave me ideas and input... I really appreciate it.
piemai, on 06 August 2009 - 11:50 AM, said:
Further information... screen captures of error taken in the VM... (i had error reporting service disabled in windows so it never told me DEP was preventing autopatcher from running)
Adding autopatcher.exe to the exclusions list for DEP fixed the problem both in the virtual environment and on the separate physical machine.


Adding autopatcher.exe to the exclusions list for DEP fixed the problem both in the virtual environment and on the separate physical machine.













