none
Root cause found: Registry is corrupt.

    Question

  • So I installed Win 8 on a machine I connect to my tv.. worked for a few weeks.. now it won't boot.. Windows 8 tries to do an auto repair.. a bunch of reboots occur and it finally says it can not fix it.. reviewing SrtTrail.txt I see the following:

    Root cause found:
    ---------------------------
    Registry is corrupt.

    I don't have a backup or any system restore points.. I wonder if I just have to suck it up and reinstall.. I still have no idea how the registry would become corrupted.  I went through all the options in the repair menu.. refresh/restore etc they all fail.. tried safe mode.. still fails.

    Full file:

    Startup Repair diagnosis and repair log
    ---------------------------
    Last successful boot time: ‎8/‎24/‎2012 6:05:32 AM (GMT)
    Number of repair attempts: 4

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = F:\Windows
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 422 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code =  0x0
    Time taken = 31 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code =  0x0
    Time taken = 93 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code =  0x0
    Time taken = 234 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 78 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 47 ms

    Root cause found:
    ---------------------------
    Registry is corrupt.

    ---------------------------
    ---------------------------
    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = F:\Windows
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 406 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code =  0x0
    Time taken = 46 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code =  0x0
    Time taken = 344 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code =  0x0
    Time taken = 780 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 15 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 281 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 172 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code =  0x0
    Time taken = 109 ms

    Test Performed:
    ---------------------------
    Name: Setup state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 577 ms

    Test Performed:
    ---------------------------
    Name: Registry hives test
    Result: Completed successfully. Error code =  0x0
    Time taken = 374 ms

    Root cause found:
    ---------------------------
    Registry is corrupt.

    Repair action: Registry roll back
    Result: Completed successfully. Error code =  0x0
    Time taken = 2871 ms

    ---------------------------
    ---------------------------
    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = E:\Windows
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 406 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code =  0x0
    Time taken = 46 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code =  0x0
    Time taken = 78 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code =  0x0
    Time taken = 234 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 63 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 47 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code =  0x0
    Time taken = 15 ms

    Test Performed:
    ---------------------------
    Name: Setup state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 234 ms

    Test Performed:
    ---------------------------
    Name: Registry hives test
    Result: Completed successfully. Error code =  0x0
    Time taken = 2075 ms

    Test Performed:
    ---------------------------
    Name: Windows boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Bugcheck analysis
    Result: Completed successfully. Error code =  0x0
    Time taken = 484 ms

    Test Performed:
    ---------------------------
    Name: Access control test
    Result: Completed successfully. Error code =  0x0
    Time taken = 11279 ms

    Test Performed:
    ---------------------------
    Name: File system test (chkdsk)
    Result: Completed successfully. Error code =  0x0
    Time taken = 24414 ms

    Test Performed:
    ---------------------------
    Name: Software installation log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Fallback diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Root cause found:
    ---------------------------
    Unspecified changes to system configuration might have caused the problem.

    ---------------------------
    ---------------------------


    • Edited by illafam Sunday, September 09, 2012 8:16 AM
    Sunday, September 09, 2012 8:07 AM

Answers

  • Hi, illafam

    Same issue in my dev lab. After 2 unsuccessful boot attempts Windows launched auto repair. After some time repair rebooted system and after that point OS can't boot anymore. SrtTrail.txt shows same error - registry is corrupt. 

    I've attached system volume to another lab and looked into system32\config system32\config\regback folders. Registry hives in both places were about 260 kb in size (typically they should be much bigger). Regedit mounted them without any errors but all hives were totally empty, i think  that's the reason OS couldn't boot.

    I tried to investigate what happened to registry and specifically to registry backup.
    Using freshly installed Win 8 OS I've noticed that backup registry hives in system32\config\regback folder were all 0 kb in size. Digging deeper I've found that registry backup is performed by system scheduled task RegIdleBackup which is configured by default to run every 10 days on Windows 7 (it can be found under Microsoft\Windows\Registry path), in my Win 8 lab I can see it didn't run yet. I suppose that's the reason regback folder contains no real backup files (if I run this task manually i can see registry is backed up). Moreover for some reason system protection was switched off by default in this freshly installed lab for system drive C:

    To see what will happen in this lab containing no real registry backup after auto repair runs I've performed hard reset a couple of times during normal OS boot. After second unsuccessful boot attempt auto repair launched, after it finished OS fails to boot with "registry is corrupt" error and registry files look similar to those in my previous lab both in system32\config and system32\config\regback folders, i.e. about 260 kb in size containing no reg keys.

    I think turning on system protection for system drive C: and running registry backup task manually after OS install might help to avoid this in the future. Additionally auto repair might be disabled with bcdedit tool: 
    bcdedit /set {default} recoveryenabled no
    • Edited by Ivan Andreyev Monday, October 01, 2012 5:48 PM scheduled task inacurate details
    • Marked as answer by Niki HanModerator Tuesday, October 09, 2012 2:06 AM
    Monday, October 01, 2012 5:24 PM

All replies

  • ugh... this was a big problem in Vista... dont tell me it is back.
    Monday, September 10, 2012 2:27 PM
  • I wonder if there is anything to do.. I tried f8 at startup to see if there was an option like last known good config.. I eventually found a menu for safe mode.. But that wouldn't load either.  I cant remember making any major config changes lately.. I may have swapped the video card out and went back to onboard video.. But it had been working since then..

    Monday, September 10, 2012 2:39 PM
    • Proposed as answer by Eric Sabotta Monday, December 03, 2012 3:55 PM
    Tuesday, September 11, 2012 8:17 AM
  • So I followed the steps, the time stamp on most of the files is August 23rd which was probably when it last worked correctly.  When I loaded up Windows 8 I selected advanced/command prompt.  My windows directory appears to be on the d:\ drive so I copied the files to d:\regbak

    Then I typed this:

        copy /y software  ..
        copy /y System  ..
        copy /y Sam ..

    After reboot there was no change, if I look on the root of d:\ now I see a Software, System and SAM file all at about 262,000 bytes.  Is this the correct procedure?

    I tried doing this through safe mode/command prompt but when I load it up it seems like the same repair console as before.

    ----UPDATE------

    I tried copying the software/system/sam files from d:\windows\system32\config\regbackup to d:\windows\system32\config and restarted, it still takes me to the repair wizard.  (I also had a usb stick for readyboost I have since removed)

    The SRT Log file has a different root cause now though:

    Root cause found:
    ---------------------------
    Startup Repair has tried several times but still cannot determine the cause of the problem.

    ---------------------------
    ---------------------------

    • Edited by illafam Tuesday, September 11, 2012 9:07 AM
    Tuesday, September 11, 2012 8:52 AM
  • i may be wrong but dont they need to go to windows\system32?
    Tuesday, September 11, 2012 8:31 PM
  • ugh... this was a big problem in Vista... dont tell me it is back.

    No, this was a big problem in XP. Fixed with NTFS TxF in Vista and Windows 7. Same kernel :o)

    Anway, I have also posted to Microsoft about 2 weeks ago about Windows 8 having recovery problems with the system core: http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/5b39e962-0ced-4756-984d-9800befba3ac

    ... and also like Illafarm mentions that he has no system restore points. That's why I advise in the link above that for reliability in case of such bugs in the recovery of the system core just after Windows 8 installation - there should be at least 1 system restore point created automatically. Then the auto-recovery would at least work in this case.

    ... I also wrote in the link above, that the system core got corrupted when I used a soft reboot. What seemed to confuse Microsoft in my post is, that I also wrote about a Windows Update - but that was not directly connected to the error. I just wrote that to indicate this happened before any Windows Updates had been installed (I did not reboot during a system update in progress or replacement of core files ... unless it was going on unadvertised at the desktop (would be a bug) ... but even in Win7 it should not be a problem with TxF?).

    Wednesday, September 12, 2012 12:58 AM
  • ugh... this was a big problem in Vista... dont tell me it is back.

    No, this was a big problem in XP. Fixed with NTFS TxF in Vista and Windows 7. Same kernel :o)

    Anway, I have also posted to Microsoft about 2 weeks ago about Windows 8 having recovery problems with the system core: http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/5b39e962-0ced-4756-984d-9800befba3ac

    ... and also like Illafarm mentions that he has no system restore points. That's why I advise in the link above that for reliability in case of such bugs in the recovery of the system core just after Windows 8 installation - there should be at least 1 system restore point created automatically. Then the auto-recovery would at least work in this case.

    ... I also wrote in the link above, that the system core got corrupted when I used a soft reboot. What seemed to confuse Microsoft in my post is, that I also wrote about a Windows Update - but that was not directly connected to the error. I just wrote that to indicate this happened before any Windows Updates had been installed (I did not reboot during a system update in progress or replacement of core files ... unless it was going on unadvertised at the desktop (would be a bug) ... but even in Win7 it should not be a problem with TxF?).

    I beg to differ... I could reproduce it on many machines of all types.  Most of the time, all i had to do was reboot.
    Wednesday, September 12, 2012 6:56 PM
  • Hi,

    It seems there is no solid solution for this issue. I suggest resetting or refreshing the computer.

     


    Niki Han

    TechNet Community Support

    Friday, September 14, 2012 7:56 AM
  • Hi, illafam

    Same issue in my dev lab. After 2 unsuccessful boot attempts Windows launched auto repair. After some time repair rebooted system and after that point OS can't boot anymore. SrtTrail.txt shows same error - registry is corrupt. 

    I've attached system volume to another lab and looked into system32\config system32\config\regback folders. Registry hives in both places were about 260 kb in size (typically they should be much bigger). Regedit mounted them without any errors but all hives were totally empty, i think  that's the reason OS couldn't boot.

    I tried to investigate what happened to registry and specifically to registry backup.
    Using freshly installed Win 8 OS I've noticed that backup registry hives in system32\config\regback folder were all 0 kb in size. Digging deeper I've found that registry backup is performed by system scheduled task RegIdleBackup which is configured by default to run every 10 days on Windows 7 (it can be found under Microsoft\Windows\Registry path), in my Win 8 lab I can see it didn't run yet. I suppose that's the reason regback folder contains no real backup files (if I run this task manually i can see registry is backed up). Moreover for some reason system protection was switched off by default in this freshly installed lab for system drive C:

    To see what will happen in this lab containing no real registry backup after auto repair runs I've performed hard reset a couple of times during normal OS boot. After second unsuccessful boot attempt auto repair launched, after it finished OS fails to boot with "registry is corrupt" error and registry files look similar to those in my previous lab both in system32\config and system32\config\regback folders, i.e. about 260 kb in size containing no reg keys.

    I think turning on system protection for system drive C: and running registry backup task manually after OS install might help to avoid this in the future. Additionally auto repair might be disabled with bcdedit tool: 
    bcdedit /set {default} recoveryenabled no
    • Edited by Ivan Andreyev Monday, October 01, 2012 5:48 PM scheduled task inacurate details
    • Marked as answer by Niki HanModerator Tuesday, October 09, 2012 2:06 AM
    Monday, October 01, 2012 5:24 PM
  • I had the same problem.

    I was able to use these instructions to solve the issue!

    My software hive had grown to over 1.8gb - I think it was the issue.

    Monday, December 03, 2012 3:56 PM