1st Boot Fails, 2nd Boot Works (Bios?)

Greetings,

So over the last weeks I tried Ubuntu Mate and Zorin. I installed each OS on my Mini PC twice and although interesting they weren't stable enough to switch to. I then installed Win10 again and it's actually zippy and works fine. Except for --

-- a strange booting issue. When I hit the Power button on the back of the unit, the little light comes on, I get the Beelink Splash Page (the OEM) with the spinning dots. Then the screen goes black and the little light goes out. Yes. Then I hit the power button again and it boots properly.

I had to play with the BIOS to make it boot Linux. I believe I set everything back properly. Did I? Does this sound like a BIOS issue to you?

Ghot said:

When you installed Windows again, did you erase the drive first?

Thanks for reply.

There's a small partition I believe Beelink includes with drivers and such. But maybe I've got that wrong. This is what I see --



I'm not so versed in all this and so I don't know if this looks set up properly.

I was in the BIOS yesterday. I felt setting it back to EUFI is the correct move? And that the boot order reads properly here?

Ghot said:

On top of everything else, I've no idea what if any special requirements that mini-comp has.

That makes two of us.

I just played with Legacy vs. EUFI. If you set it to the former, a grub menu appears.

I checked if the power supply was loose -- but it wouldn't be so reliable as to fail every FIRST try but succeed every second. It's gotta be a setting somewhere.

Berton said:

That Network PXE Configuration choice would be worrisome for me using a stand-alone computer. Same may be for not needing Wake on LAN unless on a company network.

Are you suggesting I try turning off Wake on LAN?

Are you suggesting anything else?

(thanks for reply)

I found this and was wondering if the Ubuntu should even be there? (Is it a remnant or a generic option that's always there?)

Run two commands in a command prompt with admin privileges:

Code:

bcdboot C:\Windows
Powercfg -h off

See if that fixes it.

Oh, and you have to boot that disk in UEFI mode.

bcdboot C:\Windows rewrote the boot files contained in your EFI System Partition. I really doubt that did anything because it looks like you had a clean install of Windows 10 which would have written new boot files anyway. But it would not have hurt anything to run it.

powercfg -h off turned off hibernation, deleted the hiberfil.sys file from the root of C: drive, and turned off Windows 10 fast startup. Windows 10 fast startup is turned on by default when you install Windows 10. It is a modified form of hibernation using the hiberfil.sys file and many computers just don't get along with it very well. I suspect that was your problem. The computer on first boot was trying to start up from Windows 10 fast startup modified hibernation state and it was failing. On your second attempt, Windows 10 fast startup would have been cancelled due to the failure of the first attempt and the computer would successfully do a full cold boot. Disabling Windows 10 fast startup causes the computer to shut down completely so the next boot is always the standard full boot.