A week ago, I've loaded an app into Olly, as an exercise and out of curiosity. It has been successfully loaded and I've found out that there's no protection of any kind applied (all strings are plaintext, no anti-debugging techniques, simply nothing).Today, I wanted to come back to said program and suddenly I'm unable to load it into Olly - even before Olly starts its analysis (the bar in the bottom of the window), the process terminates and I land in ntdll.dll.If run without a debugger, the exe works fine - there seem to be no problems.I'm really puzzled because since then I've made two changes to my PC: Installed Nod32 4 (disabled it, nothing changed)Downloaded WDK 8.1 from this page:http://msdn.microsoft.com/en-us/windows/hardware/gg454513.aspx (uninstalled, didn't help either)I've also tried this on another PC which hasn't been even powered on for the last month and is basically a clean Win7 install, still to no avail.At the first glance, this probably looks like battling a TLS Callback protection, but as I said, I'm certain the exe has no protection at all, as I've been able to play around with it a couple days ago.Are there any 'common' causes for such behavior?
Suddenly unable to load exe into OllyDbg - process terminates before execution
ollydbg