Windows 10: Windows 10 - can be my UEFI and MBR conflict?

But you looked at screen from bios? ( up )Before format i had only 2 boot options in UEFI to choose1 SSD SAMSUNG 250 GB ( MBR )and UEFI KINGSTON USB. And after i change boot from UEFI KINGSTON USB to P1 SSD SAMSUNG 250 GB automatic repair happens only at 1 boot of Windows 10. Then after i click restart from automatic repair screen i was boot to Windows 10 fine. Is this because UEFI conflict with MBR? Or that doesnt matter of Automatic repair ?

 

I did look at all of your screenshots and I still have the user manual for your motherboard.

I've taken a 2nd look at your manual and there IS an option to use legacy boot through a Compatibility Support Module (CSM) to boot an MBR disk. On the "BOOT" screen, scroll down to items regarding CSM and secure boot. You probably have to disable secure boot to access the legacy boot options. See pages 3-53 and 3-54 in your user manual.

If booting in UEFI mode, you need a GPT disk scheme (which would have a 100 MB or so EFI System Partition) to boot with.

MBR disk scheme has NO EFI System Partition. You can call it "conflict" but it's more like you're mixing apples and oranges.

The UEFI boot of the MBR scheme disk has already passed from your BIOS to Windows control when it fails - the resolution and 2nd boot is accomplished by Windows finding in the repair routine what it needs to boot - and NOTHING in your BIOS/EFI firmware has been changed. So, then if you close Windows and reboot from your BIOS/EFI, you keep having the same result.

 

Explain me please why at 1 boot windows get Automatic repair. On screen with automatic repair i click restart and then windows boot fine. So needed 2 boots.Is this someting with bios related what you are talking about? Or cause was elsewhere?

This is answer yes? Can you explain more brighter? :"The UEFI boot of the MBR scheme disk has already passed from your BIOS to Windows control when it fails - the resolution and 2nd boot is accomplished by Windows finding in the repair routine what it needs to boot - and NOTHING in your BIOS/EFI firmware has been changed. So, then if you close Windows and reboot from your BIOS/EFI, you keep having the same result."


So this is issue with disk or only bios?

 

No, I don't think I can explain more brighter as I've tried to explain it about 8 different ways.

It's all BIOS/UEFI, MBR/GPT, Windows related.

1) MBR disks must be booted by legacy BIOS (which is an option I've pointed out how to accomplish on your motherboard).

2) UEFI booting requires a GPT disk. This is why Windows has to fix itself and only boots in 2nd cycle - as you keep trying to boot UEFI to an MBR disk.

I recommend you make up your mind whether to set up your disk as MBR or GPT and then set your BIOS boot options (in manner I have already explained to you) to either boot legacy (if MBR chosen) or boot UEFI (if GPT chosen).

I highly recommend you choose UEFI secure boot to a GPT disk scheme - which it looks like you are currently doing.

 

1.After formatted disk to GPT partition scheme i am booting Windows 10 from: SSD SAMSUNG 250 BOOT MANAGER in UEFI. No problems with this, system booting properly once without Automatic repair . So last time , why it was booting two times ( 1 boot was automatic repair ) after closing system? ( Parition was on MBR )



2.I dont change anything in UEFI SECURE BOOT , all is on default*Smile




3.Somebody said to me this:" UEFI firmware can emulate BIOS functionality (CSM/Legacy) and work with MBR disks just fine." But you said:"UEFI booting requires a GPT disk. This is why Windows has to fix itself and only boots in 2nd cycle - as you keep trying to boot UEFI to an MBR disk." So why i had automatic repair during 1 boot?

 

Because you can't boot UEFI to an MBR disk, as I've stated repeatedly. Closing system does NOTHING to resolve the conflict that you have attempting to boot UEFI on an MBR disk. The repair was having NO effect on the BIOS and it shouldn't - it's strictly a Windows function - and Windows simply found an alternate way to boot, it did NOT create an EFI System Partition for you.

Good. You should keep your disk in a GPT partition scheme then.

I explained to you that your firmware can indeed emulate BIOS functionality AND I pointed you to the specific pages in your user manual that explained to you how to take advantage of that capability - did you read it? - Post #15.

I think we're going in circles on this one. Exactly what is it you don't understand about: You passed control to Windows and Windows fixed itself but did nothing to fix the fact that you were repeatedly trying to boot UEFI with an MBR disk?

 

SO before i mark thread as solved so this is not hardware issue?

 

Not an issue with your hardware - only the manner in which you attempted to use it, the firmware, and the software.

 

Last question i will be very greatful for response.
Also i know that UEFI firmware can emulate BIOS functionality (CSM/Legacy) and work with MBR disks just fine.

So why it happened when i change boot from UEFI USB to SDD?

Somebody said to me:""If you switch boot devices, try to keep them in the same family. If you use NON UEFI CD/HDD/SSD/USB on everything, don't switch any of them to UEFI or strange things may happen (and if you use UEFI don't switch to BIOS (aka Legacy).

I wouldn't worry about it, just try to avoid the trigger (switching your boot order around from USB to HDD). Or at least, if you know it's
going to happen, you know how to fix it! <grin>."



Maybe because i switch then?


My bios settings are on default and my disk was formatted in MBR partition. CSM was ENABLED.

 

Look at your screenshot in post # 12 - it shows the USB as a UEFI bootable device, the Samsung NOT (no "UEFI" in front of it).

Exactly: because you were configured on BOOT screen for UEFI boot and switch to a first boot device that was NOT suitable for UEFI boot (MBR Samsung disk) and Windows was left on its own after boot failure and found an alternative means to boot. Definition of Insanity: doing the same thing over and over again and expecting the outcome to change. If you made no change in BIOS to switch to Legacy Boot, you would continually have the failure to boot 1st time and Windows finding a way to boot itself (2nd boot).

I would say that the advice you got to make up your mind over sticking entirely with Legacy Boot (use MBR) or else sticking entirely with UEFI (use GPT) was good advice [see my "2)" in my post # 17]. I would opt for sticking with UEFI/GPT going forward and only revert to Legacy Boot in special circumstances that may occur on rare occasions.

 

Yes but why system working fine and booting properly once ,just before i change "UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Before i do that system booting properly even if i had primary P1 SSD SAMSUNG EVO 250 GB.

Problem with Automatic Repair started after i change in my UEFI boot priority from :"UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Any idea?:] This is my last question and sorry for problem .

 

That would be hard to answer with certainty. We would have to know:

1) Are you sure it actually booted from the Samsung (as MBR) ? Was the Kingston drive bootable and can you be sure it didn't boot from that?

2) Is it possible you actually had the BIOS configured for Legacy boot at the time and it booted from the Samsung (as MBR)? You said it was switched to BIOS defaults at some time - was it possibly configured for Legacy boot and you reset defaults and had booting UEFI for all the other attempts?

Unless you reproduce that precise behavior and then give all the particulars on settings and devices actually present for boot, it seems like it would be useless to speculate at this point. I understand your burning curiosity at on that one question but, unless you have way more time on your hands than I do or another TenForums member can explain things in a way I'm unable to, I would just move on and enjoy what now sounds like is a properly configured and operating UEFI/GPT system.*Smile

 

Previously at first time i formatted disk to MBR ( because disk was formatted without warning about GPT ) partition during install Windows 10 by bootable usb ( iN UEFI boot was: UEFI KINGSTON USB ). Then i had in UEFI options: P1 Samsung Evo 250 GB and UEFI KINGSTON USB. Windows 10 working fine till someday i run memtest86 from bootable usb ( boot was the same :UEFI KINGSTON USB ). After finished memtest i decide to boot windows 10 and then i switch from UEFI KINGSTON USB to P1 Samsung Evo 250 GB and after this Automatic repair started. And then on Automatic repair cant repair your pc screen i choose restart and windows 10 boot at second time properly . Every boot of Windows 10 i had Automatic repair. So i dont know if it was Partition/bios issue ?

ps:
I never change anything in bios ( i dont touch CSM,Legacy,Uefi options all is on default )


I am actually after second format ( this time, i dont know why during installation of Windows 10, Windows give me warning to convert to GPT in UEFI systems so i do this ) and i am booting Windows 10 by SSD Samsung 250 Boot Manager in UEFI, and have no problems, all is fine.
And i was use the same Usb boot option in UEFI "UEFI KINGSTON USB" to install Windows 10 after this second format.
But i like to know if that problem was hardware or software/bios related?

Samsung Evo 250 GB BOOT MANAGER option in UEFI was added after installing Windows 10 on GPT format. ( after this second format )
So i have 2 options now in UEFI : Samsung Evo 250 GB and Samsung Evo 250 GB Boot Manager.

 

Hard to say - one or the other, both, or neither. I will say the trail has gotten a bit cold on this though.*Wink

 

You my good friend have the patience of Jobe!!!! Whew.... *Wink