Trying to dual boot Ubuntu 14.10 with Windows 10, last one not detected












11














I have a laptop, and I'm going to install Ubuntu (I have experience, and I have successfully installed Arch Linux, Ubuntu, Fedora, Debian, Xubuntu, Kubuntu, Manjaro Linux, etc.), but installing Ubuntu 14.10 (Utopic Unicorn) alongside Windows 10, Ubuntu can't detect Windows.



It shows me like there's no OS, but I have Windows 10.



I have two primary partitions by the way if I manually install. If the Ubuntu installer can't detect Windows 10, will it be detected at GRUB?










share|improve this question





























    11














    I have a laptop, and I'm going to install Ubuntu (I have experience, and I have successfully installed Arch Linux, Ubuntu, Fedora, Debian, Xubuntu, Kubuntu, Manjaro Linux, etc.), but installing Ubuntu 14.10 (Utopic Unicorn) alongside Windows 10, Ubuntu can't detect Windows.



    It shows me like there's no OS, but I have Windows 10.



    I have two primary partitions by the way if I manually install. If the Ubuntu installer can't detect Windows 10, will it be detected at GRUB?










    share|improve this question



























      11












      11








      11


      3





      I have a laptop, and I'm going to install Ubuntu (I have experience, and I have successfully installed Arch Linux, Ubuntu, Fedora, Debian, Xubuntu, Kubuntu, Manjaro Linux, etc.), but installing Ubuntu 14.10 (Utopic Unicorn) alongside Windows 10, Ubuntu can't detect Windows.



      It shows me like there's no OS, but I have Windows 10.



      I have two primary partitions by the way if I manually install. If the Ubuntu installer can't detect Windows 10, will it be detected at GRUB?










      share|improve this question















      I have a laptop, and I'm going to install Ubuntu (I have experience, and I have successfully installed Arch Linux, Ubuntu, Fedora, Debian, Xubuntu, Kubuntu, Manjaro Linux, etc.), but installing Ubuntu 14.10 (Utopic Unicorn) alongside Windows 10, Ubuntu can't detect Windows.



      It shows me like there's no OS, but I have Windows 10.



      I have two primary partitions by the way if I manually install. If the Ubuntu installer can't detect Windows 10, will it be detected at GRUB?







      dual-boot grub2






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 1 '15 at 20:42









      Fabby

      26.4k1360159




      26.4k1360159










      asked Dec 23 '14 at 0:44









      user284299

      56117




      56117






















          6 Answers
          6






          active

          oldest

          votes


















          12














          I wasn't able to get the boot repair to work so I manually added a Windows 10 boot option.



          The first step is to edit /etc/grub.d/40_custom (using SUDO) and add the following lines to the bottom of the file:



          menuentry 'Windows 10' {
          set root='(hd0,msdos1)'
          chainloader +1
          }


          In this case my bootloader was in /dev/sda1 hence the 1 at the end of msdos. After this run sudo update-grub2 and you should be good to go.



          Worked for me, advice taken from here:
          http://technologytales.com/2010/11/21/manually-adding-an-entry-for-windows-7-to-an-ubuntu-grub2-menu/






          share|improve this answer



















          • 1




            Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
            – SonicARG
            Jul 31 '15 at 23:43



















          3














          Windows should be detected while you manually install Ubuntu 14.10 and added to GRUB. If it is not added initially, boot into Ubuntu, install Boot Repair and run that. That should add Windows 10 to your GRUB.



          Source: I have run a Windows 10, Ubuntu 14.10, elementary OS, Fedora quad boot






          share|improve this answer





















          • i will add solved to the tittle and apply this thanks
            – user284299
            Dec 23 '14 at 4:11










          • grub just show me w10 recovery and dont the normal start
            – user284299
            Dec 23 '14 at 21:31










          • Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
            – oldfred
            Dec 25 '14 at 4:45










          • win10 clean install fela
            – user284299
            Dec 26 '14 at 5:04










          • @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
            – Fabby
            Jun 1 '15 at 20:41





















          1














          I had the same problem with Windows 7 after an Ubuntu 15.04 install.



          The solution was to use Grub 2 ntloader module instead of chainloader.



          Here is my 42_custom in /etc/grub.d/



          menuentry "Win 7 (loader) (on /dev/sda1)" --class windows --class os {
          insmod part_msdos
          insmod ntfs
          insmod ntldr
          set root='(hd0,msdos1)'
          search --no-floppy --fs-uuid --set=root 9804BD3004BD126C
          ntldr ($root)/bootmgr
          }


          You can change the text to Windows 10, it's only text.






          share|improve this answer























          • what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
            – DrCord
            Sep 1 '16 at 14:22










          • A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
            – J V
            Dec 10 '16 at 22:19





















          0














          Why don't you try to run boot repair from the Windows 10 ISO image? That way, Windows will have an MBR, and it would show the other operating systems. Try that.



          I believe you have installed Ubuntu, so insert the Windows DVD and select repair -> cmd.



          Now enter,



          Bootrec.exe /fixmbr


          There are other commands too. You can try these out:



          /FixBoot - writes a boot sector onto system partition to start Windows

          /ScanOs - scans all disks for Windows installation and displays them.

          /RebuildBCD - scans all disks for Windows installations and prompts you to pick the ones you want to add to the BCD.





          share|improve this answer



















          • 1




            it will show me ubuntu too?
            – user284299
            Dec 26 '14 at 5:05










          • You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
            – cyberrspiritt
            Dec 26 '14 at 5:07






          • 1




            Windows boot repair ignores other OS systems
            – DnrDevil
            Jan 11 '16 at 21:49










          • Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
            – shad0w_wa1k3r
            Jun 26 '16 at 20:35



















          0














          Boot Ubuntu and mount your Windows partition (simply open the disk on Nautilus)



          Run the following on the command line:
          CtrlAltt:



          sudo os-prober


          If your Windows installation was found, you can run:



          sudo update-grub


          Note that step 2 is just for your convenience. You could just mount the Windows 7 partition and then run update-grub.






          share|improve this answer































            0














            I have something like this



            menuentry 'Windows 10' {
            search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
            chainloader /EFI/Microsoft/Boot/bootmgfw.efi
            }





            share|improve this answer

















            • 2




              It might be helpful to describe what this code fragment means and what file it's found in (and what section)
              – Nick Weinberg
              Nov 6 '16 at 14:24












            • I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
              – Elder Geek
              Nov 6 '16 at 15:25










            • I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
              – Elhatron
              Nov 6 '16 at 15:56











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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%2faskubuntu.com%2fquestions%2f564496%2ftrying-to-dual-boot-ubuntu-14-10-with-windows-10-last-one-not-detected%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            6 Answers
            6






            active

            oldest

            votes








            6 Answers
            6






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            12














            I wasn't able to get the boot repair to work so I manually added a Windows 10 boot option.



            The first step is to edit /etc/grub.d/40_custom (using SUDO) and add the following lines to the bottom of the file:



            menuentry 'Windows 10' {
            set root='(hd0,msdos1)'
            chainloader +1
            }


            In this case my bootloader was in /dev/sda1 hence the 1 at the end of msdos. After this run sudo update-grub2 and you should be good to go.



            Worked for me, advice taken from here:
            http://technologytales.com/2010/11/21/manually-adding-an-entry-for-windows-7-to-an-ubuntu-grub2-menu/






            share|improve this answer



















            • 1




              Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
              – SonicARG
              Jul 31 '15 at 23:43
















            12














            I wasn't able to get the boot repair to work so I manually added a Windows 10 boot option.



            The first step is to edit /etc/grub.d/40_custom (using SUDO) and add the following lines to the bottom of the file:



            menuentry 'Windows 10' {
            set root='(hd0,msdos1)'
            chainloader +1
            }


            In this case my bootloader was in /dev/sda1 hence the 1 at the end of msdos. After this run sudo update-grub2 and you should be good to go.



            Worked for me, advice taken from here:
            http://technologytales.com/2010/11/21/manually-adding-an-entry-for-windows-7-to-an-ubuntu-grub2-menu/






            share|improve this answer



















            • 1




              Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
              – SonicARG
              Jul 31 '15 at 23:43














            12












            12








            12






            I wasn't able to get the boot repair to work so I manually added a Windows 10 boot option.



            The first step is to edit /etc/grub.d/40_custom (using SUDO) and add the following lines to the bottom of the file:



            menuentry 'Windows 10' {
            set root='(hd0,msdos1)'
            chainloader +1
            }


            In this case my bootloader was in /dev/sda1 hence the 1 at the end of msdos. After this run sudo update-grub2 and you should be good to go.



            Worked for me, advice taken from here:
            http://technologytales.com/2010/11/21/manually-adding-an-entry-for-windows-7-to-an-ubuntu-grub2-menu/






            share|improve this answer














            I wasn't able to get the boot repair to work so I manually added a Windows 10 boot option.



            The first step is to edit /etc/grub.d/40_custom (using SUDO) and add the following lines to the bottom of the file:



            menuentry 'Windows 10' {
            set root='(hd0,msdos1)'
            chainloader +1
            }


            In this case my bootloader was in /dev/sda1 hence the 1 at the end of msdos. After this run sudo update-grub2 and you should be good to go.



            Worked for me, advice taken from here:
            http://technologytales.com/2010/11/21/manually-adding-an-entry-for-windows-7-to-an-ubuntu-grub2-menu/







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 8 '15 at 0:37









            DaneM

            30613




            30613










            answered Jun 8 '15 at 18:02









            Zack

            12115




            12115








            • 1




              Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
              – SonicARG
              Jul 31 '15 at 23:43














            • 1




              Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
              – SonicARG
              Jul 31 '15 at 23:43








            1




            1




            Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
            – SonicARG
            Jul 31 '15 at 23:43




            Tip: When using grub-customizer to create the GRUB2 menues (I do, just to have them neat ;)), creating a chainloader type entry adds two additional lines to the two you had mentioned in the post. Be aware to remove them, otherwise Windows 10 will refuse to boot (It happened to me, so I spread the voice for solving the problem)
            – SonicARG
            Jul 31 '15 at 23:43













            3














            Windows should be detected while you manually install Ubuntu 14.10 and added to GRUB. If it is not added initially, boot into Ubuntu, install Boot Repair and run that. That should add Windows 10 to your GRUB.



            Source: I have run a Windows 10, Ubuntu 14.10, elementary OS, Fedora quad boot






            share|improve this answer





















            • i will add solved to the tittle and apply this thanks
              – user284299
              Dec 23 '14 at 4:11










            • grub just show me w10 recovery and dont the normal start
              – user284299
              Dec 23 '14 at 21:31










            • Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
              – oldfred
              Dec 25 '14 at 4:45










            • win10 clean install fela
              – user284299
              Dec 26 '14 at 5:04










            • @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
              – Fabby
              Jun 1 '15 at 20:41


















            3














            Windows should be detected while you manually install Ubuntu 14.10 and added to GRUB. If it is not added initially, boot into Ubuntu, install Boot Repair and run that. That should add Windows 10 to your GRUB.



            Source: I have run a Windows 10, Ubuntu 14.10, elementary OS, Fedora quad boot






            share|improve this answer





















            • i will add solved to the tittle and apply this thanks
              – user284299
              Dec 23 '14 at 4:11










            • grub just show me w10 recovery and dont the normal start
              – user284299
              Dec 23 '14 at 21:31










            • Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
              – oldfred
              Dec 25 '14 at 4:45










            • win10 clean install fela
              – user284299
              Dec 26 '14 at 5:04










            • @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
              – Fabby
              Jun 1 '15 at 20:41
















            3












            3








            3






            Windows should be detected while you manually install Ubuntu 14.10 and added to GRUB. If it is not added initially, boot into Ubuntu, install Boot Repair and run that. That should add Windows 10 to your GRUB.



            Source: I have run a Windows 10, Ubuntu 14.10, elementary OS, Fedora quad boot






            share|improve this answer












            Windows should be detected while you manually install Ubuntu 14.10 and added to GRUB. If it is not added initially, boot into Ubuntu, install Boot Repair and run that. That should add Windows 10 to your GRUB.



            Source: I have run a Windows 10, Ubuntu 14.10, elementary OS, Fedora quad boot







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 23 '14 at 3:31









            larouxn

            601510




            601510












            • i will add solved to the tittle and apply this thanks
              – user284299
              Dec 23 '14 at 4:11










            • grub just show me w10 recovery and dont the normal start
              – user284299
              Dec 23 '14 at 21:31










            • Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
              – oldfred
              Dec 25 '14 at 4:45










            • win10 clean install fela
              – user284299
              Dec 26 '14 at 5:04










            • @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
              – Fabby
              Jun 1 '15 at 20:41




















            • i will add solved to the tittle and apply this thanks
              – user284299
              Dec 23 '14 at 4:11










            • grub just show me w10 recovery and dont the normal start
              – user284299
              Dec 23 '14 at 21:31










            • Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
              – oldfred
              Dec 25 '14 at 4:45










            • win10 clean install fela
              – user284299
              Dec 26 '14 at 5:04










            • @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
              – Fabby
              Jun 1 '15 at 20:41


















            i will add solved to the tittle and apply this thanks
            – user284299
            Dec 23 '14 at 4:11




            i will add solved to the tittle and apply this thanks
            – user284299
            Dec 23 '14 at 4:11












            grub just show me w10 recovery and dont the normal start
            – user284299
            Dec 23 '14 at 21:31




            grub just show me w10 recovery and dont the normal start
            – user284299
            Dec 23 '14 at 21:31












            Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
            – oldfred
            Dec 25 '14 at 4:45




            Do you even have a Windows 10 recovery partiton. With some versions os-prober mis-identified Windows 7 boot and recovery, so maybe the same with Windows 10?
            – oldfred
            Dec 25 '14 at 4:45












            win10 clean install fela
            – user284299
            Dec 26 '14 at 5:04




            win10 clean install fela
            – user284299
            Dec 26 '14 at 5:04












            @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
            – Fabby
            Jun 1 '15 at 20:41






            @user284299 As you're a reputation 4 user: If this answer helped you, don't forget to click the grey at the left of this text, which means "yes, this answer is valid"! ;-) (Don't add "Solved" to the title... ;-))
            – Fabby
            Jun 1 '15 at 20:41













            1














            I had the same problem with Windows 7 after an Ubuntu 15.04 install.



            The solution was to use Grub 2 ntloader module instead of chainloader.



            Here is my 42_custom in /etc/grub.d/



            menuentry "Win 7 (loader) (on /dev/sda1)" --class windows --class os {
            insmod part_msdos
            insmod ntfs
            insmod ntldr
            set root='(hd0,msdos1)'
            search --no-floppy --fs-uuid --set=root 9804BD3004BD126C
            ntldr ($root)/bootmgr
            }


            You can change the text to Windows 10, it's only text.






            share|improve this answer























            • what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
              – DrCord
              Sep 1 '16 at 14:22










            • A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
              – J V
              Dec 10 '16 at 22:19


















            1














            I had the same problem with Windows 7 after an Ubuntu 15.04 install.



            The solution was to use Grub 2 ntloader module instead of chainloader.



            Here is my 42_custom in /etc/grub.d/



            menuentry "Win 7 (loader) (on /dev/sda1)" --class windows --class os {
            insmod part_msdos
            insmod ntfs
            insmod ntldr
            set root='(hd0,msdos1)'
            search --no-floppy --fs-uuid --set=root 9804BD3004BD126C
            ntldr ($root)/bootmgr
            }


            You can change the text to Windows 10, it's only text.






            share|improve this answer























            • what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
              – DrCord
              Sep 1 '16 at 14:22










            • A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
              – J V
              Dec 10 '16 at 22:19
















            1












            1








            1






            I had the same problem with Windows 7 after an Ubuntu 15.04 install.



            The solution was to use Grub 2 ntloader module instead of chainloader.



            Here is my 42_custom in /etc/grub.d/



            menuentry "Win 7 (loader) (on /dev/sda1)" --class windows --class os {
            insmod part_msdos
            insmod ntfs
            insmod ntldr
            set root='(hd0,msdos1)'
            search --no-floppy --fs-uuid --set=root 9804BD3004BD126C
            ntldr ($root)/bootmgr
            }


            You can change the text to Windows 10, it's only text.






            share|improve this answer














            I had the same problem with Windows 7 after an Ubuntu 15.04 install.



            The solution was to use Grub 2 ntloader module instead of chainloader.



            Here is my 42_custom in /etc/grub.d/



            menuentry "Win 7 (loader) (on /dev/sda1)" --class windows --class os {
            insmod part_msdos
            insmod ntfs
            insmod ntldr
            set root='(hd0,msdos1)'
            search --no-floppy --fs-uuid --set=root 9804BD3004BD126C
            ntldr ($root)/bootmgr
            }


            You can change the text to Windows 10, it's only text.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 21 at 14:09









            Sree

            33




            33










            answered Jul 31 '15 at 18:55









            ross minet

            264




            264












            • what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
              – DrCord
              Sep 1 '16 at 14:22










            • A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
              – J V
              Dec 10 '16 at 22:19




















            • what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
              – DrCord
              Sep 1 '16 at 14:22










            • A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
              – J V
              Dec 10 '16 at 22:19


















            what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
            – DrCord
            Sep 1 '16 at 14:22




            what does the string 9804BD3004BD126C mean? I am getting weird errors relating to that...
            – DrCord
            Sep 1 '16 at 14:22












            A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
            – J V
            Dec 10 '16 at 22:19






            A bit late to the party, but that's his partition UUID (They're short like that when windows sets them) And shouldn't the set root=... line be redundant since the search overwrites it?
            – J V
            Dec 10 '16 at 22:19













            0














            Why don't you try to run boot repair from the Windows 10 ISO image? That way, Windows will have an MBR, and it would show the other operating systems. Try that.



            I believe you have installed Ubuntu, so insert the Windows DVD and select repair -> cmd.



            Now enter,



            Bootrec.exe /fixmbr


            There are other commands too. You can try these out:



            /FixBoot - writes a boot sector onto system partition to start Windows

            /ScanOs - scans all disks for Windows installation and displays them.

            /RebuildBCD - scans all disks for Windows installations and prompts you to pick the ones you want to add to the BCD.





            share|improve this answer



















            • 1




              it will show me ubuntu too?
              – user284299
              Dec 26 '14 at 5:05










            • You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
              – cyberrspiritt
              Dec 26 '14 at 5:07






            • 1




              Windows boot repair ignores other OS systems
              – DnrDevil
              Jan 11 '16 at 21:49










            • Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
              – shad0w_wa1k3r
              Jun 26 '16 at 20:35
















            0














            Why don't you try to run boot repair from the Windows 10 ISO image? That way, Windows will have an MBR, and it would show the other operating systems. Try that.



            I believe you have installed Ubuntu, so insert the Windows DVD and select repair -> cmd.



            Now enter,



            Bootrec.exe /fixmbr


            There are other commands too. You can try these out:



            /FixBoot - writes a boot sector onto system partition to start Windows

            /ScanOs - scans all disks for Windows installation and displays them.

            /RebuildBCD - scans all disks for Windows installations and prompts you to pick the ones you want to add to the BCD.





            share|improve this answer



















            • 1




              it will show me ubuntu too?
              – user284299
              Dec 26 '14 at 5:05










            • You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
              – cyberrspiritt
              Dec 26 '14 at 5:07






            • 1




              Windows boot repair ignores other OS systems
              – DnrDevil
              Jan 11 '16 at 21:49










            • Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
              – shad0w_wa1k3r
              Jun 26 '16 at 20:35














            0












            0








            0






            Why don't you try to run boot repair from the Windows 10 ISO image? That way, Windows will have an MBR, and it would show the other operating systems. Try that.



            I believe you have installed Ubuntu, so insert the Windows DVD and select repair -> cmd.



            Now enter,



            Bootrec.exe /fixmbr


            There are other commands too. You can try these out:



            /FixBoot - writes a boot sector onto system partition to start Windows

            /ScanOs - scans all disks for Windows installation and displays them.

            /RebuildBCD - scans all disks for Windows installations and prompts you to pick the ones you want to add to the BCD.





            share|improve this answer














            Why don't you try to run boot repair from the Windows 10 ISO image? That way, Windows will have an MBR, and it would show the other operating systems. Try that.



            I believe you have installed Ubuntu, so insert the Windows DVD and select repair -> cmd.



            Now enter,



            Bootrec.exe /fixmbr


            There are other commands too. You can try these out:



            /FixBoot - writes a boot sector onto system partition to start Windows

            /ScanOs - scans all disks for Windows installation and displays them.

            /RebuildBCD - scans all disks for Windows installations and prompts you to pick the ones you want to add to the BCD.






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 27 '14 at 1:22









            Peter Mortensen

            1,03821016




            1,03821016










            answered Dec 25 '14 at 3:56









            cyberrspiritt

            1189




            1189








            • 1




              it will show me ubuntu too?
              – user284299
              Dec 26 '14 at 5:05










            • You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
              – cyberrspiritt
              Dec 26 '14 at 5:07






            • 1




              Windows boot repair ignores other OS systems
              – DnrDevil
              Jan 11 '16 at 21:49










            • Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
              – shad0w_wa1k3r
              Jun 26 '16 at 20:35














            • 1




              it will show me ubuntu too?
              – user284299
              Dec 26 '14 at 5:05










            • You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
              – cyberrspiritt
              Dec 26 '14 at 5:07






            • 1




              Windows boot repair ignores other OS systems
              – DnrDevil
              Jan 11 '16 at 21:49










            • Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
              – shad0w_wa1k3r
              Jun 26 '16 at 20:35








            1




            1




            it will show me ubuntu too?
            – user284299
            Dec 26 '14 at 5:05




            it will show me ubuntu too?
            – user284299
            Dec 26 '14 at 5:05












            You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
            – cyberrspiritt
            Dec 26 '14 at 5:07




            You could try... It will install windows boot manager in MBR, if windows identifies the other OS, it should.
            – cyberrspiritt
            Dec 26 '14 at 5:07




            1




            1




            Windows boot repair ignores other OS systems
            – DnrDevil
            Jan 11 '16 at 21:49




            Windows boot repair ignores other OS systems
            – DnrDevil
            Jan 11 '16 at 21:49












            Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
            – shad0w_wa1k3r
            Jun 26 '16 at 20:35




            Windows does not recognize other OS. And if you screw up the repair by running fixmbr, there may be no turning back, unless of course you get super grub 2 installed from some other system and fix your ubuntu boot option at the very least.
            – shad0w_wa1k3r
            Jun 26 '16 at 20:35











            0














            Boot Ubuntu and mount your Windows partition (simply open the disk on Nautilus)



            Run the following on the command line:
            CtrlAltt:



            sudo os-prober


            If your Windows installation was found, you can run:



            sudo update-grub


            Note that step 2 is just for your convenience. You could just mount the Windows 7 partition and then run update-grub.






            share|improve this answer




























              0














              Boot Ubuntu and mount your Windows partition (simply open the disk on Nautilus)



              Run the following on the command line:
              CtrlAltt:



              sudo os-prober


              If your Windows installation was found, you can run:



              sudo update-grub


              Note that step 2 is just for your convenience. You could just mount the Windows 7 partition and then run update-grub.






              share|improve this answer


























                0












                0








                0






                Boot Ubuntu and mount your Windows partition (simply open the disk on Nautilus)



                Run the following on the command line:
                CtrlAltt:



                sudo os-prober


                If your Windows installation was found, you can run:



                sudo update-grub


                Note that step 2 is just for your convenience. You could just mount the Windows 7 partition and then run update-grub.






                share|improve this answer














                Boot Ubuntu and mount your Windows partition (simply open the disk on Nautilus)



                Run the following on the command line:
                CtrlAltt:



                sudo os-prober


                If your Windows installation was found, you can run:



                sudo update-grub


                Note that step 2 is just for your convenience. You could just mount the Windows 7 partition and then run update-grub.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jul 17 '16 at 8:38









                Graham

                2,22061527




                2,22061527










                answered Jul 17 '16 at 7:12









                ahmad.sh

                1




                1























                    0














                    I have something like this



                    menuentry 'Windows 10' {
                    search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
                    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
                    }





                    share|improve this answer

















                    • 2




                      It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                      – Nick Weinberg
                      Nov 6 '16 at 14:24












                    • I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                      – Elder Geek
                      Nov 6 '16 at 15:25










                    • I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                      – Elhatron
                      Nov 6 '16 at 15:56
















                    0














                    I have something like this



                    menuentry 'Windows 10' {
                    search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
                    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
                    }





                    share|improve this answer

















                    • 2




                      It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                      – Nick Weinberg
                      Nov 6 '16 at 14:24












                    • I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                      – Elder Geek
                      Nov 6 '16 at 15:25










                    • I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                      – Elhatron
                      Nov 6 '16 at 15:56














                    0












                    0








                    0






                    I have something like this



                    menuentry 'Windows 10' {
                    search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
                    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
                    }





                    share|improve this answer












                    I have something like this



                    menuentry 'Windows 10' {
                    search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
                    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
                    }






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 6 '16 at 13:57









                    Elhatron

                    1




                    1








                    • 2




                      It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                      – Nick Weinberg
                      Nov 6 '16 at 14:24












                    • I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                      – Elder Geek
                      Nov 6 '16 at 15:25










                    • I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                      – Elhatron
                      Nov 6 '16 at 15:56














                    • 2




                      It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                      – Nick Weinberg
                      Nov 6 '16 at 14:24












                    • I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                      – Elder Geek
                      Nov 6 '16 at 15:25










                    • I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                      – Elhatron
                      Nov 6 '16 at 15:56








                    2




                    2




                    It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                    – Nick Weinberg
                    Nov 6 '16 at 14:24






                    It might be helpful to describe what this code fragment means and what file it's found in (and what section)
                    – Nick Weinberg
                    Nov 6 '16 at 14:24














                    I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                    – Elder Geek
                    Nov 6 '16 at 15:25




                    I second @NickWeinberg not everyone will recognize that snippet as an entry in the grub.cfg file. Please expand your answer for the benefit of those who don't recognize it as those who do are unlikely to need the guidance. Thank you for helping out!
                    – Elder Geek
                    Nov 6 '16 at 15:25












                    I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                    – Elhatron
                    Nov 6 '16 at 15:56




                    I found it in grub.cfg created by android installer. I'm not very good in editing grub (and english too...) but i think "root" and "chainloader" depends on localization of windows efi files.
                    – Elhatron
                    Nov 6 '16 at 15:56


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f564496%2ftrying-to-dual-boot-ubuntu-14-10-with-windows-10-last-one-not-detected%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 did Captain America manage to do this?

                    迪纳利

                    南乌拉尔铁路局