On Linux, make bootable USB from Windows installation ISO

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0















I tried creating a bootable USB from a Windows 10 ISO:



dd if=file.iso of=/dev/sdc bs=1M status=progress


However, when booting, all I saw was:



BOOTMGR is missing.
Press Ctrl+Alt+Del to restart


I can successfully mount the udf filesystem on the USB, so the dd worked ok.



My BIOS is from 2012.



What magic is required to create a bootable USB key?










share|improve this question
























  • Microsoft made Windows Installation ISO doesn't support that.

    – 炸鱼薯条德里克
    Feb 2 at 5:03






  • 1





    CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

    – telcoM
    Feb 2 at 10:54












  • I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

    – ivanivan
    Feb 2 at 14:30















0















I tried creating a bootable USB from a Windows 10 ISO:



dd if=file.iso of=/dev/sdc bs=1M status=progress


However, when booting, all I saw was:



BOOTMGR is missing.
Press Ctrl+Alt+Del to restart


I can successfully mount the udf filesystem on the USB, so the dd worked ok.



My BIOS is from 2012.



What magic is required to create a bootable USB key?










share|improve this question
























  • Microsoft made Windows Installation ISO doesn't support that.

    – 炸鱼薯条德里克
    Feb 2 at 5:03






  • 1





    CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

    – telcoM
    Feb 2 at 10:54












  • I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

    – ivanivan
    Feb 2 at 14:30













0












0








0








I tried creating a bootable USB from a Windows 10 ISO:



dd if=file.iso of=/dev/sdc bs=1M status=progress


However, when booting, all I saw was:



BOOTMGR is missing.
Press Ctrl+Alt+Del to restart


I can successfully mount the udf filesystem on the USB, so the dd worked ok.



My BIOS is from 2012.



What magic is required to create a bootable USB key?










share|improve this question
















I tried creating a bootable USB from a Windows 10 ISO:



dd if=file.iso of=/dev/sdc bs=1M status=progress


However, when booting, all I saw was:



BOOTMGR is missing.
Press Ctrl+Alt+Del to restart


I can successfully mount the udf filesystem on the USB, so the dd worked ok.



My BIOS is from 2012.



What magic is required to create a bootable USB key?







linux windows iso bootable






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 2 at 9:09







Tom Hale

















asked Feb 2 at 4:45









Tom HaleTom Hale

7,15033797




7,15033797












  • Microsoft made Windows Installation ISO doesn't support that.

    – 炸鱼薯条德里克
    Feb 2 at 5:03






  • 1





    CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

    – telcoM
    Feb 2 at 10:54












  • I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

    – ivanivan
    Feb 2 at 14:30

















  • Microsoft made Windows Installation ISO doesn't support that.

    – 炸鱼薯条德里克
    Feb 2 at 5:03






  • 1





    CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

    – telcoM
    Feb 2 at 10:54












  • I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

    – ivanivan
    Feb 2 at 14:30
















Microsoft made Windows Installation ISO doesn't support that.

– 炸鱼薯条德里克
Feb 2 at 5:03





Microsoft made Windows Installation ISO doesn't support that.

– 炸鱼薯条德里克
Feb 2 at 5:03




1




1





CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

– telcoM
Feb 2 at 10:54






CDs and DVDs use a completely different arrangement for bootability than hard disks and USB keys. Modern Linux ISO images have been specifically prepared (processed with isohybrid or similar) to be ready to boot also if transferred to USB media, but apparently Microsoft doesn't do that.

– telcoM
Feb 2 at 10:54














I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

– ivanivan
Feb 2 at 14:30





I've done it using mint-stick on a Mint system - on the menu it is titled "USB Image Writer"

– ivanivan
Feb 2 at 14:30










1 Answer
1






active

oldest

votes


















0














Use WoeUSB which makes a bootable USB key suitable for old BIOSes. It created a vfat partition whereas using dd didn't write any partitions.



I used --workaround-bios-boot-flag which says:




Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled




Note also that --device will wipe the whole USB key.



Here's my command and output:



% sudo woeusb --workaround-bios-boot-flag --device en_windows_10_multiple_editions_x64_dvd_6846432.iso /dev/sdc
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem...
Wiping all existing partition table and filesystem signatures in /dev/sdc...
/dev/sdc: 5 bytes were erased at offset 0x00008001 (udf): 43 44 30 30 31
Ensure that /dev/sdc is really wiped...
Creating new partition table on /dev/sdc...
Creating target partition...
Making system realize that partition table has changed...
Wait 3 seconds for block device nodes to populate...
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
Mounting target filesystem...
Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
Copying files from source media...
Installing GRUB bootloader for legacy PC booting support...
Installing for i386-pc platform.
Installation finished. No error reported.
Installing custom GRUB config for legacy PC booting...
Applying workaround for buggy motherboards that will ignore disks with no partitions with the boot flag toggled
Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
Unmounting and removing "/media/woeusb_source_1549081699_11951"...
Unmounting and removing "/media/woeusb_target_1549081699_11951"...
You may now safely detach the target device
Done :)
The target device should be bootable now


For good measure, type sync afterwards.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f498245%2fon-linux-make-bootable-usb-from-windows-installation-iso%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














    Use WoeUSB which makes a bootable USB key suitable for old BIOSes. It created a vfat partition whereas using dd didn't write any partitions.



    I used --workaround-bios-boot-flag which says:




    Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled




    Note also that --device will wipe the whole USB key.



    Here's my command and output:



    % sudo woeusb --workaround-bios-boot-flag --device en_windows_10_multiple_editions_x64_dvd_6846432.iso /dev/sdc
    WoeUSB v@@WOEUSB_VERSION@@
    ==============================
    Mounting source filesystem...
    Wiping all existing partition table and filesystem signatures in /dev/sdc...
    /dev/sdc: 5 bytes were erased at offset 0x00008001 (udf): 43 44 30 30 31
    Ensure that /dev/sdc is really wiped...
    Creating new partition table on /dev/sdc...
    Creating target partition...
    Making system realize that partition table has changed...
    Wait 3 seconds for block device nodes to populate...
    mkfs.fat 4.1 (2017-01-24)
    mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
    Mounting target filesystem...
    Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
    Copying files from source media...
    Installing GRUB bootloader for legacy PC booting support...
    Installing for i386-pc platform.
    Installation finished. No error reported.
    Installing custom GRUB config for legacy PC booting...
    Applying workaround for buggy motherboards that will ignore disks with no partitions with the boot flag toggled
    Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
    Unmounting and removing "/media/woeusb_source_1549081699_11951"...
    Unmounting and removing "/media/woeusb_target_1549081699_11951"...
    You may now safely detach the target device
    Done :)
    The target device should be bootable now


    For good measure, type sync afterwards.






    share|improve this answer



























      0














      Use WoeUSB which makes a bootable USB key suitable for old BIOSes. It created a vfat partition whereas using dd didn't write any partitions.



      I used --workaround-bios-boot-flag which says:




      Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled




      Note also that --device will wipe the whole USB key.



      Here's my command and output:



      % sudo woeusb --workaround-bios-boot-flag --device en_windows_10_multiple_editions_x64_dvd_6846432.iso /dev/sdc
      WoeUSB v@@WOEUSB_VERSION@@
      ==============================
      Mounting source filesystem...
      Wiping all existing partition table and filesystem signatures in /dev/sdc...
      /dev/sdc: 5 bytes were erased at offset 0x00008001 (udf): 43 44 30 30 31
      Ensure that /dev/sdc is really wiped...
      Creating new partition table on /dev/sdc...
      Creating target partition...
      Making system realize that partition table has changed...
      Wait 3 seconds for block device nodes to populate...
      mkfs.fat 4.1 (2017-01-24)
      mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
      Mounting target filesystem...
      Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
      Copying files from source media...
      Installing GRUB bootloader for legacy PC booting support...
      Installing for i386-pc platform.
      Installation finished. No error reported.
      Installing custom GRUB config for legacy PC booting...
      Applying workaround for buggy motherboards that will ignore disks with no partitions with the boot flag toggled
      Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
      Unmounting and removing "/media/woeusb_source_1549081699_11951"...
      Unmounting and removing "/media/woeusb_target_1549081699_11951"...
      You may now safely detach the target device
      Done :)
      The target device should be bootable now


      For good measure, type sync afterwards.






      share|improve this answer

























        0












        0








        0







        Use WoeUSB which makes a bootable USB key suitable for old BIOSes. It created a vfat partition whereas using dd didn't write any partitions.



        I used --workaround-bios-boot-flag which says:




        Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled




        Note also that --device will wipe the whole USB key.



        Here's my command and output:



        % sudo woeusb --workaround-bios-boot-flag --device en_windows_10_multiple_editions_x64_dvd_6846432.iso /dev/sdc
        WoeUSB v@@WOEUSB_VERSION@@
        ==============================
        Mounting source filesystem...
        Wiping all existing partition table and filesystem signatures in /dev/sdc...
        /dev/sdc: 5 bytes were erased at offset 0x00008001 (udf): 43 44 30 30 31
        Ensure that /dev/sdc is really wiped...
        Creating new partition table on /dev/sdc...
        Creating target partition...
        Making system realize that partition table has changed...
        Wait 3 seconds for block device nodes to populate...
        mkfs.fat 4.1 (2017-01-24)
        mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
        Mounting target filesystem...
        Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
        Copying files from source media...
        Installing GRUB bootloader for legacy PC booting support...
        Installing for i386-pc platform.
        Installation finished. No error reported.
        Installing custom GRUB config for legacy PC booting...
        Applying workaround for buggy motherboards that will ignore disks with no partitions with the boot flag toggled
        Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
        Unmounting and removing "/media/woeusb_source_1549081699_11951"...
        Unmounting and removing "/media/woeusb_target_1549081699_11951"...
        You may now safely detach the target device
        Done :)
        The target device should be bootable now


        For good measure, type sync afterwards.






        share|improve this answer













        Use WoeUSB which makes a bootable USB key suitable for old BIOSes. It created a vfat partition whereas using dd didn't write any partitions.



        I used --workaround-bios-boot-flag which says:




        Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled




        Note also that --device will wipe the whole USB key.



        Here's my command and output:



        % sudo woeusb --workaround-bios-boot-flag --device en_windows_10_multiple_editions_x64_dvd_6846432.iso /dev/sdc
        WoeUSB v@@WOEUSB_VERSION@@
        ==============================
        Mounting source filesystem...
        Wiping all existing partition table and filesystem signatures in /dev/sdc...
        /dev/sdc: 5 bytes were erased at offset 0x00008001 (udf): 43 44 30 30 31
        Ensure that /dev/sdc is really wiped...
        Creating new partition table on /dev/sdc...
        Creating target partition...
        Making system realize that partition table has changed...
        Wait 3 seconds for block device nodes to populate...
        mkfs.fat 4.1 (2017-01-24)
        mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
        Mounting target filesystem...
        Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
        Copying files from source media...
        Installing GRUB bootloader for legacy PC booting support...
        Installing for i386-pc platform.
        Installation finished. No error reported.
        Installing custom GRUB config for legacy PC booting...
        Applying workaround for buggy motherboards that will ignore disks with no partitions with the boot flag toggled
        Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files.
        Unmounting and removing "/media/woeusb_source_1549081699_11951"...
        Unmounting and removing "/media/woeusb_target_1549081699_11951"...
        You may now safely detach the target device
        Done :)
        The target device should be bootable now


        For good measure, type sync afterwards.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 2 at 4:45









        Tom HaleTom Hale

        7,15033797




        7,15033797



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f498245%2fon-linux-make-bootable-usb-from-windows-installation-iso%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

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?