Frequently Asked Questions

VB Decompiler analyzes programs written in Visual Basic 5.0/6.0 and .NET (C#, VB.NET). It can restore source code (decompilation), disassemble native code, recover forms and user controls (.frm, .ctl), and allow you to edit string constants.

Yes, it supports all standard compiled binary types: EXE (Executables), DLL (Dynamic Link Libraries), and OCX (ActiveX Controls) for both VB6 (P-Code, Native Code) and .NET (C# and Visual Basic) platforms.

For .NET applications, yes — full support for x86 and x64 assemblies.
For Visual Basic 6.0, only 32-bit files are supported (since VB6 never produced 64-bit code).

No. VB Decompiler is specialized for Visual Basic 5.0 / 6.0 and C# .NET. If you try to open a Delphi or C++ file, it will warn you that the format is unsupported. However, we have internal tools for Delphi/FreePascal and offer this as a separate service. Just email us.

Success depends on compilation type:

• P-Code (VB6): High success rate (up to 85%). Logic is mostly restored.
• .NET (C#/VB.NET): Very high success rate (up to 95%). Code is decompiled into readable C#.
• Native Code (VB6): Medium success rate, hardest to decompile. You get a partially recovered Visual Basic code (up to 75% recovery).

The AI Helper (available in v12.6+) uses a LLM models in a local network (using Ollama with models like Qwen3) to post-process decompiled code. It can rename variables based on context, convert Goto jumps into While/For loops, and generally clean up the syntax. It requires a GPU with 8GB+ VRAM for best performance.

By default, VB Decompiler processes the entire file at once. For large projects, this takes time. "Fast Decompilation" mode processes only the procedures you explicitly open, making the tool work instantly even on huge files. You can toggle this in Options -> Advanced features.

In most cases, no. Compilers strip variable names to optimize file size. You will see generic names like var_10, etc. However, Forms, Controls, standard Events, and Public functions usually retain their original names.

Tracing lets you emulate the execution of any functions from the compiled VB6 program without running it. You can step through instructions, watch register values (EAX, EBX...), and see stack changes. This is safer than running malware in a debugger.

Yes. Use Tools -> String References to find all text strings. You can edit them directly. Note that the new string length cannot exceed the original length (due to binary file structure limitations).

Yes! You can export analyzed data (procedure names, entry points) to MAP files, IDC scripts (for IDA), or NAMET files (for HIEW). This helps you continue analysis in other debuggers and disassemblers.

VB Decompiler includes a generic 32bit unpacker only for simple packers (like UPX) and it works only in a 32bit version of Windows. If a file is packed, it will attempt to unpack it automatically. However, it can't help for custom packers or for a protected files.

• Single Developer License: For 1 person. Installation on 1 PC (physical or virtual) allowed. This license assigns to the developer' name and can't be transferred between developers or used by anyone other than the owner.
• Enterprise License: For companies. Installation on up to 20 PCs (physical or virtual) allowed. Using by up to 20 developers. If you require activating software on more than 20 PCs (or use by more than 20 employees), you need to procure additional licenses for these devices.

Both allow commercial use.

No. The Educational license is strictly for non-commercial home learning. It prohibits decompiling commercial / copyrighted software, malware analysis, and commercial usage.

Your license is perpetual for the version you purchased. You can keep using already installed software forever. But only on the PC, where you activated it during active license subscription. The subscription covers access to new updates and technical support. Also subscription allow you to movу the license to the new PC. You can renew your license at a discount price.