Typelib security bridge ("Viral" bug ?)

[Mark.Stewart]

000000000046 will duplicate in the registry when the bridge is broke, because it is a failsafe. The failsafe. Is it a choker that every time CCleaner runs a registry scan, cleans all, and this 000000000046 child mirror reappears? To quote our Horse's Engineer, "That Cleaner is one step away from viral." CC has the starch to actually remove the key for about 1/10,000 of a second. So if the CC key tag system can handle that, why can't it FAIL to report 000000000046 Typelib every time it runs UNLESS there is a legitimate bridge issue?

 

Usual excuse from Piriform is, "Gosh, it was Norton again!" Not. It was Windows. Thing is this, when the bridge gets banged up, CC's key tangle makes it instantly part of the problem. At an administration level redesigning interrupts at 1/10,000 of a second... wait, NO! at 1/20,000 of a second. verified on this box a few times, lol. IE11 readdresses back servers. And so does the kernel. Just a thought, eh.

 

Abstract::

 

Missing TypeLib Reference IBackupLocationsShellFolderImpl - {00020424-0000-0000-C000-000000000046} HKCR\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5} Mark

HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5} (Default) REG_SZ IBackupLocationsShellFolderImpl

HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}\TypeLib (Default) REG_SZ {00020424-0000-0000-C000-000000000046}

HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}\TypeLib Version REG_SZ 1.0

Key Name: HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}

Class Name: <NO CLASS>

Last Write Time: 130716 - 22:13

Value 0

Name: <NO NAME>

Type: REG_SZ

Data: IBackupLocationsShellFolderImpl

 

Key Name: HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}\ProxyStubClsid

Class Name: <NO CLASS>

Last Write Time: 130716 - 22:13

Value 0

Name: <NO NAME>

Type: REG_SZ

Data: {00020424-0000-0000-C000-000000000046}

 

Key Name: HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}\ProxyStubClsid32

Class Name: <NO CLASS>

Last Write Time: 130716 - 22:13

Value 0

Name: <NO NAME>

Type: REG_SZ

Data: {00020424-0000-0000-C000-000000000046}

 

Key Name: HKEY_CLASSES_ROOT\Interface\{F0E3A5D7-80C7-4228-90FE-61DF01C417A5}\TypeLib

Class Name: <NO CLASS>

Last Write Time: 130716 - 22:13

Value 0

Name: <NO NAME>

Type: REG_SZ

Data: {00020424-0000-0000-C000-000000000046}

Value 1

Name: Version

Type: REG_SZ

Data: 1.0

[Nergal]

uh, what?

 

this is unreadable I've no clue what you are talking about.

 

however the little I gathered it seems you a trying to remove a registry key and the key is the put back. I am assuming (as you mentioned Norton and listed a reg key that begins with I) that this key is related to your antivirus/security software.

Would you rather Norton were to clearly mark this key so ccleaner recognizes that it is not invalid...the consequences of that would indeed help Viruses to disable the key...I'm (sarcastically) sure that this is what you hope to achieve.

 

in seriousness, the general rule for registry cleaning, not just with ccleaner, is this: if you don't know for sure that it SHOULD be removed then you SHOULD NOT remove it from your computer. Registry cleaning has no benefit and major dangers so only remove what is safe.

 

You are correct, this is not a Norton or Windows problem. It, however, is also not a CCleaner problem; this is a user caused issue.

 

As far as ccleaner being "viral" maybe it's a translation issue but I see no sense in this claim.

 

Edit: I've never seen a horse's engineer, please provide a photograph of this person working on a horse's engine so I may be less boggled.

[mta]

@Mark, was there suppose to be a suggestion in there somewhere? (or were you just getting something off your chest?)

[Andavari]

I can't make any sense out of that first post. Therefore if you want any serious feedback re-post information in a more serious manner that we can understand.

 

I've never seen a horse's engineer, please provide a photograph of this person working on a horse's engine so I may be less boggled.

[Alan_B]

One horse engineer at work photo coming up

 

http://foter.com/photo/the-farrier/

[OnThePike]

While overwhelmingly and unnecessarily convoluted, I believe the OP was "simply" attempting to seek resolution of an issue with respect to deleting a registry key using CCleaner. In particular, the following key (which is part of Norton Internet Security’s Norton 360 Backup Package):

 

{00020424-0000-0000-C000-000000000046}

 

The scenario is as follows:

 

While scanning as usual, CCleaner displays a registry error that usually and ordinarily would be resolved by simply checking the “bad” key and attempting to delete it. CCleaner will then delete the registry key, however upon restart (or even recheck), the key will return because it’s locked by Norton as part of their tamper resistant permissions. This makes it impossible to use CCleaner to remove the entry, and the error will present itself upon each successive scanning of the registry.

 

The reason I am posting under this particular post is because it’s the most current of the many other posts relating and pertaining to the very same issue throughout these forums. However, in an effort to avoid necroposting, I chose the most current post (and unfortunately, the most incoherent, but I digress).

 

Because just about all of Norton is locked down (for safety and security reasons), deleting keys and/or files is almost impossible under normal operating conditions. Therefore, to remedy this situation, we must follow abnormal operating conditions; namely “Safe Mode”. Quite (and literally) simply, this issue can be resolved by restarting your computer in Safe Mode (or equivalent), running CCleaner in Safe Mode, deleting the offending key then restarting your computer. That’s pretty much it – problem solved.

 

The following steps resolved the issue for me running MS Windows Vista Home Premium on an HP Pavillion. Your particular keystrokes may differ:

• Close all running programs including those within the taskbar.
  
• Open Task Manager and kill the explorer.exe process (so nothing performed to this point is saved).
  
• Open and run CCleaner to eliminate all junk up to this point, then close it.
  
• Restart your computer.
  
• Press F8 (or whatever your equivalent is) to access the Safe Mode start-up options and select Safe Mode.
  
• Simultaneously, press and hold CNTRL + ALT + DEL to bring up your Home Options Screen.
  
• Select Start Task Manager.
  
• File -> New Task (Run) and type ccleaner.exe
  
• Registry -> Scan for Issues
  

When the offending key is returned, delete it as you normally would. Close CCleaner and restart your computer (by bringing up the Home Options Screen detailed above).

 

You should now be free of the bad key and the problem should be permanently resolved.

 

Hope this helps (1) clarify the original posting, and (2) help others who face the same problem.

 

Jeff