GRUB shows error: not a regular file when I select Windows 10 for boot

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





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
-1
down vote

favorite
1












I was dual booting Ubuntu with Windows 10 on my HP ProBook 430 G3. I have decided to give Antergos a try over Ubuntu. After a successful installation my grub menu was showing only Antergos.



It was quite a hassle to add the Windows 10 entry but when I selecting it I get the following error:



error: not a regular file


Is it possible that my Windows efi file /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi/grubx64.efi was somehow corrupted during the Antergos install?



This is the entry from the grub custom entry config /etc/grub.d/40_custom:



 if [ "$grub_platform" == "efi" ]; then
menuentry "Windows 10 64-bit UEFI-GPT"
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 D1C2-3A9A
chainloader /EFI/Microsoft/Boot/bootmgfw.efi

fi


Here is the result of sudo fdisk -l:



Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier:

Device Start End Sectors Size Type
/dev/sda14 962799616 1707433983 744634368 355.1G Microsoft basic data
/dev/sda17 1912236032 1914243071 2007040 980M Windows recovery environment
/dev/sda18 1914243072 1949319167 35076096 16.7G Microsoft basic data
/dev/sda19 1949319168 1953513471 4194304 2G Microsoft basic data


Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier:

Device Start End Sectors Size Type
/dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
/dev/sdb2 1024000 1228799 204800 100M EFI System
/dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
/dev/sdb4 1261568 295094942 293833375 140.1G Microsoft basic data
/dev/sdb5 295096320 296959999 1863680 910M Windows recovery environment
/dev/sdb6 296960000 300592811 3632812 1.7G Linux filesystem
/dev/sdb7 300592812 488397134 187804323 89.6G Linux filesystem


I have searched wiki and grub tutorials for Arch but I have not found description of the error that I am encountering. I have found this thread How to recover from grub renaming issue But the recommended steps did not resolve my issue. I have reinstalled the grub and re-created the grub config. The Windows 10 was not detected via os-prober either so adding it manually was the only option.







share|improve this question



























    up vote
    -1
    down vote

    favorite
    1












    I was dual booting Ubuntu with Windows 10 on my HP ProBook 430 G3. I have decided to give Antergos a try over Ubuntu. After a successful installation my grub menu was showing only Antergos.



    It was quite a hassle to add the Windows 10 entry but when I selecting it I get the following error:



    error: not a regular file


    Is it possible that my Windows efi file /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi/grubx64.efi was somehow corrupted during the Antergos install?



    This is the entry from the grub custom entry config /etc/grub.d/40_custom:



     if [ "$grub_platform" == "efi" ]; then
    menuentry "Windows 10 64-bit UEFI-GPT"
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 D1C2-3A9A
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi

    fi


    Here is the result of sudo fdisk -l:



    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier:

    Device Start End Sectors Size Type
    /dev/sda14 962799616 1707433983 744634368 355.1G Microsoft basic data
    /dev/sda17 1912236032 1914243071 2007040 980M Windows recovery environment
    /dev/sda18 1914243072 1949319167 35076096 16.7G Microsoft basic data
    /dev/sda19 1949319168 1953513471 4194304 2G Microsoft basic data


    Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier:

    Device Start End Sectors Size Type
    /dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
    /dev/sdb2 1024000 1228799 204800 100M EFI System
    /dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
    /dev/sdb4 1261568 295094942 293833375 140.1G Microsoft basic data
    /dev/sdb5 295096320 296959999 1863680 910M Windows recovery environment
    /dev/sdb6 296960000 300592811 3632812 1.7G Linux filesystem
    /dev/sdb7 300592812 488397134 187804323 89.6G Linux filesystem


    I have searched wiki and grub tutorials for Arch but I have not found description of the error that I am encountering. I have found this thread How to recover from grub renaming issue But the recommended steps did not resolve my issue. I have reinstalled the grub and re-created the grub config. The Windows 10 was not detected via os-prober either so adding it manually was the only option.







    share|improve this question























      up vote
      -1
      down vote

      favorite
      1









      up vote
      -1
      down vote

      favorite
      1






      1





      I was dual booting Ubuntu with Windows 10 on my HP ProBook 430 G3. I have decided to give Antergos a try over Ubuntu. After a successful installation my grub menu was showing only Antergos.



      It was quite a hassle to add the Windows 10 entry but when I selecting it I get the following error:



      error: not a regular file


      Is it possible that my Windows efi file /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi/grubx64.efi was somehow corrupted during the Antergos install?



      This is the entry from the grub custom entry config /etc/grub.d/40_custom:



       if [ "$grub_platform" == "efi" ]; then
      menuentry "Windows 10 64-bit UEFI-GPT"
      insmod part_gpt
      insmod fat
      insmod search_fs_uuid
      insmod chain
      search --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 D1C2-3A9A
      chainloader /EFI/Microsoft/Boot/bootmgfw.efi

      fi


      Here is the result of sudo fdisk -l:



      Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier:

      Device Start End Sectors Size Type
      /dev/sda14 962799616 1707433983 744634368 355.1G Microsoft basic data
      /dev/sda17 1912236032 1914243071 2007040 980M Windows recovery environment
      /dev/sda18 1914243072 1949319167 35076096 16.7G Microsoft basic data
      /dev/sda19 1949319168 1953513471 4194304 2G Microsoft basic data


      Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: gpt
      Disk identifier:

      Device Start End Sectors Size Type
      /dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
      /dev/sdb2 1024000 1228799 204800 100M EFI System
      /dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
      /dev/sdb4 1261568 295094942 293833375 140.1G Microsoft basic data
      /dev/sdb5 295096320 296959999 1863680 910M Windows recovery environment
      /dev/sdb6 296960000 300592811 3632812 1.7G Linux filesystem
      /dev/sdb7 300592812 488397134 187804323 89.6G Linux filesystem


      I have searched wiki and grub tutorials for Arch but I have not found description of the error that I am encountering. I have found this thread How to recover from grub renaming issue But the recommended steps did not resolve my issue. I have reinstalled the grub and re-created the grub config. The Windows 10 was not detected via os-prober either so adding it manually was the only option.







      share|improve this question













      I was dual booting Ubuntu with Windows 10 on my HP ProBook 430 G3. I have decided to give Antergos a try over Ubuntu. After a successful installation my grub menu was showing only Antergos.



      It was quite a hassle to add the Windows 10 entry but when I selecting it I get the following error:



      error: not a regular file


      Is it possible that my Windows efi file /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi/grubx64.efi was somehow corrupted during the Antergos install?



      This is the entry from the grub custom entry config /etc/grub.d/40_custom:



       if [ "$grub_platform" == "efi" ]; then
      menuentry "Windows 10 64-bit UEFI-GPT"
      insmod part_gpt
      insmod fat
      insmod search_fs_uuid
      insmod chain
      search --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt2' --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 D1C2-3A9A
      chainloader /EFI/Microsoft/Boot/bootmgfw.efi

      fi


      Here is the result of sudo fdisk -l:



      Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier:

      Device Start End Sectors Size Type
      /dev/sda14 962799616 1707433983 744634368 355.1G Microsoft basic data
      /dev/sda17 1912236032 1914243071 2007040 980M Windows recovery environment
      /dev/sda18 1914243072 1949319167 35076096 16.7G Microsoft basic data
      /dev/sda19 1949319168 1953513471 4194304 2G Microsoft basic data


      Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: gpt
      Disk identifier:

      Device Start End Sectors Size Type
      /dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
      /dev/sdb2 1024000 1228799 204800 100M EFI System
      /dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
      /dev/sdb4 1261568 295094942 293833375 140.1G Microsoft basic data
      /dev/sdb5 295096320 296959999 1863680 910M Windows recovery environment
      /dev/sdb6 296960000 300592811 3632812 1.7G Linux filesystem
      /dev/sdb7 300592812 488397134 187804323 89.6G Linux filesystem


      I have searched wiki and grub tutorials for Arch but I have not found description of the error that I am encountering. I have found this thread How to recover from grub renaming issue But the recommended steps did not resolve my issue. I have reinstalled the grub and re-created the grub config. The Windows 10 was not detected via os-prober either so adding it manually was the only option.









      share|improve this question












      share|improve this question




      share|improve this question








      edited Jul 29 at 16:59
























      asked Jul 29 at 16:10









      msam

      166




      166

























          active

          oldest

          votes











          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          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%2f459197%2fgrub-shows-error-not-a-regular-file-when-i-select-windows-10-for-boot%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459197%2fgrub-shows-error-not-a-regular-file-when-i-select-windows-10-for-boot%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

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

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay