Falha instalação dual boot

Adriana_Alves · 6 August 2020 18:22

Olá, estou tentando fazer a instalação pelo windows, mas sempre proximo do final do passo 3 da instalação, ocorre um erro. (Tentei instalar a versão completa e a básica, deram o mesmo erro)
segue os logs:

EndlessInstaller20200806_13_35_53.log (2,4,MB) EndlessInstaller20200805_18_55_50.log (957,9,KB)

egrath · 6 August 2020 18:52

Can you please check the following:

Press Windows-R, then enter msinfo32. Now check for the following Information:

BIOS Mode
Secure Boot State

Additionally, do you have administrative privileges on your computer? I ask these because the Installer assumes on your installation that it has been bootet with UEFI but is unable to mount the EFI Boot partition which is kinda strange:

14:38:05 - EFI system with 64-bit Windows; assuming x64 EFI (which is ok)
14:51:47 - C:\projects\rufus\endless\src\endless\EndlessUsbToolDlg.cpp:6262 CEndlessUsbToolDlg::MountESPFromDrive
14:51:47 - C:\projects\rufus\endless\src\endless\EndlessUsbToolDlg.cpp:6276 Unexpected partition type. Partition style is not GPT (GLE=[0])
14:51:47 - C:\projects\rufus\endless\src\endless\EndlessUsbToolDlg.cpp:5732 Error on MountESPFromDrive (GLE=[0])

To verify your partition structure, please also run diskpart and enter the following commands:

lis dis
sel dis 0
lis par
Should look like:

image552×510 9.64 KB

Please post all requested information ideally with screenshots.

Adriana_Alves · 6 August 2020 19:59

Respondendo sua pergunta, eu creio que sim, tenho privilégio de administrador.

segue em anexo os screenshots:

(desculpe não enviar screenshots separados, como membro novo só posso enviar uma imagem por vez)

egrath · 6 August 2020 20:49

@Byron_Diaz
Can you please verify the installer log with the engineers to check if this could be a bug - incorrect detection of x64 UEFI environment as it seems.

Byron_Diaz · 7 August 2020 03:45

Not a problem, reference number T30619.

wjt · 14 August 2020 09:37

Yes, it does look like the installer is incorrectly detecting a UEFI system. But the logic we use is very simple and is documented in Microsoft’s own documentation.

github.com

endlessm/rufus/blob/04b5f55f74c46e963f3bd82933f9010dbd9efe21/endless/src/endless/EndlessUsbToolDlg.cpp#L5636-L5645


bool CEndlessUsbToolDlg::IsLegacyBIOSBoot()
{
	FUNCTION_ENTER;
	// From https://msdn.microsoft.com/en-us/library/windows/desktop/ms724325(v=vs.85).aspx
	// On a legacy BIOS-based system, or on a system that supports both legacy BIOS and UEFI where Windows was installed using legacy BIOS,
	// the function will fail with ERROR_INVALID_FUNCTION. On a UEFI-based system, the function will fail with an error specific to the firmware,
	// such as ERROR_NOACCESS, to indicate that the dummy GUID namespace does not exist.
	DWORD result = GetFirmwareEnvironmentVariable(L"", L"{00000000-0000-0000-0000-000000000000}", NULL, 0);
	return result == 0 && GetLastError() == ERROR_INVALID_FUNCTION;
}

Unfortunately there isn’t a good way to work around this misdetection at the moment.

system · 11 September 2020 09:37

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.