• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MS's boot loader sucks.

Elixer

Lifer
For those of you that dual/tri boot with win 10, is there anything more annoying than to select win 10 on the OS pick menu, then it reboots the system, and then goes into 10?
With 7 or 8, it goes right into the OS, no reboots.

Heck, even with grub, it can boot directly to the OS you want with no reboots.
So, one has to ask, why is MS doing a reboot with its boot loader?
 
I had an XP/8.1 dual-boot system and it would also restart a few times before booting into the chosen OS. Annoying, I agree 😎
 
Hmm.. I just installed Dual Boot Win 7/Win 10 few hours ago.

I install each one straight and used EZBCD to configure the Boot Menu.

It goes directly to 7 or 10 Without any additional reboot.

https://neosmart.net/EasyBCD/

You have to make sure that the choices are both are configured with the same type Boot BIOS.

I.e., Not one OS regular BIOS and the other UEFI.



😎
 
The UEFI is probably it. The other OS(es) are in legacy mode, Win10 in UEFI.

I don't dual boot but now I almost want to try this just to see since my Win10 is loaded in legacy mode as my motherboard doesn't support UEFI.
 
The UEFI is probably it. The other OS(es) are in legacy mode, Win10 in UEFI.

I don't dual boot but now I almost want to try this just to see since my Win10 is loaded in legacy mode as my motherboard doesn't support UEFI.

Yeah, the install that I mentioned above is on an Old HP Probook, both OSs are installed in Legacy Mode.

.
 
In my case, the mobo is NOT UEFI capable, and it reboots.
As I said, you can replace MS's bootlader with something else, and it don't reboot either, so, MS is doing something odd.
 
In my case, the mobo is NOT UEFI capable, and it reboots.
As I said, you can replace MS's bootlader with something else, and it don't reboot either, so, MS is doing something odd.

Any odd switches or setting on the windows 10 entry? the reason why i mention it is I had dual boot option with hyper-v on and off, and to boot between those it would reboot once selected from the menu
 
There's option for command-line boot configuration tool, bcdedit.exe to ask it to use legacy boot menu. Aka Windows 7 style. That one just displays list of entries an then boots to selected one.

EDIT. Command is
Code:
bcdedit /set {default} bootmenupolicy legacy
should be ran from elevated privilege command prompt
 
Last edited:
There's option for command-line boot configuration tool, bcdedit.exe to ask it to use legacy boot menu. Aka Windows 7 style. That one just displays list of entries an then boots to selected one.

EDIT. Command is
Code:
bcdedit /set {default} bootmenupolicy legacy
should be ran from elevated privilege command prompt

I forgot to mention, this did fix it, so after this is done, there is no need for the machine to have an extra reset.

The problem was that with the new boot loader, it pre-loads system files before the OS pick stage, so, it needs to reset in order to wipe those pre-loaded ones out.
 
I understand these complaints, but to me, it just doesn't matter that much.

In another thread, I mentioned my experience with Primo-Cache 2.2.0, and a new feature that saves your RAM-cache to disk at restart or shutdown, making it a persistent cache. Reloading the cache at boot-time is an extra delay -- could be 10 seconds or more, I can't say. But I suffer this delay so that my hit-rate on the cache just keeps going up with every successive reboot.

If the system hibernates, it will simply come back to the OS last selected, without going through a re-boot hoop. If you can fix it with the tool already mentioned, that's great. To me, it hardly seems worth the trouble.
 
To meet some of their goals, the boot experience was designed to be much deeper into Windows in Windows 8 than previous incarnations. I'm sure if you look up the 'Designing Windows 8' blog you can find the articles where they expand on how and why they made the decisions they did.
 
Back
Top