Bleh. It was found to be Autopatcher. And I should not respond to unnecessary arbitrary personal attacks, but I'll do so for what is likely my last post here. You apprently overlooked the So your thought was correct, sir, intended to be a compliment.
Sorry, but enabling a DEP exception for a modern program simply isn't very obvious. Especially when such a problem is far more rare than other possibilities here. Also, hardware DEP normally works by providing its own error/warning frame when it catches incorrect memory accesses, etc.. As opposed to program crashes or whatever else interfering with providing that frame. I would qualify that by restating my experience with all sorts of programs old & new not exibiting such an issue (besides virii), thus a DEP exception not being the first troubleshooting step on the top of mind. But such statements apparently bother you, so I won't.
OK dude. I was posting as I went along with troubleshooting. You made mention earlier of not having experience with Windows 7's WEP as opposed to XP's so I spent time detailing the output differences. Sorry about spending time doing so.
Huh? Where do you get the idea that I didn't? With it disabled, as mentioned, full program crashes nearly always provide no UI feedback at all in Windows 7, unlike XP. Including autopatcher when tested with the problem with it disabled, thus providing nothing of value. Who said it "wasn't safe"? And what are you talking about in that "I don't know what I'm talking about"?
I prefer the MS Download Center .
My "approval" is irrelevant. It was found in the end to be an issue with autopatcher unusually not working with DEP. That's all. The managers can take the problem info and do what they wish with it. It doesn't matter to me at all. Its a great program idea and I do really appreciate Viroman's help with the matter.