DEP Conflict
piemai
06 Aug 2009
Sorry to double/cross post... but i thought it appropriate to post it here too.
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..
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.
FuturepowerŪ
20 Nov 2009
A conflict with DEP (Data Execute Prevention) is a VERY serious problem. What is Autopatcher doing that it is trying to execute data?
Cristiano
20 Nov 2009
nothing. autopatcher works fine with DEP enabled, but sometimes DEP goes crazy and then you find yourself in trouble even to open certain things in control panel. when this happen, the best thing that can be done is help fix DEP, that can be done by scanning the system with an anti-virus software and/other actions
[]s
[]s
Cristiano
21 Nov 2009
by the way: this is how DEP is enabled in all my machines:
/noexecute=optin /fastdetect
so far i know, this is the default setting for dep in xp sp3. and autopatcher works in that way.
[]s
/noexecute=optin /fastdetect
so far i know, this is the default setting for dep in xp sp3. and autopatcher works in that way.
[]s
FuturepowerŪ
29 Nov 2009
Does Autopatcher or any program supplied with Autopatcher execute data?
Cristiano
29 Nov 2009
autopatcher only does this:
- checks the registry for certain keys that are used also detections;
- check certain files for versions and md5;
- creates an temp .bat file that will run the selected modules
- erases the temp .bat file
- goes to the next
- oh yes, i've forgot: autopatcher runs reboot.exe after finish, if an reboot is required
also i've said a dozen of times, i always run autopatcher with DEP enabled and i never had any issue. for sure, there's an signature issue, but this issue doesn't happen in normal situations, where DEP is running like should be running. so, in yours case, i bet that yours have messed with windows in any way that make DEP goes crazy. and, also yours should know, DEP has a lot of issues with certain softwares that doesn't have an signature on it and this issue us to become worst when something messes with DEP. so, one advice: don't mess with windows
[]s
Edited by Cristiano, 29 November 2009 - 03:49 PM.
- checks the registry for certain keys that are used also detections;
- check certain files for versions and md5;
- creates an temp .bat file that will run the selected modules
- erases the temp .bat file
- goes to the next
- oh yes, i've forgot: autopatcher runs reboot.exe after finish, if an reboot is required
also i've said a dozen of times, i always run autopatcher with DEP enabled and i never had any issue. for sure, there's an signature issue, but this issue doesn't happen in normal situations, where DEP is running like should be running. so, in yours case, i bet that yours have messed with windows in any way that make DEP goes crazy. and, also yours should know, DEP has a lot of issues with certain softwares that doesn't have an signature on it and this issue us to become worst when something messes with DEP. so, one advice: don't mess with windows
[]s
Edited by Cristiano, 29 November 2009 - 03:49 PM.
