I need an advanced reverse engineering software/tool for Windows environment (32 bit or 64 bit, Windows 8 or Windows 10 etc. - preferably 64 bit Windows 10) including low-level kernel mode debuggers which doesn't require you to have two computers.

Regarding debuggers, I have tried:

  • Windbg requires two computers as I know
  • Ollydbg is not much advanced as I know
  • Any other software like "Syser" after "SoftICE" had been discontinued.

I'd also need disassemblers (after IDA Pro etc.), patching tools (hex etc.) and any other miscellaneous reversing tools or de-compilers etc. Strictly for educational purpose only.

  • Gratis? Do you need any other features?
    – Nicolas Raoul
    Aug 1, 2016 at 7:43
  • 1
    Are you looking for a single software to cover it all? // I've just edited your question to make it fit this site (we don't do research for what's famous or most-used – we recommend software that fits given requirements). Still, your question looks like you are searching for multiple different tools. If that's so, please put each question in a separate question post. Also see: What is required for a question to contain "enough information"?
    – Izzy
    Aug 1, 2016 at 8:53
  • As the top 2 user in the WinDbg tag I don't see an alternative to WinDbg at this time. It is the official Microsoft debugger. It does not need 2 computers for kernel debugging. Although it can disassemble, you'll not be happy with it, since IDA Pro is much more powerful. Also, WinDbg does not include a patching system. What you need is a complete tool chain which may consist of dozens of programs, since you'll need special tools for .NET (SOS, SOSex, dotPeek) and other languages. Your request is too broad for this site as it stands now. Aug 3, 2016 at 16:33
  • You might have a look on reverseengineering.stackexchange.com for tools these guys are using. However, they don't really like beginners over there. A question like this may easily be downvoted. Looking at the tags, IDA is possibly the most favorite tool for reverse engineering. Combine that with WinDbg for kernel debugging and you can already get very far I'd say. Aug 3, 2016 at 16:35


Your Answer

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