Damaged Registry Repair and Recovery in Windows XP (Q318159)

The information in this article applies to:

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
SYMPTOMS

When a registry hive becomes damaged, your computer may become unbootable, and you may receive one of the following Stop error messages on a blue screen:

  • Unexpected Shutdown
  • Stop:0xc0000135
  • CAUSE

    Registry damage often occurs when programs with access to the registry do not cleanly remove temporary items that they store in the registry. This problem may also be caused if a program is terminated or experiences a user-mode fault.

    RESOLUTION

    NOTE : The hotfix that is described in this article automatically repairs the registry during startup, but does not display any notification of this process. If you import a damaged registry hive, you may receive a notification, and the recovery of the registry hive takes place as it imports.

    A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this fix.

    Although there is a fix- basicly they are recomending that you wait for sp1 which will be here soon to get a proper patch.

    News source: The Inquirer.net

    View: MS error page

    sorry to the Danes.... but ENGLAND 3-0!!!!!

    Previous Story
    Gnome 2.0 RC1
    Next Story
    Intel Application Accelerator 2.3.2135 Beta