Windows 10: Windows Boot Manager

I converted my partition from mbr to gpt using mbr2gpt.execmd. After that a new folder is created in C:Windows drive named 'EFI' which contains bcd,bootmgr stuff.

When i try to go into system recovery

'Boot Configuration Data file doesn't contain valid information for an operating system' this error occurs but pc boots normally.
Also bootrec /rebuildbcd showing 0 wimdows installation found

I looked up for solutions on web:

bcdedit /export c:\bcdbackupattrib c:\\boot\\bcd -r –s -hren c:\\boot\\bcd bcd.old bootrec /rebuildbcd


From this,second and third command doesn't work saying path not found to C:boot

My guess is that bcd should be mapped to this newly created EFI folder.

Any suggestions?

:)

 

Windows boot manager

There could be some system conflict triggered after the said changes. To help you with your concern, we suggest that you perform a clean boot. A
clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This will help to determine what is causing the issue on the Windows boot manager. To do this, click on this
link and scroll down to the
How to determine what is causing the problem by performing a clean boot section then follow the steps listed..

Note: If the installation is successful and the issue has been resolved. Please go through the section “How to reset the computer to start as usual” to reset your computer to the normal startup.

Let us know how it goes after performing the suggested steps.

 

Boot Process

Hi,

Please suggest me a link that can explain the boot process step by step of ...

• Windows 7,
• Windows 8.1,
• Windows 10,
• Windows Server 2008 R2 and
• Windows Server 2012 R2

With Regards

InTech

 

Partition management

Or at the very least, make sure that your hard drive boot order is correct, because it will take the first writable drive in the boot list to determine where to put the boot loader. As Jester suggested, pop the Windows install disk in, make sure your boot order is correct (or unplug the drive,) and run repair. It's really that simple.