Hi, I did advise exporting disabled config if any in the windows registry.
quote:
regedit has changed appearance.
The menu on the left has changed to
HKEY_CLASSES_ROOT NAME Default TYPE RegSZ DATA
I do not know, when he got those changes. But by removing if disabled, it would not have happened. Since , it will delete the key , lf malware changed to create disabled config key. He did note about some specific trojan. The specified information on the trojan, could suggest that it will damage the av,mv, and also create some registry hacks. The information on this trojan, vary from site to site.
Regarding dependency walker, i came to know that the logs while creating profile on the particular application exe, would pinpoint where the error comes. it tries to solve by calling those components or keys , and if it could it solves, otherwise, marking as RED LINE in the bottom box.
For example, i did try and succeeded in some exes. But could not understand the thing from logs it create as it is in alphanumeric , and code like 0x00 keys.
coming to the core point, it takes some dlls for its analysis. Here i have a doubt. The system contain dlls and may be the exe also contains or utilizes this dll to run those applications. The dependency walker changes in the call of the program dll to execute the program, which other application has also using. or particularly dlls from its own program, i.e., depencency walker. This is where i have the doubt and expressed the moderators to see.
Normally trouble shoot the exe would fix most of the things. If i have a program that it was not executing, it is executing without any thing other than dragging the same to the DW window and create Start Profile by checking. The log we supply in the program profiling, only produces log for the all the operations and errors are shown as RED. The program updates frequently.
