"Exclude Always" issues!

[augieboo]

I use to "Exclude Always" many registry keys detected as invalid by AU.
Although those excluded keys are stored in ignore list files, AU still detects and reports them as invalid.

For example, recently I've installed VS2005b2 using custom install. As a result AU detected many ProgIDs as invalid, probably because only part of VS was installed. The problem is that those registry entries are either required or recreated automatically whenever VS is running.
So I have to exclude all those entries from being detected by AU registry cleaner. Unfortunately AU ignores my exclusions still detecting them as invalid ProgIDs. BTW that not only happens with the specific ProgIDs, I've noticed that AU always redetects "some" of the excluded entries.

IMHO this behavior is really very annoying. I think that an advanced user should be able to exclude anything he wants to keep intact.

Is there any way I can order AU to really exclude those entries from being reported as invalid?

Regards

[hari]

Can you please let us know some of the entries ?

What was the ignore word that you added to the list ?

[augieboo]

Many (>20) of those keys are "openwithprogids" entries.

Code: Select all

Example:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cpp\OpenWithProgids
This one contains a REG_NONE entry, named "VisualStudio.cpp.8.0"

Some are similar to that one others are detected as missing ProgIDs.
As I said, I've just selected them in AU and used context menu "Exclude Always (never find again)" command to ignore them.
On next run, AU still detected them as invalid.

Many of those entries may be safe to delete. VS recreates them when it runs so every time I have to browse a huge list of found keys in AU if they cannot be ignored.

BTW I have not tried to put them manually in an ignore list, just used the context menu command. I still wonder why that works on most entries but not all of them.

AU is configured to "Thorough" scanning method with all scanning options selected.

[Cal]

Hi Inray, see if creating a .INI file in AU's directory folder "Ignore_Reg" will help. Example: CAL.INI

[augieboo]

Hmm, sorry Cal but I don't get it.
Do you mean check if Ignore_reg folder is writable or create a new ini with exclussion list?
If so, yes there is no problem. All excluded entries can be found in User.ini.
BTW I tried, to store them manually in a new Ignore_reg\xxx.INI file without any success.

Code: Select all

A part of User.ini follows...

HKEY_USERS\S-1-5-21-842925246-1645522239-725345543-1008\Software\Microsoft\VisualStudio\8.0\vsmacros\RecordingProject7\Path
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.asm\openwithprogids\VisualStudio.asm.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.asmx\openwithprogids\VisualStudio.asmx.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.aspx\openwithprogids\VisualStudio.aspx.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.c\openwithprogids\VisualStudio.c.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cpp\openwithprogids\VisualStudio.cpp.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cxx\openwithprogids\VisualStudio.cxx.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.def\openwithprogids\VisualStudio.def.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.h\openwithprogids\VisualStudio.h.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.hpp\openwithprogids\VisualStudio.hpp.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.hxx\openwithprogids\VisualStudio.hxx.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.idl\openwithprogids\VisualStudio.idl.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.inc\openwithprogids\VisualStudio.inc.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rc\openwithprogids\VisualStudio.rc.8.0
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.sln\.sln
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.srf\openwithprogids\VisualStudio.srf.8.0
HKEY_CLASSES_ROOT\.asa\OpenWithProgids\VisualStudio.asa.8.0
HKEY_CLASSES_ROOT\.asax\OpenWithProgids\VisualStudio.asax.8.0
HKEY_CLASSES_ROOT\.ascx\OpenWithProgids\VisualStudio.ascx.8.0
HKEY_CLASSES_ROOT\.ashx\OpenWithProgids\VisualStudio.ashx.8.0
HKEY_CLASSES_ROOT\.asm\OpenWithProgids\VisualStudio.asm.8.0
HKEY_CLASSES_ROOT\.asmx\OpenWithProgids\VisualStudio.asmx.8.0
HKEY_CLASSES_ROOT\.asp\OpenWithProgids\VisualStudio.asp.8.0
HKEY_CLASSES_ROOT\.aspx\OpenWithProgids\VisualStudio.aspx.8.0
HKEY_CLASSES_ROOT\.bmp\OpenWithProgids\VisualStudio.bmp.8.0
HKEY_CLASSES_ROOT\.c\OpenWithProgids\VisualStudio.c.8.0
HKEY_CLASSES_ROOT\.cpp\OpenWithProgids\VisualStudio.cpp.8.0
HKEY_CLASSES_ROOT\.cur\OpenWithProgids\VisualStudio.cur.8.0
HKEY_CLASSES_ROOT\.cxx\OpenWithProgids\VisualStudio.cxx.8.0
HKEY_CLASSES_ROOT\.def\OpenWithProgids\VisualStudio.def.8.0
HKEY_CLASSES_ROOT\.h\OpenWithProgids\VisualStudio.h.8.0
HKEY_CLASSES_ROOT\.hpp\OpenWithProgids\VisualStudio.hpp.8.0
HKEY_CLASSES_ROOT\.hta\OpenWithProgids\VisualStudio.hta.8.0
HKEY_CLASSES_ROOT\.htm\OpenWithProgids\VisualStudio.htm.8.0
HKEY_CLASSES_ROOT\.html\OpenWithProgids\VisualStudio.html.8.0
HKEY_CLASSES_ROOT\.hxx\OpenWithProgids\VisualStudio.hxx.8.0
HKEY_CLASSES_ROOT\.ico\OpenWithProgids\VisualStudio.ico.8.0
HKEY_CLASSES_ROOT\.idl\OpenWithProgids\VisualStudio.idl.8.0
HKEY_CLASSES_ROOT\.inc\OpenWithProgids\VisualStudio.inc.8.0
HKEY_CLASSES_ROOT\.js\OpenWithProgids\VisualStudio.js.8.0
HKEY_CLASSES_ROOT\.rc\OpenWithProgids\VisualStudio.rc.8.0
HKEY_CLASSES_ROOT\.res\OpenWithProgids\VisualStudio.res.8.0
HKEY_CLASSES_ROOT\.srf\OpenWithProgids\VisualStudio.srf.8.0
HKEY_CLASSES_ROOT\.txt\OpenWithProgids\VisualStudio.txt.8.0
HKEY_CLASSES_ROOT\.vbs\OpenWithProgids\VisualStudio.vbs.8.0
HKEY_CLASSES_ROOT\.WSF\OpenWithProgids\VisualStudio.wsf.8.0
HKEY_CLASSES_ROOT\.xml\OpenWithProgids\VisualStudio.xml.8.0
HKEY_CLASSES_ROOT\.xsl\OpenWithProgids\VisualStudio.xsl.8.0

Even though anything looks just fine, AU still detects all the above registry entries. It's not a new issue though. I've reported that twice in the past.

[Cal]

No, actually create the file with "Note pad."

[augieboo]

I did that Cal without any success.

[Cal]

OK, then the Acelogix team will have to check into the matter then. Sorry for your difficulty as I know with that many entries needing to be ignored can be very annoying!

[augieboo]

It seems that some entries with a specific format are always detected as invalid by AU. I’ve noticed this nasty behavior many times in the past. It is really very annoying and I had to stop using AU registry cleaner because of that.

Thanks for help Cal.

[hari]

Actually, it is because AU will not allow entries with '\fileexts\' to be ignored, as there is nothing wrong in deleting them.

Did you see any problems after deleting these entries ?

We will have to update AU to let these entries into the ignore list.

[augieboo]

Actually, it is because AU will not allow entries with '\fileexts\' to be ignored, as there is nothing wrong in deleting them.

Hari, besides "/FileExts/" segment, many other keys cannot be ignored too.

Did you see any problems after deleting these entries ?

As I said before the most annoying problem is that applications like VS recreate these entries whenever they run. That results to a very long registry key list when AU scans system. I'm sure you understand that reviewing a three - four pages list isn't that easy.

We will have to update AU to let these entries into the ignore list.

That would be great. Please make sure that anything can be ignored.

Thanks hari

[jazzbodepew]

Inray

I often have so many programs running I don't want to see all of them in Add/Remove..
Like in testing ACe Utilities ;I have shortcuts for 5 or 6 versions on the desktop..Only the latest one is in Add/Remove...

When I go to install the latest version I,first, copy the entire folder of the previous version to my main "ACE" folder and rename it with the version number(eg."Ace232")..
Now I uninstall the "ACE232"version and install the (eg.ACE242) version.
I can make a shortcut,on the desktop, to the "ACE232" exe..
Now I have both versions working, to compare, and the registry only reflects the newest version...

So;To make a short boring idea long and boring-

Backup and make a restore point
Copy the folder of your program to another directory
Clean the registry of its entries(to your satisfaction)
See if it will run properly from the copied folder
If it does uninstall the booger
Re-boot
Do an ACE cleanup
Run the program from the copied folder

This may not work on newer programs but might be worth a try as a workaround..

jazz.....................