Page 4 of 5 FirstFirst ... 2345 LastLast
  1.    3 Weeks Ago #31
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Quote Originally Posted by AndreTen View Post
    Have to read through your other thread (why did you separate them?).

    When topgun (or was it Navy..) suggested you to clean install and restore just C: partition, you said you did. But you didn't clean install, just did in-place upgrade. I could misunderstood, of course.
    I did a then b as per original thread.
    a. Clean install, (worked) then restored image of C:
    b. Subsequent to that I tried an in-place upgrade repair install (hence my two recovery partitions).

    (why did you separate them?).
    In this thread I was simply hoping to learn how this works, rather than investigate my particular problem.
      My ComputerSystem Spec
  2.    3 Weeks Ago #32
    Join Date : Feb 2016
    Maribor, Slovenia
    Posts : 8,204
    Windows 10 (Pro and Insider Pro)

    Quote Originally Posted by dalchina View Post
    I did a then b as per original thread.
    a. Clean install, (worked) then restored image of C:
    b. Subsequent to that I tried an in-place upgrade repair install (hence my two recovery partitions).


    In this thread I was simply hoping to learn how this works, rather than investigate my particular problem.
    Thanks Interesting debate, happy to learn from you guys
      My ComputerSystem Spec
  3.    3 Weeks Ago #33
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,057
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    if you open admin command, copy and paste: reagentc /boottore&shutdown /r /f /t 00
    Does it boot into recovery ?
    - that gives me a 454 'Unexpected error'
    This tells me that the BCD is partially corrupted.

    The commands: shutdown.exe /r /o /f /t 00
    or: %SystemRoot%\System32\Cmd.exe /c reagentc /boottore&shutdown /r /f /t 00
    should boot into Recovery if everything is configured correctly.
    FYI, If Windows is configured correctly:
    1. If Reagentc is disabled, you still can get into Recovery but with limited options.
    2. If Reagentc is enabled, you'll get all options.
    3. If you boot Windows using Recovery USB stick, You'll get into Recovery with couple of options missing.


    Here's my suggestion if you want to try:
    OPTION 1: Will save the trouble of re-install Windows.

    1. Download the image of my first 3 partitions (450MB Recovery, 100 MB EFI partition, and 16MB unformatted primary)
      EFI_Boot-00-00.7z - Google Drive
    2. Run Macrium and restore the image from step 1, overwriting your existing 1st three partitions, leaving C alone.
    3. Delete the 490MB Recovery partition.
    4. From Macrium, run fix boot problems.
    5. Reboot. Open Admin command prompt then run Reagentc /info to make sure that it is enabled. If not, enable it.
      if failed to enable, reboot and try again.

    OPTION 2: Assuming you've already had Windows backup with Macrium.

    1. Wipe out the first 5 parttiions. (450MB, 100MB, 16MB, C Drive, 480MB)
    2. Fresh install Windows 10
    3. Restore C drive from backup image, run fix boot problems
    4. repeat step 5 from OPTION 1 above.
      My ComputerSystem Spec
  4.    3 Weeks Ago #34
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Many thanks, will take a look when time permits.

    If the BCD data is corrupted, I'm surprised rebuilding the EFI partition, or clean installing and restoring the Windows partition didn't resolve this.
      My ComputerSystem Spec
  5.    3 Weeks Ago #35
    Join Date : Jul 2015
    Posts : 3,655
    10 Pro

    Quote Originally Posted by dalchina View Post
    I did a then b as per original thread.
    a. Clean install, (worked) then restored image of C:
    b. Subsequent to that I tried an in-place upgrade repair install (hence my two recovery partitions)..
    Are you saying that after you did a clean install you did a repair install and it made another recovery partition? That never happens - repair install (or upgrade) only makes a new partition if the existing recovery partition is too small (unless this is a new bug).

    It seems to me you didn't do a clean install - what you did was delete C. The installer found not enough space for recovery and made another. Back up C, delete all partitions and do it again.

    If you have one instance of WinRE.wim and it is registered then it will work (could be on C or on recovery partition).

    If you don't have WinRE.wim registered it won't work. There isn't much more to it than that really.

    The other possibility is you have to reset NVRAM but that is more a boot issue.
      My ComputerSystem Spec
  6.    3 Weeks Ago #36
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Thanks for your interest.

    As you suggest, I may just repeat the whole process again, as it makes little sense that a fully working clean install should lose access to the advanced startup options as a result of restoring the Windows partition, but not for the reason you suggest.

    Now I do know what a clean install is. I deleted all the Windows partitions on my SSD.
    All the partitions were thus replaced when I did a clean install.
    Following the clean install I had exactly the correct number of partitions.
    I did not only delete the Windows partition.

    I have done this procedure previously - a year ago- (Clean install and replace the Windows partition from and image)

    And finally, I did insert the installation DVD and progress through a normal installation process.

    Subsequent to having done all that, finding the advanced startup options now missing, I did the in-place upgrade repair install.

    That's the second time I've seen an in-place upgrade repair install create a second recovery partition (the other was a year ago or so).

    This time I know a bit more, so can try to investigate what's happening,
      My ComputerSystem Spec
  7.    3 Weeks Ago #37
    Join Date : Jul 2015
    Posts : 3,655
    10 Pro

    Quote Originally Posted by dalchina View Post
    That's the second time I've seen an in-place upgrade repair install create a second recovery partition (the other was a year ago or so
    The only difference between what you have done (and what works for me) is I made the partitions manually and made recovery 500MB and put it after C as recommended here UEFI/GPT-based hard drive partitions | Microsoft Docs

    Could be Windows Upgrade team doesn't talk to Install team.

    It is worth a try though. 500MB after C works for me (but then 450MB before C worked in the past too but I've not tried it on 1507).
      My ComputerSystem Spec
  8.    3 Weeks Ago #38
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,057
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    Quote Originally Posted by dalchina View Post
    Many thanks, will take a look when time permits.

    If the BCD data is corrupted, I'm surprised rebuilding the EFI partition, or clean installing and restoring the Windows partition didn't resolve this.
    Rebuilding the BCD will only fix boot problems, it does not fix the Recovery problem, you'd need to use reagentc for this.

    FYI, there's other programs, when run also modify the BCD. For example, when you run from admin command: reagentc /boottore
    an entry will be added to the BCD:
    bootsequence {31416d29-611c-11e6-8f31-90f4a30e3b92} ====> GUID of the Recovery partition.pointing the GUID of the Recovery partition so when you restart, Windows will get into the Recovery environment dirrectly.

    In addition, the file "ReAgent.xml" under: C:\Windows\System32\Recovery is modified with info as shown:
    When Eanabled
    <?xml version='1.0' encoding='utf-8'?>

    <WindowsRE version="2.0">
    <WinreBCD id="{00000000-0000-0000-0000-000000000000}"/>
    <WinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
    <ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
    ......

    When Disabled:
    <?xml version='1.0' encoding='utf-8'?>

    <WindowsRE version="2.0">
    <WinreBCD id="{31416d2b-611c-11e6-8f31-90f4a30e3b92}"/>
    <WinreLocation path="\Recovery\WindowsRE" id="0" offset="1048576" guid="{f32021c5-b6b3-4c83-8a3c-ad3d2eac74d0}"/>
    ......

    As you can see, Windows save all the info for the Recovery partition. So, when you re-enable it, it will set to the correct location.


    OPTION 1 mentioned above was used successfully to fix the exact same problem for a friend in the past.
      My ComputerSystem Spec
  9.    2 Weeks Ago #39
    Join Date : Feb 2016
    Maribor, Slovenia
    Posts : 8,204
    Windows 10 (Pro and Insider Pro)

    @dalchina
    Do you now this toy? Bootice

    See it somewhere and remembered this thread...
      My ComputerSystem Spec
  10.    2 Days Ago #40
    Join Date : Aug 2016
    S/E England
    Posts : 4,134
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by dalchina View Post
    None of my advanced recovery options (restart to Safe Mode, command prompt, startup repair, system restore) have worked since upgrading to the Creator's build. They were ok in the Anniversary build. The upgrade went smoothly.
    Remembering your problems, I tested advanced recovery after upgrading to Fall Creators Update. All working in 1709 as it was in 1703 (and 1607 before that).
      My ComputersSystem Spec

 
Page 4 of 5 FirstFirst ... 2345 LastLast


Similar Threads
Thread Forum
General Tips Open Command Prompt at Boot in Windows 10
How to Open a Command Prompt at Boot in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the...
Tutorials
Solved Unable to login to boot command prompt
Hi, I have just used the SHIFT-Restart option to activate the Windows 10 Troubleshooting and tried to open a command prompt. It asked for a password. I entered my password but was told it was incorrect. I booted normally using the PIN I...
General Support
Solved How to boot to a command prompt in Win10 ?
Tapping F8 or spacebar doesn't do anything ? I want to boot to command prompt only. I need to rename my user folder, in an attempt to get it named correctly, after the clean upgrade decided to drop the last character, which now gives me a...
General Support
SFC wont run from boot command prompt, says ....
SFC wont run from boot command prompt, says there are other pending actions and needs to reboot. Rebooting does no good. in other win OS this command, dism.exe /image:c:\/cleanup-image /revertpendingactions would fix this issue. Edit: I just...
General Support
Advanced Boot Options Menu (Choose an option)
The same trick from Windows 8/8.1 still works in 10. https://www.tenforums.com/tutorials/2294-boot-options-menu-open-windows-10-a.html Click on Start, click the power icon at the top of the Start Menu. Hold down Shift and click on Restart. ...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:56.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums