Suddenly I have a strange extra loading of a Opus Lister.
What is supposed to happen...at Windows Startup Opus, will load but with NO Lister (a blank Desktop).
What is happening... at Windows Startup Opus loads WITH a Lister on the Desktop. The Lister is not my saved Default Lister; it is similar but is not showing the same folders as my Default.
I can still run my custom Opus HotKey "C:\Program Files\Directory Opus\dopusrt.exe" /cmd GO NEW LASTACTIVELISTE and it is all OK with the correct folders showing.
I have done a search for all "Startup" items in drive C:\ and deleted any Opus items found but the extra Lister still loads at windows Startup.'
I un-checked "Launch directory Opus automatically on System startup".
I checked "Don't open any Listers".
I Restored an older backup of Opus (long before this problem started).
Still get the un-wanted Lister at Bootup.
I am suspecting the un-wanted Lister loading is taking place in the Registery but can't locate it.
Using Revo Uninstaller Pro, I did a complete un-install of Opus; ran CCleaner & Registry Mechanic (with a compact the registry) to clean out any leftovers.
Re-installed Opus & restored my settings... same problems an extra un-wanted Lister on boot up.
I just restored the backup of my original default Opus installation... same thing, an Opus Lister (but now the original factory default) is loading at startup even though the "Launch directory Opus automatically on System startup" is un-checked and "Don't open any Listers" is checked.
Disable Explorer Replacement and reboot. Do you get an Explorer window opening instead of an Opus window?
As a side note, running Revo Uninstaller or CCleaner at any hint of a problem will more likely cause more problems than solve them. They should be a last resort, not something used routinely.
Got it resolved. I used the 'ol "BRUTE FORCE" method of a Windows System Restore to the day before all this happened. It's fixed.
I suspect it was a Registry problem but may never know for sure.
Doing a system Restore or even a complete Drive Image restore is often faster then trying to find the exact problem; you know one of those "It takes 10 hours to find a 10 second fix" kind of thing. I have VERY good backups (14 removable drives) with a history going back over 9 years. I do a Macrium Reflect Drive Image each week on drive C:\ and individual folder backups on Drive D & E. This brings up another reason why I LOVE Opus... simply double-clicking on a Macrium Reflect backup file opens the whole thing directly in Opus; the restore is as easy as dragging the file (or folder) to be restored from the backup tree (in drive F) to drive C, D, or E where it is needed. Could not be easier.
As far as Registry Mechanic & CCleaner are concerned I can't live without them. I have seen a BIG improvement in performance from time to time and it is simply amazing how much junk they find and remove. Been using them for many years. My method is...
1: Run Registry Mechanic.
2: Run CCleaner (catches some items that RM misses.
3: Run RM again to pick up additional garbage.
4: Run RM "Compact the Registry".
I have seen as much as 10,000 (or more) pieces of C**P removed.
I ran the above scenario on a friends computer that was running very slow and it was amazing how much faster it was afterwords; he too is now a believer and does the weekly shuffle to keep things humming along.
My guess is that something else was launching a folder during startup and it would have opened whatever the default file manager was, not necessarily Opus.
I really doubt that manually cleaning/compacting the registry has any real effect on modern hardware, unless some setting is so wrong that it is causing timeouts/errors (which would be much more than a slight slow-down).
My solution to "10,000 pieces of junk in the registry" is to not install junk in the first place. But most registry cleaners massively exaggerate those numbers to make it look like they are doing something useful. (I gather that CCleaner is one of the better ones, and maybe it's not a bad program, but if you have to run something like that regularly then there's a bigger problem. And every time you run one of those programs which messes with other program's files and registry settings, you risk breaking things, because there is no way for those 'cleaner' programs to know for sure how the things they are modifying are really intended to work; they have to make assumptions or use files with rules for different known applications/files, which may change with new versions of those programs. Such tools can be useful but if you use them as magical "click button to fix unknown problems" tools then they're probably going to cause problems.)
They are very good at removing leftovers from uninstalled programs. Windows uninstaller does a very poor job at removing all files in a program, Revo does a much better job here but even then there is always some leftover junk; this is where RM & CCleaner come in. Neither of them has ever caused me any registry problems. They are also very good at cleaning up the endless junk that collects from web browsing and clearing out broken links & extensions from uninstalled programs.
They are also mandatory when cleaning up a new computer which most always comes with tons of junk already installed (depending on vendor). That's why I always build my own desktops; I control what is installed. I have seen some laptops speedup by a factor as much as 2X after uninstalling junk programs & running my cleaners.
I'm just very comfortable with my long time favorite cleaners & have had consistently good results but, to each his own.
But most registry cleaners massively exaggerate those numbers to make it look like they are doing something useful. (I gather that CCleaner is one of the better ones, and maybe it's not a bad program, but if you have to run something like that regularly then there's a bigger problem. And every time you run one of those programs which messes with other program's files and registry settings, you risk breaking things, because there is no way for those 'cleaner' programs to know for sure how the things they are modifying are really intended to work; they have to make assumptions or use files with rules for different known applications/files, which may change with new versions of those programs. Such tools