UEFI Boot problem after bcedit command

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 2,322
    Win10
       #21

    Saltgrass said:
    The one entry I don't recognize is the:

    integrityserives Enabled

    But it is just Win 8.1, so I assume all references to Win 10 are gone... not much I can do.

    If you were to do a bcdedit /enum all it might show the prior Win 10 option but you may have gone beyond that.

    Could be the Security chip ie TPM (Trusted Platform Module) perhaps that's why there is a issue at boot ?

    The Manual might tell us if there is a TPM chip
      My Computers


  2. Posts : 17
    Windows 10
    Thread Starter
       #22

    The computer is a Samsumg ATIV Book 2 (270E5G/270E5J). I should have informed this from the beginning, my bad.

    I tried to translate the output of bcdedit /enum all. Probably it is not exactly as it would be in the english version of Windows.


    Firmware Initialization Manager
    ----------------------------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    timeout 2

    Windows Initialization Manager
    ---------------------------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale pt-BR
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {48ebdf9a-63ba-11e3-a5c5-e8039ae113a5}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b50e-6382-11e3-824f-806e6f6e6963}
    description Setup

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b50f-6382-11e3-824f-806e6f6e6963}
    description Boot Menu

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b510-6382-11e3-824f-806e6f6e6963}
    description Recovery

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b511-6382-11e3-824f-806e6f6e6963}
    description SATA HDD:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b512-6382-11e3-824f-806e6f6e6963}
    description SATA CD:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b513-6382-11e3-824f-806e6f6e6963}
    description CD-ROM:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b514-6382-11e3-824f-806e6f6e6963}
    description USB CD:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b515-6382-11e3-824f-806e6f6e6963}
    description USB FDD:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b516-6382-11e3-824f-806e6f6e6963}
    description USB HDD:

    Firmware Application (101fffff)
    ---------------------------------
    identifier{d235b517-6382-11e3-824f-806e6f6e6963}
    description NETWORK:

    Windows Initialization Loader
    --------------------------------------
    identifier{2175f4c9-6b7b-11e4-825d-24f5aa658942}
    device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
    re.wim,{2175f4ca-6b7b-11e4-825d-24f5aa658942}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-us
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
    re.wim,{2175f4ca-6b7b-11e4-825d-24f5aa658942}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Initialization Loader
    --------------------------------------
    identifier{current}
    device partition=C:
    path \windows\system32\winload.efi
    description Windows 8.1
    locale pt-BR
    inherit {bootloadersettings}
    recoverysequence {2175f4c9-6b7b-11e4-825d-24f5aa658942}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \windows
    resumeobject {48ebdf9a-63ba-11e3-a5c5-e8039ae113a5}
    nx OptIn
    bootmenupolicy Standard

    Continue from hibernation
    -----------------------
    identifier{48ebdf9a-63ba-11e3-a5c5-e8039ae113a5}
    device partition=C:
    path \windows\system32\winresume.efi
    description Windows Resume Application
    locale pt-BR
    inherit {resumeloadersettings}
    recoverysequence {2175f4c9-6b7b-11e4-825d-24f5aa658942}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Windows Memory Tester
    ------------------------------
    identifier{memdiag}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Memory Diagnostic
    locale pt-BR
    inherit {globalsettings}
    badmemoryaccess Yes

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

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

    RAM Defects
    ---------------
    identifier{badmemory}
    badmemorylist 0x10007

    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{2175f4ca-6b7b-11e4-825d-24f5aa658942}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume1
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    ---------------------
    identifier{29ef6fee-6c09-11e4-a5cc-da2b0061475a}
    Using the MiniTool Partition Wizard as suggest, I explored the EFI partition and found the file now set in bcdedit in the same path.

    Saltgrass, I have an Windows 10 DVD and my notebook is activated. But, before having problems to boot into Windows, I could not select in BIOS to boot from DVD/USB (actually trying to fix this is how I screwed up the boot). If the Windows boot is fixed now, I still need to fix that too.

    And should I try the bcdboot c:\Windows command?
      My Computer


  3. Posts : 25
    Windows 10
       #23

    Uzai said:
    And should I try the bcdboot c:\Windows command?
    BCDBoot Command-Line Options

    Repair the system partition. If the system partition has been corrupted, you can use BCDBoot to recreate the system partition files by using new copies of these files from the Windows partition.

    Set up or repair the boot menu on a dual-boot PC. If you've installed more than one copy of Windows on a PC, you can use BCDBoot to add or repair the boot menu.
    Run the following commands at the command prompt (as administrator).

    diskpart
    list volume (Note the volume letter where the Windows OS is installed)
    exit

    bcdboot X:\windows (Replace "X" with the volume letter of the Windows OS partition)

    The picture shows how to fix (bcdboot e:\windows) the Windows 7 startup issue on a dual-boot system.

    UEFI Boot problem after bcedit command-bcdboot-dual-boot-system-installed.png
      My Computer


  4. Posts : 17
    Windows 10
    Thread Starter
       #24

    Right now I have only Windows 8.1 installed. The command still applies?
      My Computer


  5. Posts : 25
    Windows 10
       #25

    Uzai said:
    Right now I have only Windows 8.1 installed. The command still applies?
    Yes.

    Repair the system partition. If the system partition has been corrupted, you can use BCDBoot to recreate the system partition files by using new copies of these files from the Windows partition.

    bcdboot c:\windows

    UEFI: BCDBoot copies the boot files from the Windows partition to the EFI System partition and creates the BCD store in the same partition.

    Legacy BIOS: BCDBoot copies the boot files from the Windows partition to the active partition on the primary hard drive and creates the BCD store in the same partition.
      My Computer


  6. Posts : 2,322
    Win10
       #26

    Have you ever set up TPM on this Laptop ?

    What is a TPM, and Why Does Windows Need One For Disk Encryption?

    Windows Trusted Platform Module Management Step-by-Step Guide


    The manual I found suggests that CD/DVD is the default option for boot device for the Computer but can be changed to USB etc in the Boot Options, but I guess you don't see that? It does say to turn off Fastboot , if trying to use DOS CD's however my guess is they mean if it is MBR based and not UEFI , so best to disable it anyway and transfer the Win10 ISO Files after mounting it , to a Fat32 formatted USB Drive which should be set Active as well with MTPW.

    KB
      My Computers


  7. Posts : 17
    Windows 10
    Thread Starter
       #27

    Kbird, I never touched TPM.

    Initially (since I bought the laptop) I was able to boot from DVD, USB, other SATA devices, etc.. There was a bunch of options in boot menu. I even had installed Windows 10 from a DVD, since the update from Windows 8 was buggy.
    The problem of not being able to boot from other thing than Windows Boot Manager started after I removed linux (for this problem might be better to go in a linux specific forum).

    I guess I will try to reboot the system tomorrow and hope it works after changing the path with bcdedit and using the bcdboot as suggested by Feather. If it works, then I will search how to make it bootable from other devices again.

    You all have been very helpful so far, thanks a lot.

    I will post an update tomorrow.
      My Computer


  8. Posts : 459
    Windows 8&10
       #28

    Uzai said:
    And should I try the bcdboot c:\Windows command?
    No, the BCD store does look correct for a UEFI Boot. You could try it, it appears you have nothing to loose.

    I am not clear on your situation with booting to the DVD. A DVD has two versions, if the DVD is loaded prior to starting the boot sequence, there should be in the Boot Device Menu , a Basic DVD and a UEFI version. If you were running secure boot, it should only be looking for the UEFI version. If you cannot see the UEFI version of the DVD you may have the bios set to boot Legacy.

    But you need to have the CSM disabled and secure boot enabled to see only the UEFI version of install media. But every Bios seems to be different as to how it presents options, so hard to say for sure. And I do not know what the IntegrityServices option in the BCD store does or how it might be effecting your boot.

    I also do not remember seeing so many Firmware Applications in the BCD store. Mine are normally limited to bootable devices only, such as the DVD but you seem to show Recovery options and others. Maybe these are tied to the IntegrityServices entry. Your EFI partition is the second partition on the primary drive?
      My Computer


  9. Posts : 17
    Windows 10
    Thread Starter
       #29

    Your EFI partition is the second partition on the primary drive?
    How can I check this?

    Regarding Secureboot, CSM and Legacy Mode options, I have tryeid all combinations, none worked.

    Just now I remembered something. When using the Recovery, the utility was naming the partition where I had linux installed as D:\ (which was the DVD drive name in the OS). Could it mean something?
      My Computer


  10. Posts : 2,322
    Win10
       #30

    Uzai said:
    How can I check this?

    Regarding Secureboot, CSM and Legacy Mode options, I have tryeid all combinations, none worked.

    Just now I remembered something. When using the Recovery, the utility was naming the partition where I had linux installed as D:\ (which was the DVD drive name in the OS). Could it mean something?

    It will tell you in MTPW under the TYPE column.... post a pic if needed of the view.

    Pics of your Bios Options for CSM etc may help Saltgrass or I pinpoint an issue , you may also need to delete all the keys in the SecureBoot area , it usually has an option to return to factory state or something similar.


    If the Computer was already registered with Win10 and you don't need the Win8 Recovery Partition any more , I would just Wipe the HDD with HDD Low Leveller Formatter , and Boot into a win 10 UEFI install DVD or USB , and forget about all these issues.

    If it has a SSD then doing a Secure Erase will be quicker than a LL Format and better for a SSD.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:49.
Find Us




Windows 10 Forums