RondonReverse Engineering Book a diagnosis
  1. Home
  2. Lost source code

guide · lost source code

Lost the source code? The executable still knows almost everything.

The program running on that machine carries nearly everything the system does. In most cases the logic can be recovered from the .exe or .dll and rebuilt as equivalent code that compiles and that you control again. How much comes back depends on the technology it was built with.

Updated November 19, 2026

Short answer

Can it be recovered?
In most cases, yes. Screens, business rules, calculations and data access come out of the executable itself.
Will it match the original?
No. Comments and most internal names are gone. You get equivalent code, tested side by side with the old system until the outputs match.
Where do I start?
Don't wipe or upgrade the machine the system runs on. Copy the whole folder, the database and the settings, and look for the code in the places listed below before hiring anyone.

0x01 · first step

First, don't make it worse

While the system runs, the most valuable copy you have is the installed one. Protect it before anything else.

  • Don't wipe, replace or upgrade Windows on the only machine where the system works before making a copy.
  • Copy the whole program folder: the .exe, .dll and .ocx files, .ini and .cfg files, report templates and the database folder.
  • Keep the original installer if there is one. It sometimes contains components the executable alone doesn't.
  • Write down the Windows version, where the database lives (on that PC or on a server) and who uses the system every day.
  • If you can, clone the disk of that machine. It is cheap and saves the project if the drive dies.

0x02 · where to look

Before paying anyone, look here

  • The old developer's computer or laptop, including drives sitting in a drawer.
  • Old emails with .zip or .rar attachments. Search for the system's name and the project extensions below.
  • USB sticks, CDs, file-server backups and cloud storage used at the time.
  • Old GitHub, GitLab, Bitbucket or SourceForge accounts.
  • The vendor contract. Some include source code escrow or handover of the source if the vendor shuts down.
  • The former developer or partner. Many people kept a copy and were simply never asked.
TechnologyProject files to look for
Delphi.dpr .dproj .pas .dfm
Visual Basic 6.vbp .frm .bas .cls
.NET (C#, VB.NET).sln .csproj .vbproj .cs .vb
C and C++.c .cpp .h .vcxproj .dsp .dsw

Found an old version, even outdated? It helps a lot. We compare it with the current executable and rebuild only what changed.

0x03 · by technology

What can be recovered, by technology

TechnologyWhat usually comes backEffort
.NET (C#, VB.NET)Almost everything, with class and method names. Very close to the original.low
Java and Android (APK)Almost everything in Java or Kotlin. Native libraries (.so) come back as pseudocode.low to medium
Electron and JavaScriptThe code comes out almost as written, sometimes minified.low
Packaged PythonMost of the logic, depending on the Python version.medium
DelphiComplete forms and components, event names and component SQL. Logic comes back as pseudocode and is rebuilt.medium to high
Visual Basic 6Complete forms. Logic depends on how it was compiled: P-Code recovers better than native code.medium to high
C and C++The logic, as pseudocode. The most demanding rebuild.high

Not on the list? We also work with Go, Rust, Flutter, iOS and macOS apps, firmware and old web systems.

0x04 · what never comes back

What never comes back, and why that's fine

The compiler throws away what was only there for people: comments, formatting, local variable names (in native code) and code that was never used. No technique brings that back, and anyone promising identical source code is promising the impossible.

What matters is code you control that does exactly what the old system does. During the rebuild we:

  • give business names to routines and variables (CalculateNetWeight instead of sub_401A30);
  • document every rule we find, including the ones that were never written down anywhere;
  • run the new and the old system with the same inputs until the outputs match.

0x05 · how it works

How it works

  1. Triage. You describe the problem in the form or by email. We reply with an initial technical assessment, no commitment.
  2. NDA and ownership. Before we receive any file, we sign a non-disclosure agreement and you confirm your company owns the software or is licensed to use it.
  3. Paid diagnosis, 3 to 5 business days. You get a report on what the system does, function by function and in business language, where the data lives, what is recoverable, the risks and a fixed price for the work. The report is useful even if you stop there.
  4. Work in milestones. Each milestone is tested side by side with the old system, with the same inputs, until the outputs match.
  5. Delivery and maintenance. Code that builds, documentation and, if you want, monthly maintenance: the system is no longer an orphan.

0x06 · what you get

What you get at the end

  • Source code that builds, in the language you choose: the original, on a current version, or a modern one such as C#/.NET.
  • A Git repository with the rebuild history.
  • Business-rule documentation written for non-programmers.
  • An equivalence test report comparing the old and new systems.
  • Build, install and release instructions.

.rdata · frequently asked questions

Frequently asked questions

How long does it take?

The diagnosis takes 3 to 5 business days. The timeline for the work depends on the size of the system and is in the diagnosis report, with the fixed price.

What do I need to send?

The program folder (executable, DLLs, OCX and settings) and, if possible, a copy of the database with test data. A two-minute video of someone using the system helps a lot.

Can you recover just one part?

Yes, and it is usually faster: we map only the routine that matters, such as a calculation, a report or a file reader.

Do you work with clients outside Brazil?

Yes. The work is remote, worldwide. Communication can be in English or Portuguese.

What if I only have the installer?

That works too. We extract the executable and components from the installer and start from there.

#entry · next step

Tell us about your case. We reply by email.

Tell us what the system is, what it was built with (if you know) and what is stuck. You get a technical answer, with no commitment. If it makes sense to go ahead, the next step is a paid diagnosis, 3 to 5 business days, with a report and a fixed price.

Full confidentiality, no judgment · NDA before the first byte · remote worldwide