I see that most RE tutorials around the web that give RE examples use OllyDbg 1, even if the tutorial was written after the release of OllyDbg 2.

Is there any particular reason for that? Is version 2 too buggy, or were some of the features dropped?

  • 1
    It mystifies me as well when people have already written plug-in converters for ImmDbg, which I honestly prefer for the python bindings. Commented Apr 6, 2013 at 15:25
  • "Why are more tutorials using version A rather than version B ?" cannot be objectively answered, in my opinion. Voting to close.
    – asheeshr
    Commented Apr 6, 2013 at 16:15
  • 9
    I don't agree. Usually these kind of things boil down to a very specific reason. Commented Apr 6, 2013 at 16:34

3 Answers 3


Well, there is another reason. Historical one, actually.

At end of 2001, when the first versions of Ollydbg were presented, there was SoftICE, which was at its end, and IDA was not that popular yet. So OllyDBG became sort of the de-facto replacement for the main black-hat tool for cracking\patching\keygen-writing. And OllyDBG 1.x is a good, handy tool.

Since then, the development of OllyDBG became a slow process, with lots of delays. When it was finally announced, there appeared to be some problems, plug-ins compatibility etc. You may see the story at OllyDBG 2.x webpage on offsite.

On the other hand, IDA Pro of Hex-Rays proved itself as a useful tool, very handy.

The bottom line - when in June 2010 version 2.0 of OllyDBG was released, it was buggy, didn't support old plug-ins and there were no reason to change to the new version, at least for me. In addition, many manuals were available for version 1.x, and the benefits of version 2.0 for tasks OllyDBG was used for were not attractive enough, IMHO.

End of story :)

  • 3
    I really don't see how IDA fits into the equation here. IDA is a static analysis tool while Ollydbg is a debugger. Sure Ollydbg does basic flow analysis, and IDA can talk to debuggers, but they are very different tools. Commented Apr 9, 2013 at 4:42

The main reason I believe is the scripts and plugins that exist for OllyDbg 1. Tuts4you.com has around 250 plugins for version 1 and only 30 for version 2.

Also the feature list is not great anymore to make someone change from version 1 to the new version. If someone is changing from OllyDbg v1 to something else, WinDbg could be a choice.

  • 1
    or x64dbg
    – DOD
    Commented Aug 21, 2015 at 8:46

Hi,the most important reason is: debugging / reversing is quite abstruse and difficult, when you see a full screen assembly codes, and then suddently, they carsh/ fatals / freeze ... You just have no any idea to go on. So you have to search the answer in Internet, but most informations are all about Ollydbg 1.1, and there are lots of plugins to help you resolve the problem, enen though you don't know any secret inside the plugin or else.

So, would you take your advantage to try the v2.0, face to helpless situation lonely ?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.