5 replies to this topic

[MedEvil]

There are a bunch of tools and tricks to find missing or not needed files.
Does anyone know of tools or tricks to find missing, or wrong registry keys? Mostly missing.

To avoid confusion, i'm talking about registry keys from windows components, not registry keys from installable applications.

[Sha0]

Some components use .INF files from the \Windows\Inf\ directory, if that helps.

[Brito]

I use regmon (now processmon). You need to filter the right events and then you see the keys that a given program is expecting to find while functioning.

http://technet.micro...s/bb896645.aspx

[MedEvil]

And which are the right events?

I tryed Regmon on a freshly installed XP and it gives me tons of missing keys and values. So appearantly some keys/values have to be missing or should be missing.


Maybe it's really, that i just don't see the forest for all the trees that are in the way.
My main problem is, that i lack any kind of concept on, how to go about identifying what is needed and missing and what is missing but not needed.
Can anyone help with that?

Is there a way to do with the registry, what i do with files? Namely stack folders that are searched for a needed file in a specific order. With a bit of monitoring this gives a perfect list of all needed and missing files.

[Brito]

Start filtering before running the program to clean out all the system events. Repeat this filtering until the background seems stopped and waiting for you to run the program.

This is the trick to only get the registry entries from the program itself.

And I mean running the program fully installed, see the keys that are called while using the program that you're testing.

[MedEvil]

Nuno, thank you for tying to help, but i explicitly wrote in the first topic.

To avoid confusion, i'm talking about registry keys from windows components, not registry keys from installable applications.

As you see there is no program to start, there's a whole OS to start and the system events is what i'm after.