Creator's upgrade appeared ok, but Advanced Recovery functions fail

And did that solve your original problem?

It does sound like the BCD is messed up. You can rebuild the EFI System Partition. You would boot into Kyhi's Recovery Tools. Use MiniTool Partition Wizard to assign a drive letter to the EFI System Partition (on the second drive, it looks like). Let's say you give it T:. Reformat the EFI System Partition to FAT32. Then in a command prompt you would run:

bcdboot C:\Windows /s T: /f UEFI

Make sure the path in red is to your Windows installation as it appears in Kyhi's Recovery Tools - it might not get assigned C: so you might have to change the drive letter to match.

I've seen it where there are multiple BCDs in the EFI System Partition and you are doing the repairs to one BCD, but then the computer is actually booting with another BCD in the same EFI System Partition and you wonder, What the heck, I know I changed that but the computer isn't recognizing the changes!

At this point, I guess, if you really want the advanced boot menu, I would say the only alternative is to backup your current Windows partition with Macrium Reflect. Do a clean install of Windows 10 (delete every partition in front of your D: partition and install to the unallocated space). Then boot into Kyhi's Recovery Tools or Macrium Rescue and replace only the OS partition. You might have to run Macrium's utility to fix booting. Then try /setreimage to the recovery partition.

I don't sweat the recovery menu too much. Everything on it can be executed from a Windows 10 bootable USB drive anyway.

For unrelated reasons, I just did a clean install. Here's my BCD, I think the issue has something to do with the recovery enabled setting:

Code:

C:\Windows\system32>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {faed968a-8fe5-11e7-b49b-d8cb8a71f683}
displayorder            {default}
                        {current}
toolsdisplayorder       {memdiag}
timeout                 3

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=\Device\HarddiskVolume5
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=\Device\HarddiskVolume5
systemroot              \Windows
resumeobject            {faed968a-8fe5-11e7-b49b-d8cb8a71f683}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10 Office
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {faed9688-8fe5-11e7-b49b-d8cb8a71f683}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {faed9685-8fe5-11e7-b49b-d8cb8a71f683}
nx                      OptIn
bootmenupolicy          Standard

C:\Windows\system32>

So, interesting develop. Before I did the clean install, my recovery environment was broken too. So, I wiped my SSD with the exception of my old OS partition which was at the very end of the SSD (called Windows 10 in the BCD above). I then did a complete new install to the unallocated space, and named it Windows 10 Office in the above BCD.

I got a brand new EFI System Partition and Recovery Partition. So then I added the Windows 10 entry to the BCD using the BCDBOOT command. My recovery environment works just fine in the new Windows 10 Office installation, but it is still completely broke in the Windows 10 previous installation. I think it has something to do with the extra entries you see above in the Windows 10 Office section of the BCD that are not present in the Windows 10 section of the BCD.

I'm not that proficient with the workings of the BCD to fix it at this point :-(