Reverse engineering an install on windows

In summary, this person needs to clone a working install of a program in order to figure out what components it has and where they are. He is facing a number of challenges such as software management being non-existent and proprietary programs that may require replacement disks.
  • #1
newjerseyrunner
1,533
637
Hello,
I'm in sort of a strange predicament. I need to figure out how to install a bunch of software that we don't have install programs for. They did at one time, but I think they've been lost by the employee before me or even before that.

Luckily though, I do have servers with the program installed on and I do have the licenses so I don't need to work around that. The problem I'm up against though, is how do I take an installed program and figure out where all of it's components are (executables, dlls, dependencies, registry entries, service hooks...) I'm quite unfamiliar with all of the nuances of MS Windows and know it's software management is pretty much non-existent.

I need to do this with a number of proprietary abandonware components.

It's MS Server 2008 if that's helpful.
 
Computer science news on Phys.org
  • #2
Windows uses the registry to associate all the components of a system.
There are not hard and fast rules about how that should be done though.
If you examine the registry content you will likely glean some useful information, but you might miss important entries that don't seem obvious.
If the products you want to use really are abandonware with no user support or documentation still in existence you could waste a lot of time getting nowhere.
 
  • #4
I would suggest contacting the manufacturer of the programs to see if they are willing to provide you replacement disks or a digital download for the software that you are looking for. This is your best option.

As rootone suggested, examining the windows registry is the other. Most of the settings for a program are stored in either HKCU or HKLM within the Software tree, but it could be else where too. You can search through that for your applications and export the relevant keys (I'd do a search for the name of the program/publisher as well. ) and attempt copying the program to another system. But if the software in question used an activation procedure, then this will most likley not work.

Pay extra if it comes down to it to get replacement disks, it's worth avoiding the windows registry.
 
  • #5
The issue isn't about paying, my company is perfectly willing to pay. The problem is that these are legacy systems and the companies that created the products literally don't exist any more. I have a nuclear option of simplying copying the VM, but I want a repeatable install procedure.
 
  • #6
Try copying the program folder then. I have several instances of the exact same issue at work, 25 year old instrument control systems in my case.
With the older programs, you may be able to get away with just copying the program and transferring it. Do you get errors if you just move the relevant subfolders from program files to a new system?
 
  • #7
Routaran said:
Try copying the program folder then. I have several instances of the exact same issue at work, 25 year old instrument control systems in my case.
With the older programs, you may be able to get away with just copying the program and transferring it. Do you get errors if you just move the relevant subfolders from program files to a new system?
Yeah, they were complicated systems that installed things all over the place. I'm really hoping I'm not stuck cloning VMs forever.
 
  • #8
What is it that this software accomplishes? Can you upgrade to a more modern software? The pain of transitioning may be less than that of whatever you are doing and are planning on doing.

BoB
 
  • Like
Likes rootone
  • #9
newjerseyrunner said:
Yeah, they were complicated systems that installed things all over the place. I'm really hoping I'm not stuck cloning VMs forever.
You'll have to use some process monitor software to figure out what the program on question is doing.
Here's Sysinternals' Process Monitor software
https://technet.microsoft.com/en-us/sysinternals/processmonitor

It will show you all the files/registry locations any program running on your system accesses. Filter by the process name and see what your application is doing and all the different files/locations it's using. Then make a list and copy the relevant data over to a new system. This is a slow, and rather painful process. Depending on how many different things your application hits, it might be infinitely simpler to clone your VM.

Give it a go, hopefully you'll get lucky.
 

1. What is reverse engineering an install on Windows?

Reverse engineering an install on Windows involves examining and understanding the code and processes used to install a software application on a Windows operating system. This can include analyzing the installation files, registry entries, and system changes made during the installation process.

2. Why would someone want to reverse engineer an install on Windows?

Reverse engineering an install on Windows can be useful for understanding how a particular software application works and identifying potential security vulnerabilities. It can also be used to create custom installation packages or to troubleshoot installation issues.

3. What tools are commonly used for reverse engineering an install on Windows?

There are many tools available for reverse engineering an install on Windows, including disassemblers, decompilers, and debuggers. Some popular options include IDA Pro, OllyDbg, and Dependency Walker.

4. Is reverse engineering an install on Windows legal?

In most cases, reverse engineering an install on Windows is legal as long as it is done for the purpose of understanding how the software works and not for commercial gain. However, it is important to check the terms and conditions of the software and seek permission from the developer before reverse engineering their product.

5. Are there any risks or challenges associated with reverse engineering an install on Windows?

Reverse engineering an install on Windows can be a complex and time-consuming process, especially for more advanced software applications. It also carries the risk of accidentally modifying or deleting critical files, which could potentially damage the operating system. Therefore, it is important to have a thorough understanding of the tools and processes involved before attempting to reverse engineer an install on Windows.

Similar threads

  • Computing and Technology
Replies
6
Views
1K
  • MATLAB, Maple, Mathematica, LaTeX
Replies
2
Views
829
  • Computing and Technology
Replies
18
Views
1K
  • Computing and Technology
Replies
12
Views
2K
  • Computing and Technology
Replies
5
Views
2K
  • Computing and Technology
Replies
9
Views
5K
Replies
4
Views
3K
  • Computing and Technology
Replies
5
Views
2K
  • Computing and Technology
Replies
4
Views
1K
  • Computing and Technology
Replies
12
Views
3K
Back
Top