Boot error loop -> /rebuildbcd error and cant set active volume











up vote
1
down vote

favorite












Background



After my sisters three months of vacation with no internet access, she got home and many updates for Windows 10 and Norton installed.
After reboot Windows didnt start instead "the boot configuration data is missing some required information" showed up. I got a photo of it but cant read the error code its something like 0x0000?? 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 sucessfully.



Then he put the her SSD back in her laptop, after windows automatic repair process it stucked and Windows complains about RecEnv.exe "memory could not be read" (RecEnv.exe is Windows recovery enviroment).



Here is my diskpart list



Click here to see my Disk part list



Things Ive 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 have passed no bad sectors on all discs.

  • Sfc /scannow reaches verification 100% complete but "Windows resource protection could not perform the requested operation"


  • bootrec /fixmbr ok


  • bootrec /fixboot ok

  • bootrec /rebuildbcd "The requested system device cannot be found"


  • After this I've tried to assign volume 4 the FAT32 disc letter N:


  • "bcdboot bcdboot c:windows /l sv-se /s N:" -> "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:WindowsbootEFIbootmgfw.efi)! Error code = 0xc1 Failure when attempting to copy boot files



So something is wrong with bootmgfw.efi?! how to solve that?



I copied the bootmgfw.efi from X:windowsbootefi to the same folder on the C: partition and VOILA! then I was able to "bcdboot bcdboot c:windows /l sv-se /s N: /F ALL"



Next problem Windows cant start because of ntosext.sys error code 0x000007b.... :'( Seems like the whole windows have been messed up someway...










share|improve this question
























  • It 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.
    – snayob
    Jan 1 '16 at 18:58

















up vote
1
down vote

favorite












Background



After my sisters three months of vacation with no internet access, she got home and many updates for Windows 10 and Norton installed.
After reboot Windows didnt start instead "the boot configuration data is missing some required information" showed up. I got a photo of it but cant read the error code its something like 0x0000?? 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 sucessfully.



Then he put the her SSD back in her laptop, after windows automatic repair process it stucked and Windows complains about RecEnv.exe "memory could not be read" (RecEnv.exe is Windows recovery enviroment).



Here is my diskpart list



Click here to see my Disk part list



Things Ive 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 have passed no bad sectors on all discs.

  • Sfc /scannow reaches verification 100% complete but "Windows resource protection could not perform the requested operation"


  • bootrec /fixmbr ok


  • bootrec /fixboot ok

  • bootrec /rebuildbcd "The requested system device cannot be found"


  • After this I've tried to assign volume 4 the FAT32 disc letter N:


  • "bcdboot bcdboot c:windows /l sv-se /s N:" -> "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:WindowsbootEFIbootmgfw.efi)! Error code = 0xc1 Failure when attempting to copy boot files



So something is wrong with bootmgfw.efi?! how to solve that?



I copied the bootmgfw.efi from X:windowsbootefi to the same folder on the C: partition and VOILA! then I was able to "bcdboot bcdboot c:windows /l sv-se /s N: /F ALL"



Next problem Windows cant start because of ntosext.sys error code 0x000007b.... :'( Seems like the whole windows have been messed up someway...










share|improve this question
























  • It 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.
    – snayob
    Jan 1 '16 at 18:58















up vote
1
down vote

favorite









up vote
1
down vote

favorite











Background



After my sisters three months of vacation with no internet access, she got home and many updates for Windows 10 and Norton installed.
After reboot Windows didnt start instead "the boot configuration data is missing some required information" showed up. I got a photo of it but cant read the error code its something like 0x0000?? 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 sucessfully.



Then he put the her SSD back in her laptop, after windows automatic repair process it stucked and Windows complains about RecEnv.exe "memory could not be read" (RecEnv.exe is Windows recovery enviroment).



Here is my diskpart list



Click here to see my Disk part list



Things Ive 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 have passed no bad sectors on all discs.

  • Sfc /scannow reaches verification 100% complete but "Windows resource protection could not perform the requested operation"


  • bootrec /fixmbr ok


  • bootrec /fixboot ok

  • bootrec /rebuildbcd "The requested system device cannot be found"


  • After this I've tried to assign volume 4 the FAT32 disc letter N:


  • "bcdboot bcdboot c:windows /l sv-se /s N:" -> "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:WindowsbootEFIbootmgfw.efi)! Error code = 0xc1 Failure when attempting to copy boot files



So something is wrong with bootmgfw.efi?! how to solve that?



I copied the bootmgfw.efi from X:windowsbootefi to the same folder on the C: partition and VOILA! then I was able to "bcdboot bcdboot c:windows /l sv-se /s N: /F ALL"



Next problem Windows cant start because of ntosext.sys error code 0x000007b.... :'( Seems like the whole windows have been messed up someway...










share|improve this question















Background



After my sisters three months of vacation with no internet access, she got home and many updates for Windows 10 and Norton installed.
After reboot Windows didnt start instead "the boot configuration data is missing some required information" showed up. I got a photo of it but cant read the error code its something like 0x0000?? 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 sucessfully.



Then he put the her SSD back in her laptop, after windows automatic repair process it stucked and Windows complains about RecEnv.exe "memory could not be read" (RecEnv.exe is Windows recovery enviroment).



Here is my diskpart list



Click here to see my Disk part list



Things Ive 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 have passed no bad sectors on all discs.

  • Sfc /scannow reaches verification 100% complete but "Windows resource protection could not perform the requested operation"


  • bootrec /fixmbr ok


  • bootrec /fixboot ok

  • bootrec /rebuildbcd "The requested system device cannot be found"


  • After this I've tried to assign volume 4 the FAT32 disc letter N:


  • "bcdboot bcdboot c:windows /l sv-se /s N:" -> "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:WindowsbootEFIbootmgfw.efi)! Error code = 0xc1 Failure when attempting to copy boot files



So something is wrong with bootmgfw.efi?! how to solve that?



I copied the bootmgfw.efi from X:windowsbootefi to the same folder on the C: partition and VOILA! then I was able to "bcdboot bcdboot c:windows /l sv-se /s N: /F ALL"



Next problem Windows cant start because of ntosext.sys error code 0x000007b.... :'( Seems like the whole windows have been messed up someway...







boot windows-10 gpt bcd bcdedit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 30 '15 at 10:26

























asked Dec 26 '15 at 20:40









fredrik

6114




6114












  • It 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.
    – snayob
    Jan 1 '16 at 18:58




















  • It 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.
    – snayob
    Jan 1 '16 at 18:58


















It 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.
– snayob
Jan 1 '16 at 18:58






It 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.
– snayob
Jan 1 '16 at 18:58












2 Answers
2






active

oldest

votes

















up vote
0
down vote













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.






share|improve this answer























  • I 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
    – fredrik
    Dec 27 '15 at 15:54












  • There 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.
    – snayob
    Dec 27 '15 at 16:32










  • okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
    – fredrik
    Dec 27 '15 at 16:54










  • i65.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?
    – fredrik
    Dec 27 '15 at 17:16












  • Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
    – snayob
    Dec 27 '15 at 17:38


















up vote
0
down vote














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:EFIMicrosoftBootBCD /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:sourcesinstall.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,...)






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1018275%2fboot-error-loop-rebuildbcd-error-and-cant-set-active-volume%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    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.






    share|improve this answer























    • I 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
      – fredrik
      Dec 27 '15 at 15:54












    • There 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.
      – snayob
      Dec 27 '15 at 16:32










    • okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
      – fredrik
      Dec 27 '15 at 16:54










    • i65.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?
      – fredrik
      Dec 27 '15 at 17:16












    • Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
      – snayob
      Dec 27 '15 at 17:38















    up vote
    0
    down vote













    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.






    share|improve this answer























    • I 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
      – fredrik
      Dec 27 '15 at 15:54












    • There 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.
      – snayob
      Dec 27 '15 at 16:32










    • okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
      – fredrik
      Dec 27 '15 at 16:54










    • i65.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?
      – fredrik
      Dec 27 '15 at 17:16












    • Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
      – snayob
      Dec 27 '15 at 17:38













    up vote
    0
    down vote










    up vote
    0
    down vote









    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.






    share|improve this answer














    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.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 28 '15 at 19:16

























    answered Dec 27 '15 at 10:02









    snayob

    3,83111018




    3,83111018












    • I 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
      – fredrik
      Dec 27 '15 at 15:54












    • There 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.
      – snayob
      Dec 27 '15 at 16:32










    • okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
      – fredrik
      Dec 27 '15 at 16:54










    • i65.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?
      – fredrik
      Dec 27 '15 at 17:16












    • Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
      – snayob
      Dec 27 '15 at 17:38


















    • I 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
      – fredrik
      Dec 27 '15 at 15:54












    • There 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.
      – snayob
      Dec 27 '15 at 16:32










    • okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
      – fredrik
      Dec 27 '15 at 16:54










    • i65.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?
      – fredrik
      Dec 27 '15 at 17:16












    • Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
      – snayob
      Dec 27 '15 at 17:38
















    I 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
    – fredrik
    Dec 27 '15 at 15:54






    I 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
    – fredrik
    Dec 27 '15 at 15:54














    There 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.
    – snayob
    Dec 27 '15 at 16:32




    There 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.
    – snayob
    Dec 27 '15 at 16:32












    okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
    – fredrik
    Dec 27 '15 at 16:54




    okay if I understand you right UEFI doesnt use active/inactive settings.. So whats wrong then?
    – fredrik
    Dec 27 '15 at 16:54












    i65.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?
    – fredrik
    Dec 27 '15 at 17:16






    i65.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?
    – fredrik
    Dec 27 '15 at 17:16














    Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
    – snayob
    Dec 27 '15 at 17:38




    Map EFI System to drive letter, say N:, then cd to N:EFIMicrosoftBoot. Rename BCD to BCD.old. Then try bcdboot command again as in my answer.
    – snayob
    Dec 27 '15 at 17:38












    up vote
    0
    down vote














    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:EFIMicrosoftBootBCD /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:sourcesinstall.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,...)






    share|improve this answer

























      up vote
      0
      down vote














      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:EFIMicrosoftBootBCD /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:sourcesinstall.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,...)






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote










        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:EFIMicrosoftBootBCD /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:sourcesinstall.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,...)






        share|improve this answer













        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:EFIMicrosoftBootBCD /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:sourcesinstall.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,...)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 14 '17 at 17:39









        NetwOrchestration

        1,87211127




        1,87211127






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1018275%2fboot-error-loop-rebuildbcd-error-and-cant-set-active-volume%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Сан-Квентин

            Алькесар

            Josef Freinademetz