Windows 10: Can you confirm advanced recovery options work after upgrading to CU?

Hi, could you advise your experience of this please?

If you upgraded from the Anniversary Edition to the Creator's build, when you boot to the Advanced Recovery options (e.g. via SHIFT + left click Restart)

does clicking on the boxes for
- Command Prompt
- System Restore
- Startup Repair

fail or succeed?

I find I just get a logo screen and 'Please Wait' and haven't yet been able to repair this.
Just wondering if anyone else has seen this.

A clean install of the CU (using exactly the same source) is fine. Thanks!

:)

 

Windows 10 reset interrupted

I upgraded from Win 8.1 to Win 10 ages ago and it has worked fine until today, when the Video output failed. I got a BSOD that referred to some video driver (I think) and so after rebooting I tried to "Reset Win 10" using the Advanced Recovery Options.

During the "Reset" process, the Video (through HDMI) failed. I tried the onboard graphics (DVI) which wouldn't work either. I waited for about 30 mins before resetting the CMOS.

I then got the onboard graphics back but the system will only boot to the "Advanced Recovery Options" blue screen. I don't have an image to restore and the system doesn't recognize the USB port, for which I have a recovery usb stick. All other recovery options
return me to the "Advanced Recovery Options" screen.

What can I do? Can anyone please help.

thanks

 

Cannot get to advanced recovery options

So I recently caused an issue with my computer by messing up the startup applications. By doing this I someone disabled my ability to enter the password required to sign into my computer. My immediate thought is to do a system restore. I've tried multiple
options to this route but have not had much luck. First I cannot access the advanced recovery options through the boot up process. I've tried hitting F12, F8, F3, and even shift+F8. I used my laptop to create a recovery disk but I get a disk error when I insert
it into my desktop. Using this shift+restart process doesn't seem to do anything other than restart my computer also. So I'm wondering if someone perhaps had a solution to my issue. Thank you in advance.

 

Both the machines in 'My Computers' below have been upgraded from 1607 to 1703. I've never had cause to use Startup Repair, but I regularly use System Image Recovery on my test machine to swap between saved system images. Works fine in 1703.

I've just tried Command Prompt on my main machine (x64 1703 Home) with equal success.

 

Thanks. From a thread NavyLCDR & I worked on we haven't resolved my problem. I'll probably just leave it broken and move on.

 

Just checked 2 PC that were upgraded from 1607 to 1703 with shift + left click restart and both opened to choose an option with continue, troubleshoot, and turn off your PC.

One computer took more than 5 minutes and the other was within 1 minute.

 

Mm, there's a difference between having the options available (incl. Command Prompt, System Restore and Startup Repair) and them actually working.

I had all the options shown, but clicking e.g. Command Prompt in the Advanced Recovery screen => Please Wait, not a command prompt.

Would you mind checking that please?

Our experience in the thread leads me to think there's a chance more people may have this issue- few would be aware, as few would actually use them often. The error number I encountered (0xc0000454) in odd cases (not normal boot) is one not found on this forum but is reported.

 

Checked 3 computers.
All three opened to command prompt
choose an account to continue
forgot your password or don't see your account?

Once the passwords were entered each computer opened to Administrator: X:\Windows\system32.cmd.exe

0xc0000454 search is opening links with information similar to this:
How to Fix Boot Configuration Error Code 0xc0000454 on Windows 10?

 

Thanks, yes, I've seen that one.

I've tried rebuilding the BCD, the entire EFI partition, clean installing and replacing the Windows partition with an image of my current one - even an in-place upgrade repair install and one or two other things.

 

Just tried shift + left click restart with a 1703 clean install and it was nearly instant to the windows advanced troubleshooting.
I have one computer that failed to upgrade from 1607 to 1703 and all opened command prompt with Administrator X.

It's a puzzle that both clean install and in place upgrade did not fix the problem.

Spoke too soon. The 1607 that failed to upgrade is stuck on command prompt.
The 1607 that failed to upgrade is due to insufficient free space in the reserved partition.
In March I had had this problem with another computer. This was before the 1703 upgrade was available.

Just fixed it. It required using the keyboard up/down arrows. It opened to Administrator X



This link indicates NVRAM: ​Help! error 0xc0000454 : Windows10

 

Thanks, to be exact, the clean install itself was fine. And the upgrade from the AU completed with smoothly. It's finding a way to get my current Windows partition consistent with the recovery partition after the upgrade that's the problem.. (I've always used the same DVD for the CU in this- for the upgrade, the in-place upgrade install and the clean install - so that's probably not the problem).

 

If you diskpart two computers (one with the problem next to one that is normal) are there any differences? Are the sizes similar? I would need to read more on the topic as this is the first time I heard about the problem.



See this link it has a tool:

Fix 0xC0000454

I cannot tell whether it is a legitimate site or not.

 

Thanks for your interest. Here's the thread:
Creator's upgrade appeared ok, but Advanced Recovery functions fail - Windows 10 Forums

I don't have 2 Win 10 PCs unfortunately.

 

Yes, I subscribe to that thread but NavyLCDR seems to be giving all the help I could offer, so haven't felt I had much I could contribute. My only thoughts are that you problems with Reagentc and Bcdedit were already there in the 1607 (dormant, perhaps) before the upgrade to 1703.

 

Perhaps so- I'd have hoped either rebuilding the EFI partition or replacing the Windows partition after a clean install would have dealt with that.

Note: I'm not trying to re-open a discussion on my particular problem- merely wondering if anyone else had the same underlying symptom, given a page I'd read on error 0xc0000454.