Repair your computer option not working (restoring factory backup)

Page 4 of 21 FirstFirst ... 2345614 ... LastLast

  1. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #31

    What I see is that the recovery to factory settings doesn't change much to the bcd settings at all!!
    only this as a see with a quick compare.
    • it leaves the ramdisk options as it is
    • it leaves the winre settings as it is
    It only changes:

    id {current}
    recoverysequence {4ff2fcb5-a07f-11df-9201-a4badbd9db87}

    it is hardcoded!! It assumes the winre ID is already there and has number: {4ff2fcb5-a07f-11df-9201-a4badbd9db87}

    You can repair it by donig:
    bcdedit /set {current} recoverysequence {actual number of winre entry}
      My Computer


  2. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #32

    maybe there is a trick to change the winre ID in BCD to {4ff2fcb5-a07f-11df-9201-a4badbd9db87}
    ???
      My Computer


  3. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #33

    please delete the useless entries I told. After that post bcdedit /enum all output again
      My Computer


  4. Posts : 17
    Windows 7 Home Premium x64
    Thread Starter
       #34

    Are those 2 useless enteries are same as previous one ?
      My Computer


  5. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #35

    bcdedit /enum all shows you the windows recovery environment entry now {6425ee6e-5ca5-11e1-a48c-a4badbd9db87}
    As long you don't use reagentc it isn't changed. Even recovery to factory settings doesn't touch it.
    I don't know of any hack. It's definitely hardcoded wrong in recovery procedure!

    try:
    bcdedit /set {current} recoverysequence {6425ee6e-5ca5-11e1-a48c-a4badbd9db87}
    you can do it now. And you have to do it anytime you recover to factory settings. Can you still enter winre after doing the command in {current} so from within win7?
      My Computer


  6. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #36

    ussama said:
    Are those 2 useless enteries are same as previous one ?
    the 2 entries are left overs from previous reagentc command. So they are not the same
      My Computer


  7. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #37

    identifier {c26c3bcd-5c99-11e1-a582-a4badbd9db87}=>useless now!
    ------------
    identifier {c26c3bce-5c99-11e1-a582-a4badbd9db87}=>useless now!

    So

    bcdedit /del {c26c3bcd-5c99-11e1-a582-a4badbd9db87}
    bcdedit /del {c26c3bce-5c99-11e1-a582-a4badbd9db87}
      My Computer


  8. Posts : 17
    Windows 7 Home Premium x64
    Thread Starter
       #38

    Kaktussoft said:
    bcdedit /enum all shows you the windows recovery environment entry now {6425ee6e-5ca5-11e1-a48c-a4badbd9db87}
    As long you don't use reagentc it isn't changed. Even recovery to factory settings doesn't touch it.
    I don't know of any hack. It's definitely hardcoded wrong in recovery procedure!

    try:
    bcdedit /set {current} recoverysequence {6425ee6e-5ca5-11e1-a48c-a4badbd9db87}
    you can do it now. And you have to do it anytime you recover to factory settings. Can you still enter winre after doing the command in {current} so from within win7?


    YEs WIN RE IS ACcessible after entering this command(at that time useless entries are not deleted)
      My Computer


  9. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #39

    bcdedit /set {current} recoverysequence {6425ee6e-5ca5-11e1-a48c-a4badbd9db87}
    is the only thing to do in the future!! so put in a file and don't forget it!
      My Computer


  10. Posts : 17
    Windows 7 Home Premium x64
    Thread Starter
       #40

    Kaktussoft said:
    identifier {c26c3bcd-5c99-11e1-a582-a4badbd9db87}=>useless now!
    ------------
    identifier {c26c3bce-5c99-11e1-a582-a4badbd9db87}=>useless now!

    So

    bcdedit /del {c26c3bcd-5c99-11e1-a582-a4badbd9db87}
    bcdedit /del {c26c3bce-5c99-11e1-a582-a4badbd9db87}


    When I enter the Above del Commands
    Following result appears
    An unknown command was specified.
      My Computer


 
Page 4 of 21 FirstFirst ... 2345614 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:03.
Find Us