Jump to content
|Topic||Stats||Last action by|
|How to pronounce "Israel"?||
|The Big Wrestling Thread!||
|Satya Nadella talks with Prime Minister of India about partnerships and employees||
|Default forum avatar image broken?||
|GNU / Linux December 2014 Desktops||
Posted 20 July 2014 - 16:35
Posted 23 July 2014 - 13:16
Posted 23 July 2014 - 19:34
Thanks BudMan. I've used Nirsoft's apps for some time - didn't remember that one.
But, not sure if it'll monitor installation processes, or only existing, running processes.
I need something to log reg changes made during installation process.
RegFromApp doesn't require any installation process or additional dll files. In order to start using it, simply run the executable file - RegFromApp.exe
After running it, select the process that you want to inspect, and click Ok. After clicking Ok, each time that the selected process writes a value into the Registry, the main window of RegFromApp will display the written value in Windows .reg file format. You can copy & paste the desired values to another Registry file, or alternatively, you can save the entire Registry changes into a .reg file by using the 'Save As' option.
I think the key here is, you must select a process from the RegFromApp UI.
The documentation mentions for Vista (I think), you must run RFA at the same authority level as the app to be monitored. Since most installers in Vista run in Admin mode, that would mean running RFA in admin.
I got / ran the 32 bit RegFromApp (first got the 64 bit ver; says must have 32 bit RFA ver for monitoring 32 bit apps).
Started it in NON admin mode, went to main menu, File > Start New Process, then browsed / selected a typical installer .exe file (not a running process). It accepted that.
But it didn't log anything during the selected app's installation or at the app's launch. That didn't surprise me, since it was mentioned RFA must run in same mode as apps to monitor.
But when starting RFA in Admin mode, the options are grayed out to Browse / select a new process (installer) that isn't yet running, to monitor for reg changes.
AFAIK, it is then impossible to select a process (installer) to monitor, that's not yet running.
Not sure if it's a bug, misinterpretation of what it can do or operator error.
Posted 25 July 2014 - 12:16