Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
Looking for an program installer monitor or recorder

I'd like to record the changes that occur to my system between two points in time, including during a reboot. I have an application which is affected adversely by a reboot. It's easy to fix, I just run the installer and it "fixes" itself. But I'd like to know what is being overwritten. Could be reg, could be file, not sure. Thus the question.

There used to be a tool from Novell called Zenworks which came with a tool to record system changes. You used it to set up deployable applications. Does something similar exist today that I can download from somewhere? I.e. It has to have a consumer or open source price tag/


share|improve this question

marked as duplicate by Ƭᴇcʜιᴇ007, Nifle, 8088, Simon Sheehan, studiohack Nov 10 '11 at 16:09

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 1 down vote accepted

there are various ways to solve this.

procmon is good for monitoring what a process does, but it doesnt give you a summary of the changes to a system.

there are plenty of tools for that but the only free one i know is sysdiff from microsoft. its pretty old and will contain a lot of noise in the result, but it should do the job. you can run step one (analyse system), reboot, run step two (analyse and compare).

if you only want to compare registry changes "regshot" will do.

another attempt to troubleshoot your problem is to check whats run at windows startup (and breaks the application). you can use sysinternals autoruns for that, or usual places(like startup folder and "run" regkey) by hand

if your setup is a msi file you could let it write a logfile while repairing and check what file/regkey was missing (with msiexec.exe /i mysetup.msi /l*v c:\mylog.log)

another way would be (also only works with MSIs) is to repair it selectively and check if it works again. e.g. msiexec /fu mysetup.msi (only repair HKCU keys, if it works now the problem is a regkey) msiexec /fo mysetup.msi (repair missing files) etc etc

tell me if you need more information about a specific method, i'm just giving you an overview here. more details about every method would be a bit much to write now :)

share|improve this answer
Fantastic answer thank you. Setup is an exe, so the msi stuff won't help now, but actually that's really useful information for the future. Time to track down Sysdiff and regshot :) I'm used to the noise, ZenWorks would capture everything and then you'd selectively strip out stuff that wasn't related to the install. Learnt a lot about how app's work back then doing that. – Ian Oct 30 '11 at 22:20
regarding the exe, maybe its a msi inside. there are quite a few ways to extract it. the most simple and common is to just doubleclick it and check if a msi get extracted in your temp folder – weberik Oct 30 '11 at 22:24
Cunning, I will check that too! Thanks Ian – Ian Nov 1 '11 at 22:36

You can use ProcMon from SysInternals, to capture all the registry, file system and DLL operations. Using filters, you can zero in on what affects your application.

In the past, I used a much better targeted application called AppSight (now belongs to BMC software) to solve such issues, but it's a very expensive piece of software (> $100k).

ProcMon should do it for you.

share|improve this answer
If I had a 100k spare, I don't think I'd be so worried :) ProcMon may not help here as it has to tell me what happens duing the boot process. It will tell me what files and reg keys it changes, but I don't know if the installer is smart enough to only write changes to things that need changing. If that makes sense. – Ian Oct 30 '11 at 22:22

Not the answer you're looking for? Browse other questions tagged .