Multiple copies of Windows 10 in MSCONFIG Boot tab

Page 1 of 3 123 LastLast

  1. Posts : 152
    Windows 10 Pro x64
       #1

    [SOLVED] Multiple copies of Windows 10 in MSCONFIG Boot tab


    For as long as I can remember the General tab in MSCONFIG always had the Selective Startup option checked with the Use original boot configuration not checked as follows.
    Multiple copies of Windows 10 in MSCONFIG Boot tab-msconfig_1.png


    When I check the Use original boot configuration option the default switches to Normal startup as shown below.

    Multiple copies of Windows 10 in MSCONFIG Boot tab-msconfig_2.png

    I then go to the boot tab and what I see is shown below.

    Multiple copies of Windows 10 in MSCONFIG Boot tab-msconfig_3.png
    If I apply these settings and reboot I crap out immediately with boot failures. The only way to fix things is to restore a disk image that I took before I started my quest to oblivion.

    The reason I am doing this was to get back to normal startup mode. I've read that Selective startup is not an issue and it has been working fine for quite a long time. I'm just curious as to what is screwing up the boot process? I suppose the three Windows no longer exist. Delete is grayed out in MSCONFIG but I can delete them with another program. I deleted the last 2 entries thinking the first one was good. Got the same boot error when I left them there.
    Last edited by streetwolf; 03 Sep 2019 at 08:16. Reason: SOLVED
      My Computer


  2. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) bcdedit /enum all

    9) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    10) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of
      My Computer


  3. Posts : 18,432
    Windows 11 Pro
       #3

    What we really need to see is the output of bcdedit
      My Computer


  4. Posts : 152
    Windows 10 Pro x64
    Thread Starter
       #4

    As you can see below there is only one boot loader on my system as long as I do not check the use original boot configuration option. Let me be clear that the way things are now I have no problems whatsoever. I am just curious what these three other boot loader entries are. As mentioned, they are probably old entries which are no longer valid and therefore cause boot failures. Also notice, in a previous MSCONFIG screen shot, that the top entry of the MSCONFIG image that shows three boot loaders is not described the same as the screenshot at the bottom which is the one I use.

    I have done all the suggested steps in the past except for wmic recoveros set autoreboot = false as I am not familiar with what this does until I do some research.

    Btw.. Doyou guys have Normal Startup checked off? If so, is use old configuration checked but grayed out?

    Microsoft Windows [Version 10.0.18362.329]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>bcdedit /enum all

    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    timeout 1

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume3
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {7f215fa1-b895-11db-b50c-c8f94e3b1201}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \windows\system32\winload.efi
    description Microsoft Windows 10
    locale en-US
    inherit {bootloadersettings}
    osdevice partition=C:
    systemroot \Windows
    resumeobject {7f215fa1-b895-11db-b50c-c8f94e3b1201}
    nx OptIn

    Resume from Hibernate
    ---------------------
    identifier {7f215fa1-b895-11db-b50c-c8f94e3b1201}
    device partition=C:
    path \windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    filedevice partition=C:
    filepath \hiberfil.sys
    pae Yes
    debugoptionenabled No

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

    Windows Legacy OS Loader
    ------------------------
    identifier {ntldr}
    device unknown
    path \ntldr
    description Earlier Version of Windows

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

    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}

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}
    Attached Thumbnails Attached Thumbnails Multiple copies of Windows 10 in MSCONFIG Boot tab-msconfig_4.png  
      My Computer


  5. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    In startup and recovery system failure the default setting is automatic restart.
    When automatic restart is checked it is easy to miss BSOD.
    When automatic restart is unchecked when there is a BSOD you should see a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys

    The wmic command unchecks automatically restart if it is not already unchecked.

    When possible please post the results of the other administrative command prompt commands and disk management.
      My Computer


  6. Posts : 152
    Windows 10 Pro x64
    Thread Starter
       #6

    I have done the other commands many times even before I discovered the three boot loader entries. I tried all the means I know where to locate these three 'wierd' entries using 3rd party programs and looking at the BCD file and checking out the registry. I can't find them.

    One thing I haven't tried is checking the use original configuration, get the three other bootladers, delete them in my other program that let's me delete them and then go back and uncheck use original configuration which might set things back to normal startup or I can do it myself. Hopefully the correct bootloader will be there and will be bootable.

    My aim is to have normal startup checked with the correct bootloader as shown in the last screenshots. As mentioned things work just fine as they are, so I don't want to make a working configuration not work. I seems to have a fallback by restoring a disk image of a good system so I can play around with all of this.

    - - - Updated - - -

    If you guys check use original config if not checked already do you get additional boot loader entries? Just make sure you don't apply anything as that will save them and possibly prevent you from booting.

    - - - Updated - - -

    Found this.. The Msconfig Startup Selection Reverts from Normal to Selective Startup
    I haven't nothing checked in Advanced Troubleshooting Settings dialog box however.
      My Computer


  7. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    When using a HD selective startup has a faster boot.
    When using a SSD it has substantially smaller impact on boot times.
    So selective startup can be a useful feature.
      My Computer


  8. Posts : 152
    Windows 10 Pro x64
    Thread Starter
       #8

    I fired up a vanilla Windows 10 VM. Looking at MSCONFIG it also has Selective startup checked and use original config is NOT checked. This is like my production machine. However, when I check use original config the Normal option gets checked and the boot tab shows the exact same name so I assume if I saved it it would boot. Since I haven't reinstalled Windows on my VM might be the reason other Windows boot loaders don't show up.

    My aim is to use Normal startup with only the boot loader appearing on the boot tab that let's me boot. The three that show up are no good.
      My Computer


  9. Posts : 41,462
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    There are log collectors used in another forum room.
    Please run each V2 and DM and upload into this thread:
    BSOD - Posting Instructions
      My Computer


  10. Posts : 18,432
    Windows 11 Pro
       #10

    On dozens of computers since Windows 7, Selective Startup is always selected because the Normal Startup option just simply will not stick. I may be able to select it and reboot once, but once it reboots it goes right back to selective startup. So I just don't worry about it.
      My Computer


 

  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 20:11.
Find Us




Windows 10 Forums