Registry Database Mutilation Using a Registry Cleaner

Posted by admin on February 8th, 2010 — Posted in Information Center, Web + Hub

MS registry mutilation using a registry cleaner:

A problem associated with registry cleaners is that some of them do not rate the severity of errors, and most that are able to do this incorrectly classify errors as critical, with diminutive reasons in support - a contemporary form of snake oil.

Discover the disadvantages using Registry Cleaners:

Critics question the validity of Registry Cleaners on the ground that there is no reliable method of assessing whether the third party application contains redundant information, invalid key or not.

Some Registry keys fail to identify used and unused key for Windows and could not determine the effects of deleting used key from computer.

Get a proven and trusted Registry Cleaner so you will avoid the disadvantages and instead get a fast XP

This has given rise to instances like system instability and/or loss of functionality, and subsequently, the release of application compatibility updates by Microsoft for blocking the registry cleaners causing problems.

Registry Cleaners have their own limitations for instance they cannot correct scenarios like undeletable registry keys owing to insertion of null characters in their names. Some specialized tools such as Sysinternals (now Microsoft) and RegDelNull utility can perform this task.

Potential to Recover:

Registry Cleaner could not repair those Registry hives which couldnt be mounted by the system.

Nevertheless, it can recover a corrupt registry in numerous ways backed by Microsoft; for example, Automated System Recovery, from a Last Known Good configuration, by enabling the setup to re-run or by deploying System Restore.

Malware elimination:

Despite all these problems, a corrupt registry can be recovered in several ways supported by Microsoft. For instance Automated System Recovery by using System Restore or by running setup from the Last Known Good boot menu.

Registry cleaners are unable to sense or flush out registry entries related to a rootkit that tends to conceal this fact from other procedures.

To draw a comparison between the results of Registry API and raw underlying Registry storage, a specialized tool is required.

Virtualization of application:

Registry cleaners fail to prove worthy in sanitizing registry entries related to virtualized applications as registry values in this case are written on a virtual registry that is application-specific in place of a real one.

Share this These icons link to social bookmarking sites where readers can share and discover new web pages.
  • OnlyWire
  • Socialize-It
  • Digg
  • del.icio.us
  • Furl
  • StumbleUpon
  • Netscape
  • YahooMyWeb
  • Reddit
  • Slashdot
  • Ma.gnolia
  • RawSugar

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.