Windows 10: Windows 8/10 dual boot problems with booting to the secondary system

Hi, I installed Windows 10 beside of existing Windows 8.1 installation as secondary OS to second physical drive. When booting to Win 8, everything works fine but when booting Windows 10, I get the error screen shown below. The weir on it is that everything is at it's place since when I press Escape on this error screen, it takes me to BIOS, which I exit without saving, and after reboot, I already can normally boot to Windows 10. After restartting from (whichever) Windows the situation repeats. At least I can boot to 10 with the described workaround, but I want to fix this annoying issue. I'm just thinking that after BIOS exit the volumes table may be different than in Windows. I even tried to re-add the boot menu entry for 10 from Win8 session but is the same, so the boot entry seems to be correct. Any idea what's wrong?






Just for case the BCD config is this: Code: Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume2 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale en-us inherit {globalsettings} default {current} resumeobject {ac05b954-fe31-11e8-ae14-ef9370ccff74} displayorder {current} {ac05b955-fe31-11e8-ae14-ef9370ccff74} toolsdisplayorder {memdiag} timeout 15 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 8.1 Enterprise 64-bit locale en-us inherit {bootloadersettings} badmemoryaccess Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {601b1f5d-e1a1-11e8-87b9-54bef771218b} nx OptIn bootmenupolicy Legacy detecthal Yes quietboot No Windows Boot Loader ------------------- identifier {ac05b955-fe31-11e8-ae14-ef9370ccff74} device partition=\Device\HarddiskVolume8 path \Windows\system32\winload.efi description Windows 10 Enterprise 64-bit locale en-us inherit {bootloadersettings} isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=\Device\HarddiskVolume8 systemroot \Windows resumeobject {ac05b954-fe31-11e8-ae14-ef9370ccff74} nx OptIn bootmenupolicy Legacy[/quote]

:)

 

Dual Boot Windows question.

here is a guide that should do the trick: How to Dual-Boot Windows 10 with Windows 7 or 8

Just remember if u want UEFI on Windows 10 u most have UEFI on your Windows 7 too if not u need to go change it in the bios everytime u want to go back to Windows 7.

 

windows 10 slow boot

I was having a slow boot issue on my Windows 7 install a little while back. It would take about 30 - 40 extra seconds to boot up for whatever reason.

I would try following these steps, while this didn't solve my issue, it did increase Read/Write to where it should be.

http://www.disk-partition.com/kb/tips-ssd-optimization-windows7-1.html

Looks to be similar to this: https://www.back2gaming.com/focus-story/ssd-optimization-for-windows-10-windows-8-and-8-1/


In the end, I had to reinstall my Windows 7 entirely to fix the booting issue. It was taking around 35 seconds to boot, and after the fresh install it takes about 7 seconds to boot.

 

Dual Boot?

I can help here iv had both i used partition magic to split my HDD and i installed vista on one and xp was already on the other only problem is id watch out if i were you for some reason vista does not like to dual boot iv seen this on a couple of my machines and my buddys. so step one have xp installed step 2 find a partitioner of your choice i dont know of any except partition magic and the one included on xp...only thing is i dont think the one on xp will even partition them...then pop in your vista DVD and select the drive of your choice....the only thing i can think of that causes vista to hate dual booting sooo much is that when their are 2 OS's installed xp uses its own prog to list them on boot well vista uses a totally diff boot loader than the previous os's and i think they conflict the problems i hade were the standard missing windows folder missing HAL.dll and the nt one dont remember the name.....that and after your done vista and boot into xp things didnt like to start correctly specially if you scan disk with vista.