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.
Tools or tricks to find missing registry keys?
Started by
MedEvil
, May 17 2010 01:36 PM
5 replies to this topic
#1
Posted 17 May 2010 - 01:36 PM
#2
Posted 17 May 2010 - 01:44 PM
Some components use .INF files from the \Windows\Inf\ directory, if that helps.
#3
Posted 17 May 2010 - 02:08 PM
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
http://technet.micro...s/bb896645.aspx
#4
Posted 17 May 2010 - 04:10 PM
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.
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.
#5
Posted 18 May 2010 - 11:23 AM
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.
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.
#6
Posted 18 May 2010 - 11:26 PM
Nuno, thank you for tying to help, but i explicitly wrote in the first topic.
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.
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.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users