I was wondering if anyone could help me.
As i am cleaning up my whole pc atm (was a real mess again) i'm having some problems removing some nasty dll's from programs wich i've installed and deinstalled a long time ago. When i try to remove them i get the famous message (won't be the same as in english versions of windows cuz it's my translating ) that the file is secured or in use. Well, if anyone has any advise on how to remove them id be really happy.
Annoying dll's
- bad_brain
- Site Owner
- Posts: 11638
- Joined: 06 Apr 2005, 16:00
- 19
- Location: In your eye floaters.
- Contact:
Hey Xonet...
Ok, here´s what I would do:
- clean your list of programs which startup together with XP (um, I assume it´s XP), you can find the lists by starting msconfig.
-clean your registry from entries you don´t need anymore, I do this with regcleaner, a real nice program, I´ll add it to the dl-section.
-clean the prefetch-folder: C:/Windows/Prefetch, you should do this anyway from time to time because it´ll speed-up the boot-time too. You can erase all in this folder, the needed programs will write a new entry into the folder at the next boot-up, so don´t wonder when it takes a little longer at the first time.
Ok,now check if the dlls are still not eraseable, if yes they´re maybe needed by other programs. To find out which programs handles the dll you can use Process Explorer, it gives you more information than the Windows Taskmanager and the user interface is much more comfy. You can even replace the TaskManager with it, but there is a little bug: If you changed the Path-variable because you develop Java-applications for example Process Explorer can´t be started (at least on my system). But well, you can change the path back to the system32-folder anytime.
Hm, I think that´s all for now, let me know if it worked...
Ok, here´s what I would do:
- clean your list of programs which startup together with XP (um, I assume it´s XP), you can find the lists by starting msconfig.
-clean your registry from entries you don´t need anymore, I do this with regcleaner, a real nice program, I´ll add it to the dl-section.
-clean the prefetch-folder: C:/Windows/Prefetch, you should do this anyway from time to time because it´ll speed-up the boot-time too. You can erase all in this folder, the needed programs will write a new entry into the folder at the next boot-up, so don´t wonder when it takes a little longer at the first time.
Ok,now check if the dlls are still not eraseable, if yes they´re maybe needed by other programs. To find out which programs handles the dll you can use Process Explorer, it gives you more information than the Windows Taskmanager and the user interface is much more comfy. You can even replace the TaskManager with it, but there is a little bug: If you changed the Path-variable because you develop Java-applications for example Process Explorer can´t be started (at least on my system). But well, you can change the path back to the system32-folder anytime.
Hm, I think that´s all for now, let me know if it worked...
well, i had allready done all those things before i made this thread (except the process explorer thing). As i have Ad-aware professional wich includes ad-watch i can see that explorer itself uses the dll's when i want to unload the dll's it simply doesn't respond, so that's kinda annoying since i would probobly be able to delete them when i shutdown explorer but then i don't know how to
- bad_brain
- Site Owner
- Posts: 11638
- Joined: 06 Apr 2005, 16:00
- 19
- Location: In your eye floaters.
- Contact:
Hm, strange, are you really sure the dll isn´t needed?
I tried to end all threads opened by explorer.exe with Process Explorer, and it worked without any problems, just right-click the process>properties and then you can kill the threads one by one. Let me know if it worked, if not post the name of the dll, maybe I can find out something....
I tried to end all threads opened by explorer.exe with Process Explorer, and it worked without any problems, just right-click the process>properties and then you can kill the threads one by one. Let me know if it worked, if not post the name of the dll, maybe I can find out something....