using bootrec from within usb-booted winpe possible?












1















As mentioned here and here, bootrec.exe and bcdedit.exe have trouble functioning from a usb-booted WinPE environment. They tend to see the wrong sets of files and they also tend to break things (which I found out the hard way). As of yet, I have found no way to get them to see any file set other than that from which they were booted, IE not the WinPE environment. Booted from an actual disk, they work fine. It seems to be an issue with usb drivers in windows PE & RE from what little I was able to find. I have also tried gandalf50's (awesome) PE4 disk (found at http://windowsmatters.com/2014/05/15/standalone-win8-1update_pe-x64-or-x86-2/) with the same results.



I am a technician, though I still view myself as a novice. But I have built my own PE disks in the past and its not difficult at all. Why then does it seem impossible to get the functionality of these very necessary repair tools when the PE is booted via usb? I have found nowhere that describes a fix or any success stories or even anyone who has even attempted to get this to work. Personally, I run all my bootable tools from a single 250gb usb drive (setup with winsetupfromusb) and I greatly enjoy not being tethered to a CD/DVD binder anymore. Any help or knowledge on this matter would be greatly appreciated!



Edit: The bcdedit export operation fails. windows vista not booting The last post here contains a plausible fix. However, it requires that EasyBCD's iso caching method be used. I could re-do my huge drive with approx 30 bootable tools and this would work but its really a workaround in my mind. A creative solution regardless.










share|improve this question

























  • The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

    – Journeyman Geek
    Aug 31 '14 at 7:41













  • Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

    – Ben Bryan
    Aug 31 '14 at 19:38











  • np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

    – Journeyman Geek
    Sep 1 '14 at 1:42
















1















As mentioned here and here, bootrec.exe and bcdedit.exe have trouble functioning from a usb-booted WinPE environment. They tend to see the wrong sets of files and they also tend to break things (which I found out the hard way). As of yet, I have found no way to get them to see any file set other than that from which they were booted, IE not the WinPE environment. Booted from an actual disk, they work fine. It seems to be an issue with usb drivers in windows PE & RE from what little I was able to find. I have also tried gandalf50's (awesome) PE4 disk (found at http://windowsmatters.com/2014/05/15/standalone-win8-1update_pe-x64-or-x86-2/) with the same results.



I am a technician, though I still view myself as a novice. But I have built my own PE disks in the past and its not difficult at all. Why then does it seem impossible to get the functionality of these very necessary repair tools when the PE is booted via usb? I have found nowhere that describes a fix or any success stories or even anyone who has even attempted to get this to work. Personally, I run all my bootable tools from a single 250gb usb drive (setup with winsetupfromusb) and I greatly enjoy not being tethered to a CD/DVD binder anymore. Any help or knowledge on this matter would be greatly appreciated!



Edit: The bcdedit export operation fails. windows vista not booting The last post here contains a plausible fix. However, it requires that EasyBCD's iso caching method be used. I could re-do my huge drive with approx 30 bootable tools and this would work but its really a workaround in my mind. A creative solution regardless.










share|improve this question

























  • The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

    – Journeyman Geek
    Aug 31 '14 at 7:41













  • Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

    – Ben Bryan
    Aug 31 '14 at 19:38











  • np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

    – Journeyman Geek
    Sep 1 '14 at 1:42














1












1








1








As mentioned here and here, bootrec.exe and bcdedit.exe have trouble functioning from a usb-booted WinPE environment. They tend to see the wrong sets of files and they also tend to break things (which I found out the hard way). As of yet, I have found no way to get them to see any file set other than that from which they were booted, IE not the WinPE environment. Booted from an actual disk, they work fine. It seems to be an issue with usb drivers in windows PE & RE from what little I was able to find. I have also tried gandalf50's (awesome) PE4 disk (found at http://windowsmatters.com/2014/05/15/standalone-win8-1update_pe-x64-or-x86-2/) with the same results.



I am a technician, though I still view myself as a novice. But I have built my own PE disks in the past and its not difficult at all. Why then does it seem impossible to get the functionality of these very necessary repair tools when the PE is booted via usb? I have found nowhere that describes a fix or any success stories or even anyone who has even attempted to get this to work. Personally, I run all my bootable tools from a single 250gb usb drive (setup with winsetupfromusb) and I greatly enjoy not being tethered to a CD/DVD binder anymore. Any help or knowledge on this matter would be greatly appreciated!



Edit: The bcdedit export operation fails. windows vista not booting The last post here contains a plausible fix. However, it requires that EasyBCD's iso caching method be used. I could re-do my huge drive with approx 30 bootable tools and this would work but its really a workaround in my mind. A creative solution regardless.










share|improve this question
















As mentioned here and here, bootrec.exe and bcdedit.exe have trouble functioning from a usb-booted WinPE environment. They tend to see the wrong sets of files and they also tend to break things (which I found out the hard way). As of yet, I have found no way to get them to see any file set other than that from which they were booted, IE not the WinPE environment. Booted from an actual disk, they work fine. It seems to be an issue with usb drivers in windows PE & RE from what little I was able to find. I have also tried gandalf50's (awesome) PE4 disk (found at http://windowsmatters.com/2014/05/15/standalone-win8-1update_pe-x64-or-x86-2/) with the same results.



I am a technician, though I still view myself as a novice. But I have built my own PE disks in the past and its not difficult at all. Why then does it seem impossible to get the functionality of these very necessary repair tools when the PE is booted via usb? I have found nowhere that describes a fix or any success stories or even anyone who has even attempted to get this to work. Personally, I run all my bootable tools from a single 250gb usb drive (setup with winsetupfromusb) and I greatly enjoy not being tethered to a CD/DVD binder anymore. Any help or knowledge on this matter would be greatly appreciated!



Edit: The bcdedit export operation fails. windows vista not booting The last post here contains a plausible fix. However, it requires that EasyBCD's iso caching method be used. I could re-do my huge drive with approx 30 bootable tools and this would work but its really a workaround in my mind. A creative solution regardless.







bcdedit usb-boot winpe






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 20 '17 at 10:16









Community

1




1










asked Aug 31 '14 at 5:07









Ben BryanBen Bryan

1615




1615













  • The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

    – Journeyman Geek
    Aug 31 '14 at 7:41













  • Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

    – Ben Bryan
    Aug 31 '14 at 19:38











  • np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

    – Journeyman Geek
    Sep 1 '14 at 1:42



















  • The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

    – Journeyman Geek
    Aug 31 '14 at 7:41













  • Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

    – Ben Bryan
    Aug 31 '14 at 19:38











  • np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

    – Journeyman Geek
    Sep 1 '14 at 1:42

















The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

– Journeyman Geek
Aug 31 '14 at 7:41







The question is certainly fine, though I removed the pre-emptive rant and fixed up your formatting a tiny bit (Use either a blank line or a doublespace fpr a new line)

– Journeyman Geek
Aug 31 '14 at 7:41















Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

– Ben Bryan
Aug 31 '14 at 19:38





Thanks...I just get so tired of seeing bad answers to legitimate questions, I felt that a disclaimer/short rant was in order lol. It was late (early) when I posted this and I couldn't figure out why my paragraph formatting wasn't showing up, so thanks for clearing that up for me.

– Ben Bryan
Aug 31 '14 at 19:38













np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

– Journeyman Geek
Sep 1 '14 at 1:42





np. When you do find an answer that completely works, feel free to self answer. In addition, with your last edit, other than the selected answer other answers are in random order, so linking directly to the answer, and/or mentioning whose is it would be a great idea.

– Journeyman Geek
Sep 1 '14 at 1:42










1 Answer
1






active

oldest

votes


















0














This has been driving me crazy not having these in WinPE, not sure if this is published elsewhere but this is what seemed to work for me:




  1. Make sure you have a Windows Recovery/Installer CD that's the same bitness (x86/x64) as your WinPE image. If you don't, run the Windows Installer Creator to create a USB installer (I had to do this since my WinPE is x86).


  2. Once you have the USB installer, look for sourcesboot.wim. Copy this file somewhere, and then mount it with dism to view the contents:



    dism.exe /mount-wim /wimfile:c:pathtoboot.wim /mountdir:c:mount /index:1



  3. Next, find sourcesboot.wim on your WinPE drive, and copy that to a different location, and mount it to a separate directory with dism:



    dism.exe /mount-wim /wimfile:c:pathtowinpeboot.wim /mountdir:c:mount-winpe /index:1



  4. With both images mounted, copy these files/folders from the installer mount path (c:mount) to the mount path for WinPE (c:mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:




    • Windowssystem32bootrec.exe

    • Windowssystem32en-USbootrec.exe.mui

    • WindowsWinSxSx86_microsoft-windows-winre-tools.resources_31bf3856ad364e35_10.0.17763.1_en-us_150e215b68bd79cc

    • WindowsWinSxSx86_microsoft-windows-winre-tools_31bf3856ad364e35_10.0.17763.1_none_5ea4ec160fde2af5



  5. Commit the WinPE image with:
    dism.exe /unmount-wim /mountdir:c:mount-winpe /commit


  6. Finally, copy the boot.wim back into the sources folder on the WinPE drive, then boot into WinPE and test that it's working with bootrec /? and bootrec /scanos.







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',
    autoActivateHeartbeat: false,
    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%2f805311%2fusing-bootrec-from-within-usb-booted-winpe-possible%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    This has been driving me crazy not having these in WinPE, not sure if this is published elsewhere but this is what seemed to work for me:




    1. Make sure you have a Windows Recovery/Installer CD that's the same bitness (x86/x64) as your WinPE image. If you don't, run the Windows Installer Creator to create a USB installer (I had to do this since my WinPE is x86).


    2. Once you have the USB installer, look for sourcesboot.wim. Copy this file somewhere, and then mount it with dism to view the contents:



      dism.exe /mount-wim /wimfile:c:pathtoboot.wim /mountdir:c:mount /index:1



    3. Next, find sourcesboot.wim on your WinPE drive, and copy that to a different location, and mount it to a separate directory with dism:



      dism.exe /mount-wim /wimfile:c:pathtowinpeboot.wim /mountdir:c:mount-winpe /index:1



    4. With both images mounted, copy these files/folders from the installer mount path (c:mount) to the mount path for WinPE (c:mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:




      • Windowssystem32bootrec.exe

      • Windowssystem32en-USbootrec.exe.mui

      • WindowsWinSxSx86_microsoft-windows-winre-tools.resources_31bf3856ad364e35_10.0.17763.1_en-us_150e215b68bd79cc

      • WindowsWinSxSx86_microsoft-windows-winre-tools_31bf3856ad364e35_10.0.17763.1_none_5ea4ec160fde2af5



    5. Commit the WinPE image with:
      dism.exe /unmount-wim /mountdir:c:mount-winpe /commit


    6. Finally, copy the boot.wim back into the sources folder on the WinPE drive, then boot into WinPE and test that it's working with bootrec /? and bootrec /scanos.







    share|improve this answer






























      0














      This has been driving me crazy not having these in WinPE, not sure if this is published elsewhere but this is what seemed to work for me:




      1. Make sure you have a Windows Recovery/Installer CD that's the same bitness (x86/x64) as your WinPE image. If you don't, run the Windows Installer Creator to create a USB installer (I had to do this since my WinPE is x86).


      2. Once you have the USB installer, look for sourcesboot.wim. Copy this file somewhere, and then mount it with dism to view the contents:



        dism.exe /mount-wim /wimfile:c:pathtoboot.wim /mountdir:c:mount /index:1



      3. Next, find sourcesboot.wim on your WinPE drive, and copy that to a different location, and mount it to a separate directory with dism:



        dism.exe /mount-wim /wimfile:c:pathtowinpeboot.wim /mountdir:c:mount-winpe /index:1



      4. With both images mounted, copy these files/folders from the installer mount path (c:mount) to the mount path for WinPE (c:mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:




        • Windowssystem32bootrec.exe

        • Windowssystem32en-USbootrec.exe.mui

        • WindowsWinSxSx86_microsoft-windows-winre-tools.resources_31bf3856ad364e35_10.0.17763.1_en-us_150e215b68bd79cc

        • WindowsWinSxSx86_microsoft-windows-winre-tools_31bf3856ad364e35_10.0.17763.1_none_5ea4ec160fde2af5



      5. Commit the WinPE image with:
        dism.exe /unmount-wim /mountdir:c:mount-winpe /commit


      6. Finally, copy the boot.wim back into the sources folder on the WinPE drive, then boot into WinPE and test that it's working with bootrec /? and bootrec /scanos.







      share|improve this answer




























        0












        0








        0







        This has been driving me crazy not having these in WinPE, not sure if this is published elsewhere but this is what seemed to work for me:




        1. Make sure you have a Windows Recovery/Installer CD that's the same bitness (x86/x64) as your WinPE image. If you don't, run the Windows Installer Creator to create a USB installer (I had to do this since my WinPE is x86).


        2. Once you have the USB installer, look for sourcesboot.wim. Copy this file somewhere, and then mount it with dism to view the contents:



          dism.exe /mount-wim /wimfile:c:pathtoboot.wim /mountdir:c:mount /index:1



        3. Next, find sourcesboot.wim on your WinPE drive, and copy that to a different location, and mount it to a separate directory with dism:



          dism.exe /mount-wim /wimfile:c:pathtowinpeboot.wim /mountdir:c:mount-winpe /index:1



        4. With both images mounted, copy these files/folders from the installer mount path (c:mount) to the mount path for WinPE (c:mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:




          • Windowssystem32bootrec.exe

          • Windowssystem32en-USbootrec.exe.mui

          • WindowsWinSxSx86_microsoft-windows-winre-tools.resources_31bf3856ad364e35_10.0.17763.1_en-us_150e215b68bd79cc

          • WindowsWinSxSx86_microsoft-windows-winre-tools_31bf3856ad364e35_10.0.17763.1_none_5ea4ec160fde2af5



        5. Commit the WinPE image with:
          dism.exe /unmount-wim /mountdir:c:mount-winpe /commit


        6. Finally, copy the boot.wim back into the sources folder on the WinPE drive, then boot into WinPE and test that it's working with bootrec /? and bootrec /scanos.







        share|improve this answer















        This has been driving me crazy not having these in WinPE, not sure if this is published elsewhere but this is what seemed to work for me:




        1. Make sure you have a Windows Recovery/Installer CD that's the same bitness (x86/x64) as your WinPE image. If you don't, run the Windows Installer Creator to create a USB installer (I had to do this since my WinPE is x86).


        2. Once you have the USB installer, look for sourcesboot.wim. Copy this file somewhere, and then mount it with dism to view the contents:



          dism.exe /mount-wim /wimfile:c:pathtoboot.wim /mountdir:c:mount /index:1



        3. Next, find sourcesboot.wim on your WinPE drive, and copy that to a different location, and mount it to a separate directory with dism:



          dism.exe /mount-wim /wimfile:c:pathtowinpeboot.wim /mountdir:c:mount-winpe /index:1



        4. With both images mounted, copy these files/folders from the installer mount path (c:mount) to the mount path for WinPE (c:mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:




          • Windowssystem32bootrec.exe

          • Windowssystem32en-USbootrec.exe.mui

          • WindowsWinSxSx86_microsoft-windows-winre-tools.resources_31bf3856ad364e35_10.0.17763.1_en-us_150e215b68bd79cc

          • WindowsWinSxSx86_microsoft-windows-winre-tools_31bf3856ad364e35_10.0.17763.1_none_5ea4ec160fde2af5



        5. Commit the WinPE image with:
          dism.exe /unmount-wim /mountdir:c:mount-winpe /commit


        6. Finally, copy the boot.wim back into the sources folder on the WinPE drive, then boot into WinPE and test that it's working with bootrec /? and bootrec /scanos.








        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Feb 14 at 0:13









        Scott

        16.1k113990




        16.1k113990










        answered Feb 13 at 23:53









        4oo44oo4

        1




        1






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f805311%2fusing-bootrec-from-within-usb-booted-winpe-possible%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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕