|
From: Jack on 4 Jul 2008 06:39 Hello, Sorry as I have also posted this in another NG, but lack responses. My question is When viewing what keys and dlls are associated with a process, how do you delete the whole lot of associated keys and files inside process explorer (when viewing them from the lower pane)? Thanks Jack
From: daniel on 4 Jul 2008 06:46 The question here is what is it that makes you think that you should delete them or what is the purpose ? //Daniel "Jack" <jl(a)knight.com> wrote in message news:%238R5MJc3IHA.1192(a)TK2MSFTNGP05.phx.gbl... > Hello, > Sorry as I have also posted this in another NG, but lack responses. > My question is > When viewing what keys and dlls are associated with a process, how do you > delete the whole lot of associated keys and files inside process explorer > (when viewing them from the lower pane)? > Thanks > Jack > >
From: Jack on 4 Jul 2008 07:00 I suspect if that is a malicious software... maybe :) But someone already told me that some dlls may belong to the kernel, so still in doubt that I should or shouldn't do this.... :) Thanks Jack
From: daniel on 4 Jul 2008 08:17 Fortunately Windows has a feature called "file system protection". If you delete or overwrite any system files, they will get recovered in an instant. Unfortunately the registry does not have such feature. Most of the files and keys used by any type of application pertain to the system. This means the system and other applications are relying on them. This means after you have deleted your malicious application and everything it uses there is not likely anything left on your system that still will work. Only if you are absolutely sure what you are doing and the files and keys you are deleting pertain to the program in question ONLY and are not shared by any other application then you could consider deleting them. The only reasonalbe way to get rid of unwanted application is Control Panel->Add/Remove Programs. //Daniel "Jack" <jl(a)knight.com> wrote in message news:Oic9$Uc3IHA.2060(a)TK2MSFTNGP02.phx.gbl... >I suspect if that is a malicious software... maybe :) > But someone already told me that some dlls may belong to the kernel, so > still in doubt that I should or shouldn't do this.... :) > Thanks > Jack > > >
|
Pages: 1 Prev: Updating file version number using UpdateResource Next: corrupt data from FindNextFileW |