Jump to content
JRosenfeld

Some SAS regkeys identified as Invalid AppID by jv16 regclea

Recommended Posts

I have SAS free 3.5,1016. As far as I can tell it is functioning correctly.

I was just testing the regcleaner app of Macecraft jv16 Power tools 2007 beta 3.

It flags the following SAS-created keys as 'Invalid AppID'

[HKEY_CLASSES_ROOT\ShellExecuteHook.SABShellExecuteHook]

@="SABShellExecuteHook Class"

[HKEY_CLASSES_ROOT\ShellExecuteHook.SABShellExecuteHook\CLSID]

@="{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}"

[HKEY_CLASSES_ROOT\ShellExecuteHook.SABShellExecuteHook\CurVer]

@="ShellExecuteHook.SABShellExecuteHook.1"

[HKEY_CLASSES_ROOT\ShellExecuteHook.SABShellExecuteHook.1]

@="SABShellExecuteHook Class"

[HKEY_CLASSES_ROOT\ShellExecuteHook.SABShellExecuteHook.1\CLSID]

@="{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}"

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}]

@="SABShellExecuteHook Class"

"AppID"="{C615554D-7B87-4275-84FF-8E0BA2AD071B}"

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}\InprocServer32]

@="C:\Program Files\SUPERAntiSpyware\SASSEH.DLL"

"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}\ProgID]

@="ShellExecuteHook.SABShellExecuteHook.1"

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}\Programmable]

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}\TypeLib]

@="{D01E70E5-2E5A-4EDC-B8A7-84FA45346E34}"

[HKEY_CLASSES_ROOT\CLSID\{5AE067D3-9AFB-48E0-853A-EBB7F4A000DA}\VersionIndependentProgID]

@="ShellExecuteHook.SABShellExecuteHook"

If those are false positives in jv16 I'd like to report that to Macecraft beta testing. However, I don't have an AppID {C615554D-7B87-4275-84FF-8E0BA2AD071B}, so I guess they are correctly flagged.

If they are invalid, then what needs fixing in the registry.

If they relate to some componet that is in SAS Pro but not in the free version it would be better not to have them created in the free install.

As an experiment I let jv16 delete them, and this did not seem to affect SAS that I could see (I then restored the keys, just in case).

Share this post


Link to post
Share on other sites

It sounds like the JV16 app is assuming creating things about the COM registration that are not actually required - that's why it's flagging those.

edited Pandato

Share this post


Link to post
Share on other sites

But then what is the purpose for creating the value

"AppID"="{C615554D-7B87-4275-84FF-8E0BA2AD071B}"

if it never gets referenced?

Deleting that value, jv16 is happy and does not flag the other entries.

Share this post


Link to post
Share on other sites
But then what is the purpose for creating the value

"AppID"="{C615554D-7B87-4275-84FF-8E0BA2AD071B}"

if it never gets referenced?

It's part of the registry script for the COM object - we may chose to use the AppId in the future, there is no harm in creating a key to an unreferenced GUID - nothing, expect registry cleaners, would be looking at that.

Share this post


Link to post
Share on other sites

OK, I understand about possible future usage, and agree that an orphaned entry in the registry does no harm.

However it will be likely to confuse those who do use registry cleaners. Although I rarely do so myself, I'm testing jv16 in anticipation of having to help out those who do.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...