The author of MRUblaster has taken the super paranoid approach that all its users want all MRU lists wiped out. Wrong! In fact, I like the MRU lists for their ease-of-use provision. However, some lists end up with old, outdated, defunct, or invalid entries and I'd like to clear them out to start over. Does MRUblaster let me select the 1 or 10 entries that *I* want to clear? No, instead it defaults to preselecting all 300, or more, lists that it found in my registry. Can I highlight all the entries and then deselect them all (so I can then select just the few that I want to clear)? No, because I cannot select them all at once (nor is there a context menu to then let me toggle their selection). Is there a button to deselect all of the entries so I could then just select the few that I want to clear? No. The user is presented with a long list where all entries are preselected and manually having to deselect hundreds of entries one by one is the only way to clear just a select few that the user really wants to clear. So the primary and intended operation of MRUblaster is to blast away ALL lists despite it showing a super long list where the user could do all the manual deselects. All or nothing (or, All or "take a long time to deselect hundreds") mode is a poor choice for behavior. Also, no information is provided to relate the entry shown in MRUblaster's list with the registry key to which it belongs. So I really haven't a clue as to what registry key will get modified or cleared by a particular entry shown in MRUblaster's list. I dislike that Ad-Aware and Spybot never elucidate just exactly what change they intend to commit when removing a detected spyware product. I really dislike being treated like a moron user that is deliberately kept blind as to what registry keys will get deleted or cleared by MRUblaster. I want to know what you intend to change with your program - which registry key, what was the old value, and what will be the new value or if the registry key gets deleted. Why should I trust the author of MRUblaster if he/she won't trust us with our own property by letting us know exactly what is being claimed as an MRU list and what changes will be made in one of the most critical files of the operating system? Why even bother showing the user the list of all the supposed MRU lists found in the registry if you are going to hide which registry keys they belong and also not allow a decent method of selecting exactly which ones to clear? Good idea but incomplete implementation. Guess I'll keep hunting for a more useful, controllable, and informative solution. I want to brush the snow off my car's windshield and you give me a bulldozer!