Windows Boots Into {Default} Boot Entry. Boot Menu is Not Showing

-

howdy,

i running on the 6.4.9860 64-bit build of windows 10 tp enterprise used domain member workstation.

the native vhdx boot is used , both physical hdd , vhdx with windows 10 gpt/ahci disks following layout:

c:\windows\system32>diskpart  microsoft diskpart version 6.4.9860  copyright (c) 1999-2013 microsoft corporation. on computer: win-ssldoe83j61  diskpart> list disk    disk ###  status         size     free     dyn  gpt   --------  -------------  -------  -------  ---  ---   disk 0    online          931 gb      0 b        *   disk 1    online          100 gb      0 b        *  diskpart> sel disk 0  disk 0 selected disk.  diskpart> list part    partition ###  type              size     offset   -------------  ----------------  -------  -------   partition 1    recovery           300 mb  1024 kb   partition 2    system             100 mb   301 mb   partition 3    reserved           128 mb   401 mb   partition 4    primary            930 gb   529 mb   diskpart> sel disk 1  disk 1 selected disk.  diskpart> list part    partition ###  type              size     offset   -------------  ----------------  -------  -------   partition 1    recovery           500 mb  1024 kb   partition 2    system             100 mb   501 mb   partition 3    reserved           128 mb   601 mb   partition 4    primary             95 gb   729 mb   partition 5    recovery          4390 mb    95 gb  diskpart> list vol    volume ###  ltr  label        fs     type        size     status     info   ----------  ---  -----------  -----  ----------  -------  ---------  --------   volume 0     e                       dvd-rom         0 b  no media   volume 1     d                ntfs   partition    930 gb  healthy    pagefile   volume 2         recovery     ntfs   partition    300 mb  healthy    hidden   volume 3                      fat32  partition    100 mb  healthy    system   volume 4     c   10tp-ent     ntfs   partition     95 gb  healthy    boot   volume 5         recovery     fat32  partition    500 mb  healthy    hidden   volume 6         efs          fat32  partition    100 mb  healthy    hidden   volume 7         recovery     ntfs   partition   4390 mb  healthy    hidden

the bcd entries follows:

c:\windows\system32>bcdedit /enum /v  windows boot manager -------------------- identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795} device                  partition=\device\harddiskvolume2 path                    \efi\microsoft\boot\bootmgfw.efi description             windows boot manager locale                  en-us inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} integrityservices       enable flightsigning           yes default                 {e2b06012-6f56-11e4-82ee-abb7ebf625e8} resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8} displayorder            {e2b06012-6f56-11e4-82ee-abb7ebf625e8}                         {e2b0600d-6f56-11e4-82ee-abb7ebf625e8}                         {e2b06010-6f56-11e4-82ee-abb7ebf625e8}                         {e2b06013-6f56-11e4-82ee-abb7ebf625e8} toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d} timeout                 30  windows boot loader ------------------- identifier              {e2b06012-6f56-11e4-82ee-abb7ebf625e8} device                  vhd=[d:]\win10tpent3.vhdx,locate=custom:12000002 path                    \windows\system32\winload.efi description             windows technical preview 10 enterprise locale                  en-us inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} integrityservices       enable isolatedcontext         yes flightsigning           yes allowedinmemorysettings 0x15000075 osdevice                vhd=[d:]\win10tpent3.vhdx,locate=custom:22000002 systemroot              \windows resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8} nx                      optin bootmenupolicy          standard hypervisorlaunchtype    auto detecthal               yes  windows boot loader ------------------- identifier              {e2b0600d-6f56-11e4-82ee-abb7ebf625e8} device                  vhd=[d:]\win10tpent.vhdx,locate=custom:12000002 path                    \windows\system32\winload.efi description             old locale                  en-us inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence        {e2b0600e-6f56-11e4-82ee-abb7ebf625e8} integrityservices       enable recoveryenabled         yes isolatedcontext         yes allowedinmemorysettings 0x15000075 osdevice                vhd=[d:]\win10tpent.vhdx,locate=custom:22000002 systemroot              \windows resumeobject            {e2b0600c-6f56-11e4-82ee-abb7ebf625e8} nx                      optin bootmenupolicy          standard  windows boot loader ------------------- identifier              {e2b06010-6f56-11e4-82ee-abb7ebf625e8} device                  vhd=[d:]\win10tpent1.vhdx,locate=custom:12000002 path                    \windows\system32\winload.efi description             old. backup locale                  en-us inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence        {e2b0600e-6f56-11e4-82ee-abb7ebf625e8} integrityservices       enable recoveryenabled         yes isolatedcontext         yes allowedinmemorysettings 0x15000075 osdevice                vhd=[d:]\win10tpent1.vhdx,locate=custom:22000002 systemroot              \windows resumeobject            {e2b0600c-6f56-11e4-82ee-abb7ebf625e8} nx                      optin bootmenupolicy          standard hypervisorlaunchtype    auto  windows boot loader ------------------- identifier              {e2b06013-6f56-11e4-82ee-abb7ebf625e8} device                  vhd=[d:]\win10tpent2.vhdx,locate=custom:12000002 path                    \windows\system32\winload.efi description             backup locale                  en-us inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} isolatedcontext         yes flightsigning           yes allowedinmemorysettings 0x15000075 osdevice                vhd=[d:]\win10tpent2.vhdx,locate=custom:22000002 systemroot              \windows resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8} nx                      optin bootmenupolicy          standard hypervisorlaunchtype    auto detecthal               yes

when start pc or restart windows, no boot menu shown , pc automatically boots {default} windows loader entry. see is:

  • efi splash screen (i using dell pc see dell's logo instead of windows logo)
  • black screen
  • welcome screen of windows setup listed in bcd {default}

as see, there multiple boot entries in boot menu, aren't shown @ booting!

i cannot choose boot operating system other using following procedure:

  1. start pc , wait until boots {default} os
  2. in booted windows 10 tp enterprise select start|pc settings|update , recovery|recovery|advanced startup , click restart now.

pc restart recovery screen can choose boot operating system , safely boot of chosen. however, if restart pc operating system, boot default os , not last booted os.

seems issue boot manager.

in windows 8/7 there option troubleshoot booting troubleshoot screen, it's gone.

any clues on fixing this?

tried

# add boot data physical drive holding vhdx
bcdboot c:\windows /s c: /f uefi
# add boot data vhdx
bcdboot c:\windows /s d: /f uefi

from within booted {default} os. no luck.

probably, doing wrong , must:

  • attach volume 6 (efs) partition
  • assign drive letter it, t:
  • copy boot files partition
  • bcdboot c:\windows /s t: /f uefi
  • remove assigned driver letter.

what think?

thank in advance.

well world live in , these hands we're given...

simply change loaders

bootmenupolicy          standard

to "legacy"

or 

create element displaybootmenu (= "yes") {bootmgr}

it seems changed("repaired") loader entries have "detecthal" but no recovery.

reference - bootmenupolicy



Windows 10 Insider Preview  >  Windows 10 Insider Preview General



Comments

Post a Comment

Popular posts from this blog

After enabling Windows Server 2012 R2 DHCP Failover Getting Packet dropped because of Client ID hash mismatch

-
we have 2 dhcp servers @ our site (they each located on different subnets).  these dhcp servers running windows server 2012 r2.  dedicated dhcp servers.  yesterday afternoon, reconfigured several scopes such become members of single dhcp failover relationship have configured load balance 50% of load placed on each dhcp failover relationship member (dhcp server). however, morning, users reported unable renew dhcp addresses.  looking dhcp logs on both dhcp servers, there several entries follow: "36,mm/dd/yyyy,hh:mm:ss,packet dropped because of client id hash mismatch or standby server.,ip subnet,,mac address,,0,6,,,,,,,,,0" i performed manual synchronization of failover relationship , scopes on both dhcp servers.  restarted dhcp service on both dhcp servers still getting same error. a bing/google search did not bring light issue encountering.  has encountered , if so, solution. i should add when attempted perform ipconfig/renew on workst...
Read more

WMI Repository 4GB limit - Win 2003 Ent Question

-
Image
hi there, i've question size limit on wmi repository (being 4gb). if isn't correct place post this, apologies , can let me know wheere post this? i've come across few servers running citrix have reached limit on wmi repository size , need install ibm director agent hw monitoring. during install getting 'out of disk space' errors entered in mofcomp.log: "(mon apr 02 04:10:36 2012.172843) : error occurred while processing item 4: (mon apr 02 04:10:36 2012.172843) : error number: 0x8004103b, facility: wmi description: out of disk space" when error number http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx i see this: wbem_e_out_of_disk_space 2147749947 (0x8004103b) disk out of space or 4 gb limit on wmi repository (cim repository) size reached. windows xp , windows 2000/nt:   disk out of space. i'm wondering if there reason why limit set 4gb or can increase needs be? can't seem find reas...
Read more

Change home folder default permission?

-
i have searched on , can't seem find similar trying do. using windows server 2003 active directory. when create new user account on domain, use profile tab specify home directory user. when user logs in first time, active directory creates folder in specified path. working correctly. problem gives user full control on folder. has caused lot of problems because "clever" users have discovered thay can change permission on folder or subfolders beneath it. because don't want staff looking @ "sensitive" files. of course doesn't work since can take ownership of file , give myself permissions. causes trouble failed backups, inability scan these folders viruses, migration new storage etc. on occasion 1 of these users call me , ask file or folder restored, , @ point discover not have backup of files , cannot restore them. give them lecture, have on 2500 users, , can't talk them all. right have create account , login teh folder created, go take away full contr...
Read more