New boot disk doesn't appear in BIOS boot devices but does in F8 menu

Page 4 of 4 FirstFirst ... 234

  1. Posts : 39,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #31

    For the recovery partition please run these commands in administrative command prompt:

    reagentc /info
    reagentc /enable

    Post images of the results into this thread.

    If the recovery partition remains disabled then perform an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade

    If that creates an additional recovery partition then the inactive one can be deleted.

    If it fails to create a recovery partition then one may be able to be created manually.



    @NavyLCDR may be able to comment on the before and after results below.


    When the disk par info bat file results were compared before and after there were some changes:


    Code:
    Disk 2 is now the selected disk.
    
    Intel Raid 1 Volume
    Disk ID: 1D085C27
    Type   : RAID
    Status : Online
    Path   : 6
    Target : 2
    LUN ID : 0
    Location Path : PCIROOT(0)#PCI(1F02)#RAID(P06T02L00)
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : Yes
    Pagefile Disk  : Yes
    Hibernation File Disk  : No
    Crashdump Disk  : Yes
    Clustered Disk  : No
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 3         System Rese  NTFS   Partition    101 MB  Healthy    System  
      Volume 4     C   _C_ (LOCAL   NTFS   Partition    921 GB  Healthy    Boot    
      Volume 5                      NTFS   Partition    542 MB  Healthy            
    
      Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    Primary            101 MB  1088 KB
      Partition 2    Primary            921 GB   104 MB
      Partition 3    Primary            542 MB   921 GB
      Partition 0    Extended             9 GB   921 GB

    Code:
    Partition 0 is now the selected partition.
    
    Partition 0
    Type  : 0F
    Hidden: No
    Active: No
    Offset in Bytes: 989668048896
    
    There is no volume associated with this partition.



    Boot Loader (BEFORE)

    Code:
    Windows Boot Loader
    -------------------
    identifier              {72ed70d8-6fde-11ec-89b4-c4ee3de2d164}
    device                  ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{72ed70d9-6fde-11ec-89b4-c4ee3de2d164}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment
    locale                  en-US
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice                ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{72ed70d9-6fde-11ec-89b4-c4ee3de2d164}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50f8-d45b-11e0-a7d7-ee688687ea3c}
    device                  unknown
    path                    \Windows\system32\winload.exe
    description             Windows 7
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {799f50f9-d45b-11e0-a7d7-ee688687ea3c}
    recoveryenabled         Yes
    osdevice                unknown
    systemroot              \Windows
    resumeobject            {799f50f7-d45b-11e0-a7d7-ee688687ea3c}
    nx                      OptIn
    
    Windows Boot Loader
    -------------------
    identifier              {799f50f9-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fa-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment
    inherit                 {bootloadersettings}
    osdevice                ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fa-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    nx                      OptIn
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50fd-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[C:]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fe-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment (recovered) 
    locale                  
    osdevice                ramdisk=[C:]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fe-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50ff-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f5100-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment (recovered) 
    locale                  
    osdevice                ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f5100-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \windows\system32\winload.exe
    description             Windows 10
    locale                  en-us
    inherit                 {bootloadersettings}
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \windows
    resumeobject            {b2b2fe46-74a8-11ec-89d8-f46d04653ffa}
    nx                      OptIn
    bootmenupolicy          Standard




    Boot Loader (AFTER)

    Code:
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \Windows\system32\winload.exe
    description             Windows 10
    locale                  en-us
    inherit                 {bootloadersettings}
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {289d5684-71aa-11ec-b609-f46d04653ffa}
    nx                      OptIn
    bootmenupolicy          Standard
    
    Windows Boot Loader
    -------------------
    identifier              {72ed70d8-6fde-11ec-89b4-c4ee3de2d164}
    device                  ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{72ed70d9-6fde-11ec-89b4-c4ee3de2d164}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment
    locale                  en-US
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice                ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{72ed70d9-6fde-11ec-89b4-c4ee3de2d164}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50f8-d45b-11e0-a7d7-ee688687ea3c}
    device                  unknown
    path                    \Windows\system32\winload.exe
    description             Windows 7
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {799f50f9-d45b-11e0-a7d7-ee688687ea3c}
    recoveryenabled         Yes
    osdevice                unknown
    systemroot              \Windows
    resumeobject            {799f50f7-d45b-11e0-a7d7-ee688687ea3c}
    nx                      OptIn
    
    Windows Boot Loader
    -------------------
    identifier              {799f50f9-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fa-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment
    inherit                 {bootloadersettings}
    osdevice                ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fa-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    nx                      OptIn
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50fd-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[C:]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fe-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment (recovered) 
    locale                  
    osdevice                ramdisk=[C:]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f50fe-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {799f50ff-d45b-11e0-a7d7-ee688687ea3c}
    device                  ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f5100-d45b-11e0-a7d7-ee688687ea3c}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment (recovered) 
    locale                  
    osdevice                ramdisk=[unknown]\Recovery\799f50f9-d45b-11e0-a7d7-ee688687ea3c\Winre.wim,{799f5100-d45b-11e0-a7d7-ee688687ea3c}
    systemroot              \windows
    winpe                   Yes



    This was present before and disappeared after:

    Code:
    Resume from Hibernate
    ---------------------
    identifier              {b2b2fe46-74a8-11ec-89d8-f46d04653ffa}
    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




    Before
    Code:
    resumeobject            {b2b2fe46-74a8-11ec-89d8-f46d04653ffa}

    After
    Code:
    resumeobject            {289d5684-71aa-11ec-b609-f46d04653ffa}
      My Computer

  2. DeepThought's Avatar
    Posts : 18
    Microsoft Windows 10 Professional (x64) Build 19044.1466 (21H2)
    Thread Starter
       #32

    zbook said:
    This was present before and disappeared after:

    Code:
    Resume from Hibernate
    ---------------------
    identifier              {b2b2fe46-74a8-11ec-89d8-f46d04653ffa}
    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
    Before
    Code:
    resumeobject            {b2b2fe46-74a8-11ec-89d8-f46d04653ffa}
    After
    Code:
    resumeobject            {289d5684-71aa-11ec-b609-f46d04653ffa}
    I'm not sure why anything from Hibernate would've been present during this troubleshooting. I used powercfg /hibernate off a couple of weeks ago, before I even upgraded to Win10, to remove hiberfil.sys from C: drive to free up space for the upgrade. I never re-enabled it. That's puzzling.

    - - - Updated - - -

    zbook said:
    For the recovery partition please run these commands in administrative command prompt:

    reagentc /info
    reagentc /enable

    Post images of the results into this thread.
    pic5 - reagentc /enable failed with error "The Windows RE image was not found."

    I followed the instructions here...
    How to Convert ESD to WIM (Install.ESD to Install.WIM) in Windows ISO >> Winhelponline
    then here...
    How to Extract Specific Files from Windows 10 ISO (Install.wim) >> Winhelponline
    then here...
    Canít Reset Windows 10; Could not find the Recovery Environment >> Winhelponline

    pic1 - reagentc /enable succeeded.

    pics 2-4 show screens I was able to access after I booted to recovery using Start - Power - hold shift down - Restart

    At this point, what is left to do? By using "Intel Volume1_HDD_Data" as the Boot Option in my BIOS, somehow it boots to the "Intel Volume0_SSD_Boot" volume automatically now, without me needing to use the F8 boot options menu. It's a kludge, but it functions. Perhaps BIOS has the wrong volume label but it's addressed correctly? I've seen stranger things, and this BIOS is old (last had an update in 2013). Perhaps they had an unpatched firmware bug.

    Thank you for helping me get my Win10 install in proper working order. Did I miss anything? Is anything else still busted?
    Attached Thumbnails Attached Thumbnails New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220117-2-reagentc-success.png   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220117-1-reagentc-failure.png   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220117-3a-recovery-screen-1.jpg   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220117-3b-recovery-screen-2.jpg   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220117-3c-recovery-screen-3.jpg  

    Last edited by DeepThought; 6 Days Ago at 12:26.
      My Computer


  3. Posts : 39,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #33

    The recovery files are on C: (partition 2) not (partition 3)

    Consider an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade
      My Computer

  4. DeepThought's Avatar
    Posts : 18
    Microsoft Windows 10 Professional (x64) Build 19044.1466 (21H2)
    Thread Starter
       #34

    zbook said:
    The recovery files are on C: (partition 2) not (partition 3)

    Consider an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade
    Forgive my ignorance. I never did master Windows as a SysEng.
    1. What is in partition 3, then? Why did the Win10 upgrade create it?
    2. What will an in place upgrade repair do? Is that the same as sfc /scannow?
      My Computer


  5. Posts : 39,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #35

    Partition 3 = recovery partition
    Partition 2 = data partition

    Windows will create new recovery partitions when it needs more space and cannot widen the current partition.

    An in place upgrade will allow Windows to install a new working recovery partition.

    If there were corruption problems identified with scannow that were not able to be fixed an in place upgrade repair can fix many corruptions.
      My Computer

  6. DeepThought's Avatar
    Posts : 18
    Microsoft Windows 10 Professional (x64) Build 19044.1466 (21H2)
    Thread Starter
       #36

    zbook said:
    Partition 3 = recovery partition
    Partition 2 = data partition

    Windows will create new recovery partitions when it needs more space and cannot widen the current partition.

    An in place upgrade will allow Windows to install a new working recovery partition.

    If there were corruption problems identified with scannow that were not able to be fixed an in place upgrade repair can fix many corruptions.
    zbook, thank you for the greater insight. I performed the in-place upgrade repair through to successful completion with no discernible results...
    1. "Intel Volume0_SSD_Boot" remains absent from my BIOS Boot Option menus.
    2. "Intel Volume1_HDD_Data" remains the only viable boot option in BIOS.
    3. ...yet, doing so continues to boot from Volume0... with no errors.
    4. Investigating Volume1... (D: drive) again, there is no boot partition on it, and no OS recovery or other data, that could allow it to be bootable.


    However, help me tie up one last loose end. Earlier, you said "The recovery files are on C: (partition 2) not (partition 3)", yet later you also said "Partition 3 = recovery partition". With my limited knowledge, could you explain that further?
      My Computer


  7. Posts : 39,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #37

    Please run:

    DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

    Tuneup_plus_log.bat Click here to go to the BSOD batch repository to download and run this batch file.



    The files for Windows recovery can be missing or on a separate partition (preferred) or in the primary partition (C: or data partition).
      My Computer

  8. DeepThought's Avatar
    Posts : 18
    Microsoft Windows 10 Professional (x64) Build 19044.1466 (21H2)
    Thread Starter
       #38

    zbook said:
    The files for Windows recovery can be missing or on a separate partition (preferred) or in the primary partition (C: or data partition).
    So, I'm still not clear on what I have, exactly. Is my recovery in C:, in the 3rd partition, both, or neither? How can I tell? Also, can the 3rd partition be safely removed, so I can run mbr2gpt successfully? I have a pair of 4TB SSDs burning a hole in my pocket right now, and I'd like to use them to their full potential here, but the last time I tried mbr2gpt, it failed, assuming because it couldn't create the partition layout it needed due to the limitations of MBR. I say that, but of course, I don't really know that's the case. Looking for some guidance in that respect.

    zbook said:
    Please run:

    DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

    Tuneup_plus_log.bat Click here to go to the BSOD batch repository to download and run this batch file.
    New stuff uploaded.

    - - - Updated - - -

    I anticipate you asking for another Tuneup, given the first one found errors, so here's the second...
    New boot disk doesn't appear in BIOS boot devices but does in F8 menu Attached Files
      My Computer


  9. Posts : 39,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #39

    The in place upgrade repair was successful in creating new recovery files on the data or primary or C: partition.
    Before reagentc /info had displayed disabled.
    The command reagentc /enable had failed earlier in the thread.

    Now reagentc /info displays enabled.
    And it displays partition 2.

    Code:
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
    
        Windows RE status:         Enabled
        Windows RE location:       \\?\GLOBALROOT\device\harddisk2\partition2\Recovery\WindowsRE
        Boot Configuration Data (BCD) identifier: fa6abf5f-793b-11ec-89e2-be275d3b4446
        Recovery image location:   
        Recovery image index:      0
        Custom image location:     
        Custom image index:        0
    
    REAGENTC.EXE: Operation Successful.

    The free space on C: is now 9 GB.
    The free space was reduced by the creation of Windows.old.
    The Windows.old by default is deleted in 10 days.

    Code:
    Disk 2    Online          931 GB     9 GB

    The first scannow displayed: Started on Wed 01/19/2022 at 14:28:50.99
    Code:
    Windows Resource Protection found corrupt files but was unable to fix some of them.

    The second scannow displayed:
    Code:
    Windows Resource Protection did not find any integrity violations.

    Code:
    2022-01-19 14:32:12, Info                  CSI    0000024b [SR] Cannot repair member file [l:27]'Windows.StateRepository.dll' of Windows-StateRepository, version 10.0.19041.844, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2022-01-19 14:32:12, Info                  CSI    0000024d [SR] Cannot repair member file [l:27]'Windows.StateRepository.dll' of Windows-StateRepository, version 10.0.19041.844, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2022-01-19 14:32:12, Info                  CSI    0000024e [SR] This component was referenced by [l:160]'Microsoft-Windows-Client-Desktop-Required-Package051021~31bf3856ad364e35~amd64~~10.0.19041.1288.AA7F1466784E999C2FAC1A65CD50CF105991C268A7D4D174F6FE640CBC6096F8'
    2022-01-19 14:32:12, Info                  CSI    00000251 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\Windows.StateRepository.dll; source file in store is also corrupted

    The second set of scannow: Started on Wed 01/19/2022 at 15:40:37.39
    Code:
    Windows Resource Protection did not find any integrity violations.

    The BIOS is Legacy.

    Please indicate what you want to do with GPT instead of MBR.

    One of the disk drives is dynamic.

    Did you want to convert one or all disk drives.
    The MBR2GPT requires a Windows drive and is not designed to work on non-Windows drives.


    For BIOS settings the computer displayed only two options.
    MBR and UEFI compatible.
    This may be UEFI with CSM.
    The 4TB drive can be MBR and use 2TB.

    If the BIOS is switched to UEFI compatible the FAT32 EFI partition can be tested.


    Please post new images of Disk Management (widen columns and rows so that characters are not cut off) and Mini Tool Partition Wizard.

    @NavyLCDR may have some ideas.
      My Computer

  10. DeepThought's Avatar
    Posts : 18
    Microsoft Windows 10 Professional (x64) Build 19044.1466 (21H2)
    Thread Starter
       #40

    I had an issue with Windows update where it kept reporting "Your device is missing important security and quality fixes" and kept failing on "2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5009543)"...at least half a dozen times. I finally ran "dism.exe /online /cleanup-image /restorehealth" and that seemed to fix it.

    So, regarding the GPT issue, I have a couple of 4TB SSDs that I want to replace the 1TB SSDs I have as my current boot devices. I'll use AOMEI Backupper like last time to clone the partitions to them. I want to run mbr2gpt so I can utilize the full 4TB on my C: drive.

    The free space on C: is now 9 GB.
    The free space was reduced by the creation of Windows.old.
    Correction, the 3rd partition of the volume is 9GB of free space. C: drive is the 2nd partition and is 921GB with 810GB free. Yes, Windows.old was created, and I'm aware it will delete in some days.
    Attached Thumbnails Attached Thumbnails New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220120-1a-windows-update.png   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220120-2-disk-manager.png   New boot disk doesn't appear in BIOS boot devices but does in F8 menu-toad-20220120-3-minitool-partition-wizard.png  
    Last edited by DeepThought; 3 Days Ago at 12:28.
      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:44.
Find Us




Windows 10 Forums