Can someone test INSTALLWATCH

Hi everyone,
I have been using INSTALLWATCH from Epsilon squared to summarisize installation changes right from Win 98 days. It interfaced beautifully/seamlessly with XP , and also WIN 7 x64 till last week. From last week onwards I have been stuck at a certain key HKLM>SOFTWARE>wow6432node.... While in the ANALYSE mode InstallWatch detects all the entries in the node as ADDED fresh nearly ( 4 lakh) which is not true. Can some expert test this. In fact I have not been able to find a Superlative application like this in its category.

The application is available here.. InstallWatch Download - SoftSea
1.Install the program.
2. In the configure you can disable the disk scan
3. Check whether all the Registry is included.
4. (if it automatically does not start creating one after config)Press Snapshot to create one.
5.Press Analyse immediately. Logic demands that added, deleted, modified registries should be ZERO save one or two.

PS
1. I created two test keys , values , datas in the particular section of the Registry mentioned above before creating a snapshot. After creating it I checked the .iws Snapshot file (using Scintilla Reader) and confirmed that they are indeed present. But annoyingly after analysis the same entries are shown as added fresh.

2.This problem I am seeing only since last week, otherwise it operated seamlessly. I am sure the software will adapt to WIN 8 as well

Sorry to Bump. Can anyone confirm that he is using the software without issues

@ Doubtingthomas,

It seems "InstallWatch" is not 64-bits Registry compatible.
Like ZSoft Uninstaller: "As a 32-bit program itself, it cannot (as standard) 'see', for instance, the 64-bit part of the registry".
So a loop issue could come out in 'Wow6432Node' key [ 4 lakh thing...].
Please see aditional info:

Test 64-bit compatibility:
1- Create a new file with Windows Explorer between snapshots in \windows\system32 (to test file system snapshot);
2- creating a new registry key with Regedit between snapshots directly under KEY_LOCAL_MACHINE\SOFTWARE (to test registry snapshot).
3- If a given snapshot program doesn't list these newly created items in a snapshot comparison, then it can't see the whole 64-bit system.

When using the registry API in a 32-bit application, Wow6432Node acts like a symbolic link that loops back to the same 32-bit hive. It does not map into the 64-bit hive as you might think.

For example, walking the registry tree down to HKLM\Software\Wow6432Node in a 32-bit application loops back to HKLM\Software. The result is infinite recursion: HKLM\Software\Wow6432Node\Wow6432Node\Wow6432Node\..., etc.

If you want to view the 64-bit registry hive in 32-bit code you must open HKLM\Software using KEY_WOW64_64KEY. Do not try to open Wow6432Node; it will not work.

P.S.: If you wants see installation changes you can try 'System Explorer' snapshot feature. It works well with 64-bits based applications.

BTW: You can uncheck the keys: HKEY_CLASSES_ROOT, HKEY_CURRENT_USER and HKEY_CURRENT_CONFIG. In fact they are subkeys from HKEY_LOCAL_MACHINE and HKEY_USERS ...

@majoMO
Thanks for the reply. I would like to clarify on the following:-
1.The program worked perfectly until 2 weeks ago with all the registry included.
2.I created a particular entry before the snap shot , and it does show after the snapshot is created. Please look at my post under PS.
3.Why two sets of behavior, while taking snapshots and while doing analysis. If it did not register the node while taking the snapshot let it not register while doing te analysis, which is not true here.
4.The program is hardly 3.5mb and is vouched safe. CAn you run it personally and confirm...

@ Doubtingthomas,
I tried in Win 7, 64bits, under 'Toolwiz Time Freeze' virtualization.

- Done like your 2. point and 'PS' info;
- Can't reproduce your problem; none 'node' annoyance; and "entries are shown as added fresh" wasn't reproduced here also.

So can't help to understand your problem.

For your information I can now confirm that "InstallWatch" can do the work if you are installing/analyze 32bits based applications. If an application is 64bits native, it is unable to do an accurate work.

Hi majomo , Can you please test in real environment.If it is working for you , it should also for me. It was doing well till 2 weeks ago..

Doubtingthomas said:

It was doing well till 2 weeks ago..

Did you tried in a Win XP system? Since you are working in a 64bits it seems to me that "Wow6432Node" loop issue comes out soon or later. Such behaviour was common with many registry cleaners that couldn't handle with the 64-bit part of the registry: first they worked and some time later they freezed in that 'Node' key...
I don't believe that is needed to work in real environment to change their behaviour, but I'll do that and I'll say something about if reproduced your annoyance.

Hi,
Not tested yet?? Is it with the latest Windows updates??

C'mon someone. Would you not give it a try. Atleast give a solution. Thanks.