[TOOL] EzWindSLIC: Easily activate Windows 7/Vista/Server 2008-2022 on UEFI-GPT

Discussion in 'MDL Projects and Applications' started by Deleted member 1435102, Apr 9, 2021.

Tags:
?

Should I use powershell in this script to add more features? Vista will no longer be supported.

Poll closed May 7, 2021.

  1. Yes

    5 vote(s)
    55.6%

  2. No

    4 vote(s)
    44.4%
Page 9 of 23
  1. Deleted member 1435102

    Deleted member 1435102 Guest

    #161 Deleted member 1435102, Jul 1, 2021 (OP)
    Can you please tell how can it be done? Thanks.
     
  2. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #162 JacksMafia, Jul 1, 2021
    i have a question i'm trying to duel boot windows 7& 10 but i installed 7 first and activate it correctly when i install 10 the system goes to boot menu after installation i choose 7 it loads fine but the activation is gone i uninstall it and install it again but it doesn't work
    any help?
     
  3. Deleted member 1435102

    Deleted member 1435102 Guest

    #163 Deleted member 1435102, Jul 1, 2021 (OP)
    The bootloader doesn't work well with dual boot unfortunately.
     
  4. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #164 JacksMafia, Jul 1, 2021
    anyway around it? or it's just a hit and miss
     
  5. Deleted member 1435102

    Deleted member 1435102 Guest

    #165 Deleted member 1435102, Jul 1, 2021 (OP)
    You can try using another method to activate. Which edition are you using?
     
  6. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #166 JacksMafia, Jul 1, 2021
    7 x64 ultimate and i did get it working before on 270f asus but i can't do it on x570
     
  7. Deleted member 1435102

    Deleted member 1435102 Guest

    #167 Deleted member 1435102, Jul 1, 2021 (OP)
    Clean install Windows 7 Enterprise and activate with KMS_VL_ALL
     
  8. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #168 JacksMafia, Jul 1, 2021
    i got it it's so wired but when i boot windows press f8 i get a choice for 2 boot manager both have win 7 & 10 now if i choose the second one activation works fine and i can log in to both 10 & 7 but the first one is no
    why do i have 2 boot managers ? and how to remove the faulty one?
     
  9. Deleted member 1435102

    Deleted member 1435102 Guest

    #169 Deleted member 1435102, Jul 1, 2021 (OP)
    Boot into the one in which activation works fine.
    Then open cmd as admin and post the output of
    Code:
    bcdedit -enum all -v
    and
    Code:
    bcdedit -enum -v
     
  10. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #170 JacksMafia, Jul 1, 2021
    Firmware Boot Manager
    ---------------------
    identifier {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
    displayorder {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    {f8532d74-da58-11eb-848c-fbcfcdd9e266}
    {74f8946d-da32-11eb-846d-806e6f6e6963}
    {e4d8f27b-da78-11eb-a805-806e6f6e6963}
    {41a8bcab-da34-11eb-90ec-806e6f6e6963}
    {41a8bcac-da34-11eb-90ec-806e6f6e6963}
    {41a8bcad-da34-11eb-90ec-806e6f6e6963}
    timeout 2

    Windows Boot Manager
    --------------------
    identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device partition=\Device\HarddiskVolume2
    path \EFI\WINDSLIC\WINDSLIC.EFI
    description Windows Boot Manager
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    displayorder {0216cc47-da81-11eb-93ad-deef3951fb86}
    {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout 10

    Firmware Application (101fffff)
    -------------------------------
    identifier {41a8bcab-da34-11eb-90ec-806e6f6e6963}
    description UEFI:CD/DVD Drive

    Firmware Application (101fffff)
    -------------------------------
    identifier {41a8bcac-da34-11eb-90ec-806e6f6e6963}
    description UEFI:Removable Device

    Firmware Application (101fffff)
    -------------------------------
    identifier {41a8bcad-da34-11eb-90ec-806e6f6e6963}
    description UEFI:Network Device

    Firmware Application (101fffff)
    -------------------------------
    identifier {74f8946d-da32-11eb-846d-806e6f6e6963}
    device partition=F:
    description UEFI: KingstonDataTraveler 2.01.00, Partition 1

    Firmware Application (101fffff)
    -------------------------------
    identifier {e4d8f27b-da78-11eb-a805-806e6f6e6963}
    device partition=\Device\HarddiskVolume2
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8532d74-da58-11eb-848c-fbcfcdd9e266}
    description Hard Drive

    Windows Boot Loader
    -------------------
    identifier {0216cc47-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    custom:15000066 3
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    osdevice partition=D:
    systemroot \Windows
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    nx OptIn
    custom:250000c2 1

    Windows Boot Loader
    -------------------
    identifier {0216cc48-da81-11eb-93ad-deef3951fb86}
    device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{0216cc49-da81
    -11eb-93ad-deef3951fb86}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-us
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    custom:15000065 3
    osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{0216cc49-da81
    -11eb-93ad-deef3951fb86}
    systemroot \windows
    nx OptIn
    custom:250000c2 1
    winpe Yes
    custom:46000010 Yes

    Windows Boot Loader
    -------------------
    identifier {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 7
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    nx OptIn

    Windows Boot Loader
    -------------------
    identifier {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    device ramdisk=[C:]\Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e2
    66\Winre.wim,{f8532d78-da58-11eb-848c-fbcfcdd9e266}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    osdevice ramdisk=[C:]\Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e2
    66\Winre.wim,{f8532d78-da58-11eb-848c-fbcfcdd9e266}
    systemroot \windows
    nx OptIn
    winpe Yes
    custom:46000010 Yes

    Resume from Hibernate
    ---------------------
    identifier {0216cc46-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    filedevice partition=D:
    filepath \hiberfil.sys
    custom:25000008 1
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
    filedevice partition=C:
    filepath \hiberfil.sys
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Memory Diagnostic
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    bootems No

    Debugger Settings
    -----------------
    identifier {4636856e-540f-4170-a130-a84776f4c654}
    debugtype Serial
    debugport 1
    baudrate 115200

    RAM Defects
    -----------
    identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}

    Global Settings
    ---------------
    identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    inherit {4636856e-540f-4170-a130-a84776f4c654}
    {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    {5189b25c-5558-4bf2-bca4-289b11bd29e2}

    Boot Loader Settings
    --------------------
    identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    {7ff607e0-4395-11db-b0de-0800200c9a66}

    Hypervisor Settings
    -------------------
    identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

    Device options
    --------------
    identifier {0216cc49-da81-11eb-93ad-deef3951fb86}
    description Windows Recovery
    ramdisksdidevice partition=D:
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {f8532d78-da58-11eb-848c-fbcfcdd9e266}
    description Ramdisk Options
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e266\boot.sdi



    Windows Boot Manager
    --------------------
    identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device partition=\Device\HarddiskVolume2
    path \EFI\WINDSLIC\WINDSLIC.EFI
    description Windows Boot Manager
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    displayorder {0216cc47-da81-11eb-93ad-deef3951fb86}
    {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout 10

    Windows Boot Loader
    -------------------
    identifier {0216cc47-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    custom:15000066 3
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    osdevice partition=D:
    systemroot \Windows
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    nx OptIn
    custom:250000c2 1

    Windows Boot Loader
    -------------------
    identifier {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 7
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    nx OptIn
     
  11. Deleted member 1435102

    Deleted member 1435102 Guest

    #171 Deleted member 1435102, Jul 1, 2021 (OP)
    Hmm... everything seems ok. Can you post a picture when the computer shows duplicate boot manager.
     
  12. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #172 JacksMafia, Jul 1, 2021
  13. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #173 JacksMafia, Jul 1, 2021
    what about now is it still ok ?
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    bcdedit -enum all -v

    Firmware Boot Manager
    ---------------------
    identifier {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
    displayorder {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    {f8532d74-da58-11eb-848c-fbcfcdd9e266}
    {361a0cec-da39-11eb-9345-806e6f6e6963}
    {e4d8f27b-da78-11eb-a805-806e6f6e6963}
    timeout 2

    Windows Boot Manager
    --------------------
    identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device partition=\Device\HarddiskVolume2
    path \EFI\WINDSLIC\WINDSLIC.EFI
    description Windows Boot Manager
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    displayorder {0216cc47-da81-11eb-93ad-deef3951fb86}
    {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout 10

    Firmware Application (101fffff)
    -------------------------------
    identifier {361a0cec-da39-11eb-9345-806e6f6e6963}
    device partition=F:
    description UEFI: KingstonDataTraveler 2.01.00, Partition 1

    Firmware Application (101fffff)
    -------------------------------
    identifier {e4d8f27b-da78-11eb-a805-806e6f6e6963}
    device partition=\Device\HarddiskVolume2
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8532d74-da58-11eb-848c-fbcfcdd9e266}
    description Hard Drive

    Windows Boot Loader
    -------------------
    identifier {0216cc47-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    custom:15000066 3
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    osdevice partition=D:
    systemroot \Windows
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    nx OptIn
    custom:250000c2 1

    Windows Boot Loader
    -------------------
    identifier {0216cc48-da81-11eb-93ad-deef3951fb86}
    device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{0216cc49-da81
    -11eb-93ad-deef3951fb86}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-us
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    custom:15000065 3
    osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{0216cc49-da81
    -11eb-93ad-deef3951fb86}
    systemroot \windows
    nx OptIn
    custom:250000c2 1
    winpe Yes
    custom:46000010 Yes

    Windows Boot Loader
    -------------------
    identifier {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 7
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    nx OptIn

    Windows Boot Loader
    -------------------
    identifier {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    device ramdisk=[C:]\Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e2
    66\Winre.wim,{f8532d78-da58-11eb-848c-fbcfcdd9e266}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    osdevice ramdisk=[C:]\Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e2
    66\Winre.wim,{f8532d78-da58-11eb-848c-fbcfcdd9e266}
    systemroot \windows
    nx OptIn
    winpe Yes
    custom:46000010 Yes

    Resume from Hibernate
    ---------------------
    identifier {0216cc46-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    filedevice partition=D:
    filepath \hiberfil.sys
    custom:25000008 1
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
    filedevice partition=C:
    filepath \hiberfil.sys
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Memory Diagnostic
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    bootems No

    Debugger Settings
    -----------------
    identifier {4636856e-540f-4170-a130-a84776f4c654}
    debugtype Serial
    debugport 1
    baudrate 115200

    RAM Defects
    -----------
    identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}

    Global Settings
    ---------------
    identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    inherit {4636856e-540f-4170-a130-a84776f4c654}
    {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    {5189b25c-5558-4bf2-bca4-289b11bd29e2}

    Boot Loader Settings
    --------------------
    identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    {7ff607e0-4395-11db-b0de-0800200c9a66}

    Hypervisor Settings
    -------------------
    identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

    Device options
    --------------
    identifier {0216cc49-da81-11eb-93ad-deef3951fb86}
    description Windows Recovery
    ramdisksdidevice partition=D:
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {f8532d78-da58-11eb-848c-fbcfcdd9e266}
    description Ramdisk Options
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\f8532d77-da58-11eb-848c-fbcfcdd9e266\boot.sdi


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    bcdedit -enum -v

    Windows Boot Manager
    --------------------
    identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device partition=\Device\HarddiskVolume2
    path \EFI\WINDSLIC\WINDSLIC.EFI
    description Windows Boot Manager
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    displayorder {0216cc47-da81-11eb-93ad-deef3951fb86}
    {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout 10

    Windows Boot Loader
    -------------------
    identifier {0216cc47-da81-11eb-93ad-deef3951fb86}
    device partition=D:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {0216cc48-da81-11eb-93ad-deef3951fb86}
    custom:15000066 3
    recoveryenabled Yes
    custom:16000060 Yes
    custom:17000077 352321653
    osdevice partition=D:
    systemroot \Windows
    resumeobject {0216cc46-da81-11eb-93ad-deef3951fb86}
    nx OptIn
    custom:250000c2 1

    Windows Boot Loader
    -------------------
    identifier {f8532d76-da58-11eb-848c-fbcfcdd9e266}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 7
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {f8532d77-da58-11eb-848c-fbcfcdd9e266}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {f8532d75-da58-11eb-848c-fbcfcdd9e266}
    nx OptIn
     
  14. Deleted member 1435102

    Deleted member 1435102 Guest

    #174 Deleted member 1435102, Jul 1, 2021 (OP)
    @JacksMafia
    Your mobo might have an option to set the default boot device.
    Enter mobo setup and try to configure the boot order.
     
  15. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #175 JacksMafia, Jul 1, 2021
    i did do that and disabled the faulty one before uploading the first bcdedit -enum all -v and bcdedit -enum -v the second upload is with all boot manager enabled
     
  16. Deleted member 1435102

    Deleted member 1435102 Guest

    #176 Deleted member 1435102, Jul 1, 2021 (OP)
    Yeah, the output seems fine.
    Does it work well for you?
     
  17. JacksMafia

    JacksMafia MDL Novice

    Feb 9, 2015
    26
    0
    0
    #177 JacksMafia, Jul 1, 2021
    for now yes restarted many times logged in to both 10 & 7 and it's fine :) was just running in circles when it hit me that why there is 2 boot managers
     
  18. Deleted member 1435102

    Deleted member 1435102 Guest

    #178 Deleted member 1435102, Jul 1, 2021 (OP)
    Good for you :D
     
  19. Deleted member 1435102

    Deleted member 1435102 Guest

    #179 Deleted member 1435102, Jul 1, 2021 (OP)
    I got less than 40 likes in more than two months here.
    I posted it on reddit on r(slash)p*r*cy and got more than 400 upvotes in less than a day :eek:
    Good for me I guess :p :D
     
  20. Deleted member 1385001

    Deleted member 1385001 Guest

    #180 Deleted member 1385001, Jul 1, 2021 (OP)
    +1 vote too.
    our expectations mostly result in a failure.
     
Page 9 of 23