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

Hi, so I bit the bullet, and upgraded. All went well, and seemed ok until I tried to get into Safe Mode or a command prompt outside of Windows, for example.

All the options were there, but when my PC restarted - nothing. Had to power down.

All had worked fine with the Anniversary build- only failed after upgrading.
Have you seen this?

Currently preparing to reinstall Windows and copy back (restore from image) my updated Windows partition.

:)

 

CD/DVD Drive not recognised after upgrading to Win 10 Pro from Win 7 Pro - help

Brilliant! that did the trick, I just uninstalled Toshiba Recovery Media Creator and my drive appeared ok.

Thanking you,

Geoff

 

Getting my optical drives back after upgrading to Windows 10

Hi,

That Registry Fix is only for when the drives do not appear in Device Manager...

Are you running preinstalled Win 10, or is this an upgrade ?

The reason I ask is that Toshiba has a couple of features for creating Recovery Media that cause this after a upgrade...

If your Win 10 is a upgrade uninstall Toshiba Recovery Disk Creator and reboot...

If you have Toshiba Recovery Media Creator instead, uninstall that...

If you have both just uninstalling the Recovery Disk Creator may be enough...

After a upgrade they are most likely useless anyway...

 

Hi, some more information:

1. Can boot normally and into Safe Mode.
2. Attempting to boot to
- System Restore
- Command prompt
- Startup Repair

all give me a logo screen (my PC manufacturer)
+

Please Wait

- and nothing happens.

Now if I try a SHIFT left click restart from the lock screen before Safe Mode, I get an error which is reported:

/EFI/Microsoft/Boot/BCD

Status 0xc0000454

The boot configuration .......................................... contains errors.

When I clean installed the Creator's edition, Advanced recovery options worked.

They fail on
- my build upgraded from the Anniversary Edition (fully updated Creator's build)
- after restoring my fully updated Creator's build C: partition in place of that of a clean install of the Creator's build
- after an in-place upgrade repair install of that

Have tried
bootrec /rebuildbcd

Internet references to this error number (none on this forum!) indicate it is specially relevant to the Creator's Build rather than the Anniversary Build.

Note: Secure Boot is already disabled (found a reference suggesting that helped).

Startup Repair (run from installation DVD) (& which should be irrelevant as booting to Safe and Normal mode is ok) reports 'couldn't repair your PC'.

The log file (SrtTrail.txt) contains no errors.

Partitions:




The first partition on Disk 1 (data disk) was created in the upgrade. (No, I didn't open the laptop up and remove the SSHD before upgrading, never having had a problem before).

 

From a Command Prompt (Admin) or Powershell (Admin), what result do you get from:

reagentc /info

 

Hi, thanks - I did try reagentc /enable at one point

 

Well, one thing I am seeing is that reagentc (which manages the Windows Recovery Environment [WinRE]) is pointing to partition 5 of hard disk 1. That appears to be the incorrect location. Run diskpart and list disk. Then select disk # (replace # with the actual number of the disk) and then list part for each of the listed disks. That will tell you which "harddisk" number to use and which partition to assign as the recovery partition using reagentc /setreimage.

Your screenshot show disk 2 partition 1 as the proper recovery partition - but that might be interpreted differently than the barebones diskpart (and, therefore Windows itself) interprets the disk numbering and layout.

 

Makes sense. What do you make of the extra 128Mb partition on Disk 1?

I think I could assign a drive letter (e.g. R) to that recovery partition, then use this:
reagentc /setreimage /path R:\Recovery\WindowsRE

I can't work out the format of the command using "harddisk" number and partition number.
Disk 0:




Disk 1:

 

The extra 128 MB "partition" is not a partition - it is just unallocated space that has no partition assigned to it.

The format for reagentc /setreimage without using a drive letter is:
reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE

I would try that first. Partition 5 is also a Recovery partition, but the standard size and position for a Windows 10 recovery partition is the first partition and 450 MB.

 

Thanks, I did it by assigning a partition letter... so I now have



but still the same symptom.

 

I had this problem once on an earlier build and the problem was as described above. With careful analysis you can work out which is the correct recovery partition and designate that one. I used Minitool Partiton Wizard to check the file dates in the recovery partitions to select the correct one.

 

Thanks, it seems set now to the correct one of the two - correct size and content.




The other (odd size) seems to have no meaningful content:

 

And did that solve your original problem?

 

No.. still same symptoms as I said. If I run Macrium Fixboot it disassociates the recovery partition completely.

I feel there's something indicated by the 0xc0000454 message in addition to the recovery partition, but I've no idea what.

 

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!