boot menu problem

Discussion in 'Windows 10 Help and Support' started by citrix, Aug 29, 2015.

  1. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    I have dual boot windows 10 and windows 7 setup. windows 10 is the main system. windows 7 is a hard drive taken from old broken laptop. I used bcdedit to set it boot up. windows 7 banner start up for 2 seconds then system would power off and restart. I wanted to see what was loaded on the system so I used windows 7 repair disc to make it start. The repair disc 'says could not automatically repair the system.. Then I restart the system.

    now the windows blue flash windows icon would come but then screen turn black, system stay on, nothing happens, hit any key on keyboard, push power button on computer case, screen still black. the power button on computer case would not turn off system. this stay long time, then the blue boot menu come on. windows 10 would load slightly slower than usual.

    how to fix this issue ?
     
  2. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    I appears you have individual installs of Windows 7 and Windows 10. We need more information, such as are both OSes installed in Legacy Mode?

    If you altered the BCD Store to get Windows 7 to boot it might be advisable for you to post a listing of your BCD store in case we can see anything.
     
  3. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,052
    Likes Received:
    302
    Hi

    Are you saying that you can boot into Windows 10, but slowly as if something is interfering?
    Once you are booted into W10 do things work, can you open and run software etc.?

    If that's the case this is just what I'd try, I'm just going by past experience, if you can run stuff in Windows 10, I'd download and install EasyBCD because the graphical interface makes it a lot easier for me to understand what's going on.

    If when you open it, you can see both your Windows 7 and Windows 10 operating systems, make sure Windows 10 is in position number 1, and set as the default OS.

    Tell it you don't want to see a boot menu, and remove the Windows 7 option from the boot menu.
    Say OK, and shut down and unplug the Widows 7 drive from the mother board.

    Reboot.

    If everything boots up and runs normally, then shut it off, plug the Windows 7 drive back in, and boot up again.
    You shouldn't see any difference from the last time, it will just boot into Windows 10.

    Now if you need to also run Windows 7, open EasyBCD and add Windows 7 back in as the second operation system.

    Select show boot menu and reboot again.

    You should get a boot menu asking which OS you want to boot into.
    This part hasn't always worked for me, but you can access the boot menu through what ever key brings up boot options on your computer.

    Maybe you'll get some better ideas here but that's what I've got.

    Mike
     
  4. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    There is no problem with boot menu item. The problem is the menu and system load slow.

    here is list of boot items from easyBCD

    There are a total of 2 entries listed in the bootloader.

    Default: Windows 10
    Timeout: 30 seconds
    Boot Drive: C:\

    Entry #1
    Name: Windows 10
    BCD ID: {current}
    Drive: C:\
    Bootloader Path: \WINDOWS\system32\winload.exe

    Entry #2
    Name: Windows 7
    BCD ID: {a92fdefc-e05a-11e2-9b1d-00268312af8f}
    Device: unknown
    Bootloader Path: \Windows\system32\winload.exe



    Windows 7 was installed on the drive when it was on the laptop. I did not reinstall it when I plug it on this PC. I forced it to run after I added it to boot menu. The problem came after I used a repair disc to make it run.
     
  5. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    I can't tell you anything from what you posted above except you have a Legacy install. A real BCDedit / enum all readout would have been better. You can always port it to a text file and just attach that.

    If it isn't the boot menu, which it still could be, did you allow the Windows 7 system to replace the original drivers with ones on the new system? Could the drive be having problems? Try disconnecting the Windows 10 drive and see how the system boots.

    This is from my only Legacy system with just the one OS.

     
  6. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    Here is the result. how can I tell it is legacy install ?

    C:\WINDOWS\system32>bcdedit /enum all

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=C:
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {cca81d47-3804-11e5-9fe7-d66e23a13c35}
    displayorder {current}
    {a92fdefc-e05a-11e2-9b1d-00268312af8f}
    toolsdisplayorder {memdiag}
    timeout 30
    displaybootmenu Yes

    Windows Boot Loader
    -------------------
    identifier {54562193-e071-11e2-83be-9534fbf94502}
    device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{54562194-e071-11e2-83be-9534fbf94502}
    path \windows\system32\winload.exe
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{54562194-e071-11e2-83be-9534fbf94502}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {80c94418-3777-11e3-8f93-dc4e03c72eed}
    device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{80c94419-3777-11e3-8f93-dc4e03c72eed}
    path \windows\system32\winload.exe
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{80c94419-3777-11e3-8f93-dc4e03c72eed}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {a92fdefc-e05a-11e2-9b1d-00268312af8f}
    device unknown
    path \Windows\system32\winload.exe
    description Windows 7
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a92fdefd-e05a-11e2-9b1d-00268312af8f}
    integrityservices Enable
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    osdevice unknown
    systemroot \Windows
    resumeobject {a92fdefb-e05a-11e2-9b1d-00268312af8f}
    nx OptIn
    bootmenupolicy Standard

    Windows Boot Loader
    -------------------
    identifier {a92fdefd-e05a-11e2-9b1d-00268312af8f}
    device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{a92fdefe-e05a-11e2-9b1d-00268312af8f}
    path \windows\system32\winload.exe
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{a92fdefe-e05a-11e2-9b1d-00268312af8f}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Setup
    -------------
    identifier {cbd971bf-b7b8-4885-951a-fa03044f5d71}
    device ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{519a323b-37e2-11e5-829f-00268312af8f}
    path \windows\system32\winload.exe
    description Windows Rollback
    locale en-US
    inherit {bootloadersettings}
    osdevice ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{519a323b-37e2-11e5-829f-00268312af8f}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \WINDOWS\system32\winload.exe
    description Windows 10
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {f91251e8-3804-11e5-9fe7-d66e23a13c35}
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \WINDOWS
    resumeobject {cca81d47-3804-11e5-9fe7-d66e23a13c35}
    nx OptIn
    bootmenupolicy Standard

    Windows Boot Loader
    -------------------
    identifier {f91251e8-3804-11e5-9fe7-d66e23a13c35}
    device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{f91251e9-3804-11e5-9fe7-d66e23a13c35}
    path \windows\system32\winload.exe
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{f91251e9-3804-11e5-9fe7-d66e23a13c35}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {2a33fc4d-3775-11e3-8f93-dc4e03c72eed}
    device partition=C:
    path \WINDOWS\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    recoverysequence {80c94418-3777-11e3-8f93-dc4e03c72eed}
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {8eba3b65-2dfc-11e3-bf0f-f46d0440ca57}
    device partition=C:
    path \windows\system32\winresume.exe
    description Windows Resume Application
    locale en-us
    inherit {resumeloadersettings}
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {a92fdefb-e05a-11e2-9b1d-00268312af8f}
    device unknown
    path \Windows\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    recoverysequence {a92fdefd-e05a-11e2-9b1d-00268312af8f}
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    filedevice unknown
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {cca81d47-3804-11e5-9fe7-d66e23a13c35}
    device partition=C:
    path \WINDOWS\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    recoverysequence {f91251e8-3804-11e5-9fe7-d66e23a13c35}
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=C:
    path \boot\memtest.exe
    description Windows Memory Diagnostic
    locale en-US
    inherit {globalsettings}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {emssettings}
    bootems No

    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Serial
    debugport 1
    baudrate 115200

    RAM Defects
    -----------
    identifier {badmemory}

    Global Settings
    ---------------
    identifier {globalsettings}
    inherit {dbgsettings}
    {emssettings}
    {badmemory}

    Boot Loader Settings
    --------------------
    identifier {bootloadersettings}
    inherit {globalsettings}
    {hypervisorsettings}

    Hypervisor Settings
    -------------------
    identifier {hypervisorsettings}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}

    Device options
    --------------
    identifier {519a323b-37e2-11e5-829f-00268312af8f}
    description Windows Setup
    ramdisksdidevice partition=C:
    ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options
    --------------
    identifier {54562194-e071-11e2-83be-9534fbf94502}
    description Windows Recovery
    ramdisksdidevice unknown
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {80c94419-3777-11e3-8f93-dc4e03c72eed}
    description Windows Recovery
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {87758bc0-374f-11e3-bf3c-00268312af8f}
    description Windows Setup
    ramdisksdidevice partition=C:
    ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options
    --------------
    identifier {a92fdefe-e05a-11e2-9b1d-00268312af8f}
    description Windows Recovery
    ramdisksdidevice unknown
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {f91251e9-3804-11e5-9fe7-d66e23a13c35}
    description Windows Recovery
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    C:\WINDOWS\system32>
     
  7. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
  8. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    It is going to take me a while to go through all the entries, but I can tell you now, a Windows 7 OS Loader entry does not use the Bootmenupolicy entry. Windows 8 and 10 use the Standard version, but Windows 7 is either Legacy or not there.

    Once that is done, the GUI menu will usually show up if Window 10 is set as primary system.

    You can tell it is a Legacy install because you are using Winload.exe instead of Winload.efi

    Edit: You also have that DisplayBootMenu entry in the Boot Manger... not sure it should be there either.

    You are showing Device as Unknown on the Windows 7 path. I think it should show the partition shown for the Windows 7 OS partition when booted into Windows 10, but not completely sure.
     

    Attached Files:

    #8 Saltgrass, Aug 30, 2015
    Last edited: Aug 30, 2015
  9. citrix

    citrix Extraordinary Member

    Joined:
    Nov 18, 2006
    Messages:
    130
    Likes Received:
    0
    I installed windows servers 2016 preview on the windows 7 drive. Windows 7 was essential to load here because I just wanted to try to see it really would load this way, since it take too much trouble then I don't need it anymore and I did not expect the problem come.

    I thought put a windows install similar to windows 10 would bring a boot menu so I put server 2016 preview. But it did not fix the problem.

    I also found out that the command to fix bootloader in windows 10.

    bootsect /nt60 c:

    still same. any idea?
     
  10. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    That command is for changing an XP boot system to a Windows Vista/7/8/10 boot system. If you weren't getting a message about a missing NTLDR you did not need to run it, but it did not hurt.

    Considering the changes you made, it appears you are on your own... Maybe Mike will be able to help.
     

Share This Page

Loading...