Hi there
Some of these boot issues are probably due to UEFI. For testing I'd switch back to thestandard NON UEFI BIOS. Since most here are using SSD's or Dual boot shouldn't be a problem.
UEFI boots tend to write stuff to the HDD -- a BIOS boot simply restricts activity to the Disk's MBR which is easy to fix if it gets hosed up via FIXMBR command.
Cheers
jimbo
No UEFI here, plain old BIOS, it's windows that wrote something on the wrong HDD, had no business doing that.
I have a triple boot, Win 7, Win 8.1 and Win 10. I use EasyBCD to keep things organized. After reading this thread I set my Win 10 partition for default boot. The update when without incident. When it was complete I set the default boot to Win 8.1 since that's where I do most of my work.
Its interesting that while the update did the "windows.old" thing similar to a refresh or upgrade it kept all my programs active like a Service Pack. It would be really nice if the upgrade from Windows 8.1 would work that way with the final release of Windows 10. Perhaps it could include some winged pigs too
Hi
It appeared to me that Windows 10 moves the boot loader on what ever partition it is installed on.
I opened EasyBCD in Windows 10 and set it up from there, and it worked fine.
I didn't have to do that after the update because I had already set the boot loader in 10 as the default.
It just stayed that way after the upgrade.
When it rebooted after is was finished the boot menu came up normally.
Since I'm only using Windows 10 I put it first in the boot order.
So if I don't respond it loads Windows 10 on its own.
Mike
You can alter quite a few boot parameters much more cleanly using msconfig.exe (search it from Start), then go to the Boot tab. From there, you can set the default OS to boot up, the timeout, and some advanced OS settings too. Obviously you have to have the dual boot settings already in your BCD for this to work. You can't add a new OS from here. EasyBCD puts proprietary entries in the BCD, which I'm not a fan of. If you want to add an OS install to the bootloader, better to learn how to use bcdboot. It's usually as simple as:
mountvol s: /s --- Makes the system partition available (if you have one)
bcdboot f:\windows /d /s s: /f ALL --- Set windows location to new installation's Windows directory; s: is drive where BCD is (system partition); can use UEFI or BIOS instead of ALL, depending on boot configuration
You can then check/adjust entries in msconfig.
Quote