Boot error loop -> /rebuildbcd error and cant set active volume
Solution 1
The answer is:
We have GPT disk and UEFI boot and NO active partition!
ESP - UEFI System partition is on volume 4 (format FAT32!).
You can assign a drive letter to volume 4 by selecting it and "ASSIGN" using diskpart.exe.
And the command for fixing:
bcdboot c:\windows /l sv-se /s N:
where N: is the drive letter of mapped volume 4 (could be another drive letter like G:, H:) and sv-se is locale for swedish in Sweden(?) could be sv-fi(?).
You could try Dual-boot Repair tool, "Automatic Repair" for fixing this on click. Download and unzip to any folder, then run it from there - the tool is portable (needs .NET 2 or 4 to be installed in booted OS so the tool cannot run from normal PE unless .NET 2 was added!).
EDIT: For a successful boot for Windows 8/10 from GPT disk there should be as minimum:
1) EFI System partition (FAT32) - very special partition
2) MS Reserved partition (not formatted) - even more special
3) OS partition (NTFS) - usual
Did you omit copying these partitions?
DISKPART> list par
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 300 MB 1024 KB
Partition 2 System 100 MB 301 MB
Partition 3 Reserved 128 MB 401 MB
Partition 4 Primary 60 GB 529 MB
Partition 5 Primary 50 GB 80 GB
Partition 6 Primary 49 GB 130 GB
for example. Partition 2 is EFI System partition, partition 3 is MSR.
EDIT2:
If you use external media with Windows 10 for fixing you should boot external media the UEFI way!
I assume Windows 10 on disk is 64-bit and external media is Windows 10 64-bit installation USB - correct?
What did you do to create the boot problem? Installed some software? Changed some setting? Windows update?
Please edit your question with details what action led to the problem.
Solution 2
Method 1:
Since you fixed your BCD store and now you are able to boot, I assume some kind of file corruption happened during the update process. If you are lucky, there's chance that windows have kept a shadow copy (a.k.a Last Know Good Configuration), which is a snapshot of the state of the system files, in which windows was able to boot successfully. But to make it possible on windows 10, you have to enable legacy boot menu in BCD, which allows for accessing advanced options upon boot by pressing F8. Follow the instructions:
1.Insert and boot from Windows 10 Installation Media.
2.When the screen to install windows appears, press Shift+F10 to open command line.
3.Assign a letter to your EFI system partition:
diskpart
select disk D (where 'D' is the disk number)
select partition P (where 'P' is your EFI partition, in your case 4)
assign letter N
exit
Note: Correct disk and partition numbers can be decided by enumerating disks and partitions, respectively by running following commands inside diskpart
context:
list disk
list partition
4.Active legacy boot menu by running:
bcdedit /store N:\EFI\Microsoft\Boot\BCD /set {default} bootmenupolicy Legacy
5.If you've got a success message, reboot and press F8 continuously until the boot menu appears.
6.If you see Last Known Good Configuration, choose it and press 'Enter'.
Warning!: Please consider that it reverts back your system files and settings to a previous state, so some settings may need to be reconfigured and some installed applications might no longer be installed.
Method 2:
If you don't see Last Known Good Configuration in Advanced Boot Menu, or it doesn't fix the problem, you can try to fix system files by DISM:
1.Insert and boot from Windows 10 Installation Media.
2.When the screen to install windows appears, press Shift+F10 to open command line.
3.If not already assigned, assign a drive letter to Windows Partition:
diskpart
select disk D (where 'D' is the disk number)
select partition P (where 'P' is your Windows partition)
assign letter C (Where 'C' is a free drive letter to assign)
exit
Note: Correct disk and partition numbers can be decided by enumerating disks and partitions, respectively by running following commands inside diskpart
context:
list disk
list partition
4.Run the following command and wait for it to complete succesfully:
dism /image:C:\ /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess
Note: C:\
is the drive letter of Windows partition, D:\
is the drive letter of installation media and :1
after install.wim is the index number of windows edition inside installation media and must correspond to the same windows edition installed. (e.g install.wim:2, install.wim:3,...)
Related videos on Youtube
fredrik
Updated on September 18, 2022Comments
-
fredrik almost 2 years
Background
After my sister's three months of vacation with no internet access, she got home and there were many updates for Windows 10 and Norton installed.
After reboot Windows didn't start. Instead "the boot configuration data is missing some required information" showed up.
I got a photo of it, but can't read the error code. It's something like0x0000
? The file is BCD though.To solve this, her dude added her SSD disk in his own computer and according to them some sort of repair process finished successfully.
Then he put her SSD back in her laptop, after Windows automatic repair process it got stuck and Windows complains about
RecEnv.exe
"memory could not be read" (RecEnv.exe
is Windows recovery environment).Here is my diskpart list
Things I've done
I have created a Windows 10 32/64bits UEFI GPT formatted bootable USB so I can get to the command prompt
Memory tests through HPs utility have passed
-
CHKDSK /R
passed; no bad sectors on all discs. -
Sfc /scannow
reaches verification 100% complete, but error:
Windows resource protection could not perform the requested operation
-
bootrec /fixmbr
ok -
bootrec /fixboot
ok -
bootrec /rebuildbcd
error:
The requested system device cannot be found
- After this I tried to assign volume 4 the FAT32 disc letter
N:
-
bcdboot bcdboot c:\windows /l sv-se /s N:
error:
cannot copy boot files
UPDATE
-
bcdboot bcdboot c:\windows /l sv-se /s N: /F ALL
BFSVC Error:
Failed to validate boot manager checksum (C:Windows\boot\EFI\bootmgfw.efi)!
Error code = 0xc1 Failure when attempting to copy boot filesSo something is wrong with
bootmgfw.efi
. How do I solve that?I copied the
bootmgfw.efi
fromX:\windows\boot\efi
to the same folder on theC:
partition and VOILA! then I was able tobcdboot bcdboot c:\windows /l sv-se /s N: /F ALL
Next problem Windows can't start because of
ntosext.sys
error code0x000007b
. Seems like the whole Windows has been messed up somehow.-
Yorkziea over 8 yearsIt seems that the repair of the disk on another computer messed up system files completely! Boot files but also kernel files and drivers. You can try: 1.) Fix component store using dism on offline image. 2.) offline sfc. Both operations are explained on Microsoft.com and other sites. 3.) After that just fix BCD with bcdboot.
-
fredrik over 8 yearsI have assigned letter N to this partition but can still not make any of the partitions active since they are not MBR discs according to command prompt. bcdboot c:\windows /l sv-se /s N works fine I tried to reboot after this but it didnt solve the problem
-
Yorkziea over 8 yearsThere is NO NADA ZERO NIX active partition on UEFI !!! There is ESP - EFI System partition on UEFI which holds boot related files for all possible OS like Windows, Linux e.t.c.
-
fredrik over 8 yearsokay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
-
fredrik over 8 yearsi65.tinypic.com/fxbclx.jpg See attached printscreen. MS Reserved partition (not formatted) must be equal to my partition 3. EFI System partition (FAT32) must be equal to my partition 2. OS partition (NTFS) must be equal to my partition 4. It looks okay to me so whats wrong then?
-
Yorkziea over 8 yearsMap EFI System to drive letter, say N:, then cd to N:\EFI\Microsoft\Boot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
-
fredrik over 8 yearsRenamed the bcd file and did "bcdboot c:\windows /l sv-se /s N:" but that didnt create a new bcd file in N:\EFI\Microsoft\Boot... Now windows complains about the missing bcd file when I try to boot. How do I create that bcd file in the N:\EFI\Microsoft\Boot folder?
-
Yorkziea over 8 yearsDid bcdboot finish with error message or success message? You should email about "bcdboot not being able to create BCD" to Microsoft support. You can always rename BCD.old to BCD and restore BCD as it was so Windows has a BCD. Eventually some kind of virus check would be usefull as there is no known case for me bcdboot not being able to create BCD or fix BCD! You could extend your question with "what created the problem" like you installed new software, you did something ...
-
fredrik over 8 yearsIt was successful and Windows automatic repair failed after reboot then I looked in diskpart again windows have removed the letter N assign I did. Doesnt I have to do something else to tell windows to look in N: when booting?
-
fredrik over 8 yearstried "bcdboot c:\Windows /l en-us /s N: /f ALL" then I got error message " BFSVC Error: Failed to validate boot manager checksum (c:\windows\boot\EFI\bootmgfw.efi)! Error code = 0xc1 Failure when attempting to copy boot files
-
Yorkziea over 8 yearsBCD does not store N: or C: it stores diskID + partitionID instead of a drive letter. There is no mapping at boot time.
-
fredrik over 8 yearscan my strange X:\windows partition somehow be the problem. please view my edited post
-
fredrik over 8 yearsIve rewrote everything from scratch please see first post
-
Yorkziea over 8 yearsCommented on Question post.