Page 3 of 5 FirstFirst 12345 LastLast
  1.    3 Weeks Ago #21
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,057
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    Thanks- looks very promising- will investigate tomorrow.
    However, what has persuaded me to discount the 480Mb recovery partition to date is its apparent lack of content:
    Reagentc command is moving things in and out from the Recovery folder to C:\Windows\System32\Recovery
    NOTE:
    You need to set folder option to show protected operating system files to see them.
    reagentc /enable =====> moves Winre.wim to Recovery folder
    reagentc /disable =====> moves Winre.win to C:\Windows\System32\Recovery

    Apparently, when you run reagentc /setimage... The new Winre.wim might be deleted and shows empty in partition 5.
      My ComputerSystem Spec
  2.    3 Weeks Ago #22
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    I'll try selecting the second recovery partition and enabling that tomorrow, thanks. I have the wim file, which I generated specifically. I found it not present in C:\Windows\System32\Recovery; it now is, so I can see what happens quite easily when I run reagentc /enable
      My ComputerSystem Spec
  3.    3 Weeks Ago #23
    Join Date : Jul 2015
    Posts : 3,655
    10 Pro

    Quote Originally Posted by dalchina View Post
    I can see what happens quite easily when I run reagentc /enable
    Disable it first. Then set the location, then enable.

    I'm not sure why you didn't to as @LCDR suggested though on your other thread. It would get rid of all your pointless partitions and make sure all others were up to date.

    It is easy - backup C, delete all partitions and clean install, restore C.
      My ComputerSystem Spec
  4.    3 Weeks Ago #24
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    It is easy - backup C, delete all partitions and clean install, restore C.
    That's exactly what I did do. It's shown in the other thread and mentioned again.

    All my pointless partitions? How many do you think there are?

    There's one as far as I know, created when I subsequently did an in-place upgrade repair install.

    So what didn't I do that @NavyLCDR suggested?
      My ComputerSystem Spec
  5.    3 Weeks Ago #25
    Join Date : Feb 2016
    Maribor, Slovenia
    Posts : 8,204
    Windows 10 (Pro and Insider Pro)

    Quote Originally Posted by dalchina View Post
    That's exactly what I did do. It's shown in the other thread and mentioned again.

    All my pointless partitions? How many do you think there are?

    There's one as far as I know, created when I subsequently did an in-place upgrade repair install.

    So what didn't I do that @NavyLCDR suggested?
    Interesting thread dalchina...

    One question: did you try to fix boot problems with Macrium. I know it's one of the most reliable programs (in that area too), just don't know if it diggs into repair section of boot.
      My ComputerSystem Spec
  6.    3 Weeks Ago #26
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Yes in the first thread... it didn't help.

    This is a learning curve- which I could have done without really- all from when a smooth upgrade to the Creator's build led to the Advanced Startup options being unavailable.

    I have an entirely speculative idea- perhaps it was caused by my Anniversary build having an extra recovery partition remaining from an in-place upgrade repair many months before...

    Later on I'll try @topgundcp 's idea...
      My ComputerSystem Spec
  7.    3 Weeks Ago #27
    Join Date : Feb 2016
    Maribor, Slovenia
    Posts : 8,204
    Windows 10 (Pro and Insider Pro)

    Quote Originally Posted by dalchina View Post
    Yes in the first thread... it didn't help.

    This is a learning curve- which I could have done without really- all from when a smooth upgrade to the Creator's build led to the Advanced Startup options being unavailable.

    I have an entirely speculative idea- perhaps it was caused by my Anniversary build having an extra recovery partition remaining from an in-place upgrade repair many months before...

    Later on I'll try @topgundcp 's idea...
    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.
      My ComputerSystem Spec
  8.    3 Weeks Ago #28
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Quote Originally Posted by topgundcp View Post
    I have questions for you:
    1. if you open admin command, copy and paste: reagentc /boottore&shutdown /r /f /t 00
      Does it boot into recovery ?
    2. Is the disk layout still look like the screen you posted in the other thread with 2 recovery partitions (450MB and 480MB)?
      Attachment 155144
      According to suggestions from the thread, you changed from partitiion 5 to partition 1 with reagentc, which in my opinion is not correct. When you upgrade, windows creates an extra 450MB after C: and put a new Winre.wim there and set it to partition 5 (counting from left to right)
    Hi, @topgundcp
    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'

    Is the disk layout still look like the screen you posted in the other thread with 2 recovery partitions (450MB and 480MB)?
    Yes

    According to suggestions from the thread, you changed from partitiion 5 to partition 1 with reagentc, which in my opinion is not correct.
    The command to set the recovery partition to partition 5 fails, as WINDOWSRE does not exist under RECOVERY
      My ComputerSystem Spec
  9.    3 Weeks Ago #29
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    Quote Originally Posted by Bree View Post
    I had occasion to sort out booting to my recovery partition a while back. The GUID involved is the one shown by bcdedit as 'recoverysequence' for {current}. This should match the 'Boot Configuration Data (BCD) identifier' shown by reagentc /info

    Somehow I'd managed to change mine and it was booting to a quite different recovery environment. I used reagentc to find the correct GUID and bcdedit to set it to boot correctly. This was back in Anniversary update, in case of further problems I kept a record of the information back then, and the updated information after the upgrade to Creators Update.

    I've attached my records in case they are of help.

    Interestingly, I've since discovered how my other system manages to boot to the recovery environment despite having no recovery partition (apparently the free upgrade to 10 was unable to find anywhere to put one, being an MBR which already had four partitions). The Windows RE location is shown by reagentc as:
    \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE

    But partition 3 is my C: drive. The files that would normally be found in the recovery partition are instead in the hidden and inaccessible C:\Recovery folder, along with a 0 byte hidden file at the root of C: called $WINRE_BACKUP_PARTITION.MARKER
    @Bree
    Thanks, I'm missing
    recoverysequence {f1e6bbc2-051f-11e7-9da9-e89a8f988ded}


    Click image for larger version. 

Name:	1.jpg 
Views:	23 
Size:	31.5 KB 
ID:	155226
      My ComputerSystem Spec
  10.    3 Weeks Ago #30
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,463
    Win 10 Pro (1703)
    Thread Starter

    So, first considering topgundcp's idea of which recovery partition to select:

    I created a folder WindowsRE under Recovery in partition 5 (offline), booted and selected that partition as the recovery partition.

    I rebooted (SHIFT+ left click Restart)

    The Advanced startup options had the Win 10 white rectangle around them, but Command Prompt, System Restore and Startup Repair were missing.

    I discovered I still needed to run
    reagentc /enable

    This gave me all Advanced startup options and the missing BCD entry is now present, but...
    the PC still hangs on selecting e,g Command Prompt as before.

    Click image for larger version. 

Name:	1.jpg 
Views:	2 
Size:	64.4 KB 
ID:	155256

    Click image for larger version. 

Name:	2.jpg 
Views:	2 
Size:	37.9 KB 
ID:	155257
    Last edited by dalchina; 3 Weeks Ago at 10:05.
      My ComputerSystem Spec

 
Page 3 of 5 FirstFirst 12345 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:58.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums