Now, ShellBag Analyzer & Cleaner cannot find that CLSID any more on my XP computers. Why? I've cheated - I used CCleaner with Enhancer.
You removed all your ShellBags, including those of the "System" and '"Control Panel". I presume that your OS will recreate it while you are using your PC. Just a question of time. We will add an option in new ShellBag analyZer v1.6 enabling users to remove all ShellBags (for testing purposes).
I think it's a very good idea to give more choices for those, "living - dangerously" advanced users. Please, make sure that an average user does not have easy access to the option "Remove All ShellBags" , otherwise, all reviewers will start screaming, "I would not recommend it to my parents, friends, colleagues etc. - it can easily mess up your computer".
Hello, we've just released a new version of Shellbag AnalyZer + Cleaner Shellbag AnalyZer + Cleaner v1.6 http://privazer.com/download-shellbag-analyzer-shellbag-cleaner.php Changelog : - Fixed bug : unable to recreate Shellbags - Improved detection of . USB drive . Network drive . CD-ROM drive - New option for advanced users : . "Control panel" Shellbags cleanup . "Systeml" Shellbags cleanup -> "Desktop" Shellbag is protected - Improved UI . New "advanced Options" . New window size
Any user who wants to experiment with something like this should already have system and/or registry backups made. As long as a user has functional backups, there's no risk.
Thank you. Are you going to keep ShellBag AnalyZer & Cleaner as a separate program or, eventually, merge it with Privazer? "This features will also be included in PrivaZer pretty soon."
we've just released a new version of Shellbag AnalyZer + Cleaner Shellbag AnalyZer + Cleaner v1.7 http://privazer.com/download-shellbag-analyzer-shellbag-cleaner.php Changelog : - ShellBags integrity check
Thanks, quick feedback, test box XP SP3... This version did clean NAS related entries when the "Folders on network/external devices" options was checked. The cleaning of Truecrypt related test entries required enabling the "Existing folders" option. After performing a clean with all options checked, I still saw many keys under .../ShellNoRoam/Bags such as ../ShellNoRoam/Bags/5 ../ShellNoRoam/Bags/2 ../ShellNoRoam/Bags/2/Shell with no settings/values (don't seem to be a threat) but which make me wonder if the cleanup process is missing something that could be eliminated for thoroughness.
Downloading from your website it says from the properties for the file that I have 1.50. Then when I open, it says v1.6. However, I am trying to get v1.7. What is going on?
Hello, sorry for delay. We hope you will appreciate the new ShellBag AnalyZer + Cleaner version : ShellBag AnalyZer + Cleaner v1.8 http://privazer.com/download-shellbag-analyzer-shellbag-cleaner.php Changelog : - New option : ShellBags Optimization - Improved "Last visit" date recovery - Improved ShellBags selection - Improved UI
Nod32 did not like this file: -http://privazer.com/shellbag_analyzer_cleaner.exe- » UPX v13_m8 probably unknown NewHeur_PE virus Something else went off on it too, not sure just what, thinking sandboxie since Nod32 blocked it.
Thanks for the info. False positive from ESET Nod32. See here : ~ VirusTotal Results Removed per Policy ~ ESET contacted. Waiting for reply.
Here is the ESET reply ----------------------------------------------------- Dear Valued Customer, Thank you for reporting us this false positive. shellbag_analyzer_cleaner.exe - is OK and won`t be detected since next update of virus signature database ~Private message contents removed~
Today, I scanned my Vista laptop with HitmanPro. It detected one malicious software - ShellBag Analyzer & Cleaner.exe. Please be advised.
Please @focus try again with ESET Nod32. That should be fixed by ESET now. They have just emailed us.
As for (a), each app has opportunity to save MRU (most recently used) files and next time you use (for instance) Windows Media Player, if you click File}Open it might open to the directory containing the recently played file. For (b), I doubt the opened document would be referenced in an MRU entry. Only if you had right-clicked and used "OpenWith" from the (desktop, or windowsExplorer context menu) or if you had dragged the file's icon onto a player's icon to open it... that would create an entry in "Recent Documents". I'll say that I find it weird that, when browsed from the XP Start Menu, Recent only shows the last XX (count? or last xx days) worth of entries. If you browse to that folder (Documents and Settings}MyUsername}Recent) it may contain shortcuts to stuff you handled, dating all the way back to Day1 of installing the O/S. For (c), if that "long-lost" removable drive had a VolumeLabel, yes, a bag registry entry referencing it will probably still exist if, within Windows Explorer, Tools}View "remember the view settings for each folder" is checkmarked. Until reading your wonderment, I had never considered this to be a privacy issue -- I had always thought it "was awesome" that WinExplorer restored the selected columns/widths and sort order when I revisited a previously browsed directory (including root dir of a removable drive). HKCU\Software\Microsoft\Windows\Shell\Bags HKCU\Software\Microsoft\Windows\Shell\BagMRU HKCU\Software\Microsoft\Windows\ShellShellNoRoam\Bags HKCU\Software\Microsoft\Windows\ShellShellNoRoam\BagMRU I use Windows Explorer A LOT. Toward battling registry bloat, I have periodically navigated to each of these in regedit left pane, ctrl+a selectAll in right pane, and Delete. As far as I can tell, doing so in XP yields no unexpected negative side-effect. Yes, emptying the bags clears the remembered custom column widths + sort order for each target folder... but IMO clearing 5000+ accumulated bag entries (against 90K total regkeys) is good housekeeping. Each time Explorer fails in creating a regkey, the event is probably logged. I'll stick with the periodic bag cleaning approach.
Noob question, as I just learned about Shellbags... If I delete all shellbags, do I lose any "essential" functionality (e.g. persistent mapped network drives - used for scheduled backups), or are these entries largely for MRU type of capability (i.e. "nice to have" functionality).