Professional Documents
Culture Documents
create partition primary <enter> (Este comando vai criar uma partio primria (no disco que
selecionou no passo select disk x)
exit <enter> (para abandonar o utilitrio diskpart )
exit <enter> (para regressar ao programa de instalao)
3 - Agora na tela de seleo de partio, escolhe aquela que acabou de criar. Se continuar a dar erro,
reinicia o computador e verifica se o erro desapareceu (de vez em quando necessrio um reboot
para que as alteraes fiquem visveis ao setup do Windows);
4 - Antes de instalar o Windows, formate o disco.
Fonte: Wikipedia, Frum UOL
Descrio do Bug
Durante a instalao no modo UEFI, "Could not open \EFI\BOOT\fallback.efi: 14" shows after
passed the BIOS phase.
Soluo
Criar um pendrive de instalao do Linux e depois renomear o arquivo
/EFI/BOOT/grubx64.efi para /EFI/BOOT/fallback.efi
Fonte: https://bugs.launchpad.net/ubuntu/+bug/1241824
The computer should reboot and then ask you for the account. Click your account to
continue.
Were going to use the built in partitioning tool called diskpart to confirm that:
1.
2.
diskpart
sel disk 0
Now that the first disk is selected we need to view all the partitions
list vol
Verify that the EFI partition is using the FAT32 file system then select the volume and assign
a drive letter to it.
Since im using Windows 8 from a VirtualBox image you wont see the FAT32 partition on
the screenshot above; but on yours you can select it by noting the Volume Number.
sel vol 3
assign letter=v:
You should see a message saying: DiskPart successfully assigned the drive letter or
mount point.
exit
You should still be in the command prompt but outside of the DISKPART> prompt.
cd /d v:\EFI\Microsoft\Boot\
bootrec /fixboot
The CD command tells the command line interpreter to change the directory to the volume
label that has the EFI boot record.
Then the bootrec /fixboot command attempts to repair the selected volume.
Alright, still with me?
BCDBoot is little tool that lets you manage the system partition files. In plain english, this
command says:
Hey Windows, Im going to use C:\Windows as the source for copying all
my boot-environment files and Im going to use the English locale and select
the volume letter that begins with v:
Fonte: http://www.fixedbyvonnie.com/2013/12/how-to-repair-the-efi-bootloader-inwindows-8/#.VFT0nvnF9ps
Using Boot Repair, as MariusMatutiae suggests, may work; however, that program sometimes does
more than is wise, so I prefer to avoid it. There are at least three less radical solutions:
Solution 1: Use the Firmware
Many EFIs provide a built-in boot manager that enables you to adjust the boot order. Your Ubuntu/GRUB
entry probably still exists, so all you need to do is to adjust the boot order using the firmware. The trouble
with this approach is that the EFI setup utilities vary so much that it's impossible to provide universallyapplicable instructions for how to do this. If your firmware supports this feature, though, it's likely to be
the simplest way to do it -- once you figure out how to get to the option!
Solution 2: Use bcdedit in Windows
The Windows bcdedit tool can add a non-Windows boot loader to the boot list. The trick is figuring out
what the file is. You can do it this way:
1.
2.
3.
4.
5.
6.
Boot to Windows
Open an Administrator Command Prompt window. (Don't use a third-party shell for this, either;
I've seen reports that bcdedit won't work correctly with some of them.)
Type mountvol S: /S to mount the ESP as S:. (You can change S: to something else if you like.)
Using the Command Prompt, check S: to locate your Ubuntu boot loader. It's probably
either S:\EFI\ubuntu\grubx64.efi or S:\ubuntu\shimx64.efi. If you see the latter, it should be
safe to use it, and it may be necessary to use it -- shim is how Ubuntu deals with Secure Boot (SB),
but on a non-SB computer, it will have little effect. If Secure Boot is inactive, then shim may or may
not be installed, so you may need to refer to grubx64.efi directly.
Type bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi,
changing shimx64.efi to grubx64.efi if shimx64.efi isn't present. Change the path if it's
something else, which is unlikely.
Optionally, type bcdedit /set {bootmgr} description "Ubuntu" to set the name that appears
in the EFI's own boot manager list. Change Ubuntu to whatever you like.
If you already know the filename for your boot loader, you can skip steps #3 and #4. (The ESP doesn't
need to be mounted to use bcdedit in this way.)
This method has the advantage that it keeps Windows from messing with the boot order -- sometimes
Windows will try to adjust the boot order unbidden. I don't know if this would prevent a repeat of this
problem if/when you upgrade to whatever comes after Windows 8.1, though.
Solution 3: Boot to Linux and Use efibootmgr
You can probably boot to Linux by using the firmware's own boot manager, which you can access on
most computers by hitting Esc or a function key at boot time, although which key varies from one
computer to another. Alternatively, you may be able to use rEFInd on a USB flash drive or CD-R as a
boot manager if yours is inadequate. You can also boot using a Linux live CD or emergency disk, but be
sure you boot in EFI mode -- a BIOS-mode boot won't be adequate. Once you're in Linux, you can
use efibootmgr to adjust the boot order:
1.
2.
Fonte: http://superuser.com/questions/696838/installed-updated-windows-8-uefi-afterubuntu-restore-grub