articleI wrote an article about this I wrote an article about thisan article about this 

scook

Anderton

scook
What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it.

Sometimes just renaming something will cause it not to be recognized, like calling is XonsoleChannel.dll.

I suppose that would work but if the problem persists, there would still need to physically move the file(s) to be sure, so why not move them first place? And in this case, there is a tool which scans and dives down directory structures so the files need to be moved out of the search path.

 
In this case, you'd want to remove it anyway. But there are instances where you don't want to delete something permanently, you just want it not to be recognized so you can re-enable it again. I wrote an article about this [http://www.harmonycentral...tor-quot/ba-p/34633749]  in relation to the Ueberschall Inspire libraries. The Inspire series can mix and match loops among other members of the family, but not non-Inspire libraries. So when using Inspire libraries I just rename the other ones, the Elastik engine doesn't recognize them, and I can go back to the usual libraries by changing the name back.
 
Another example is when I had 64-bit plug-ins for Sonar and 32-bit for other programs. Sometimes Sonar would scan the 32-bit plug-ins and accept those as the ones to use. I renamed them, re-scanned, Sonar latched on to the 64-bit versions, then I put the names back for the other programs but Sonar ignored them because it was now "keyed" to the 64-bit plug-in.