Bootrec /fixboot → "Element not found"

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 3,840
    Windows 3.1 to Windows 10
       #11

    Currently (Pictured) Disk 1 is the New SSD
    Partition 1 = OEM System Partition
    Partition 2 = Cloned OS Partition - (set to active - thus also System Partition)
    Partition 3 = OEM PBR Recovery Image Partition...
    Partition 4 = WinRE Tools Partition...

    Now that you can see the New SSD you can setup the correct BCD on That Drive via command Prompt admin

    diskpart
    select disk 1
    select partition 1
    format quick fs=ntfs label="System"
    assign letter="S"
    set id=17
    active
    select partition 2
    inactive
    exit
    bcdboot E:\Windows /s S: bios

    Shut down
    remove old Drive
    reboot
    Post results.......
      My Computer


  2. Posts : 17,252
    Windows 11 Pro
       #12

    Kyhi said:
    Currently (Pictured) Disk 1 is the New SSD
    Partition 1 = OEM System Partition
    Partition 2 = Cloned OS Partition - (set to active - thus also System Partition)
    Partition 3 = OEM PBR Recovery Image Partition...
    Partition 4 = WinRE Tools Partition...

    Now that you can see the New SSD you can setup the correct BCD on That Drive via command Prompt admin

    diskpart
    select disk 1
    select partition 1
    format quick fs=ntfs label="System"
    assign letter="S"
    set id=17
    active
    select partition 2
    inactive
    exit
    bcdboot E:\Windows /s S: bios

    Shut down
    remove old Drive
    reboot
    Post results.......
    If you are going to make Partition 1 as the system partition, basically from scratch, isn't the bootsect command needed to write BOOTMGR to the MBR?

    Also, since it was the 12.5GB Recovery partition on Disk 2 that was the Active and System Partition, why not make the cloned 12.5GB Recovery partition the active partition? It should contain all the boot files that were in the original System partition.
      My Computer


  3. Posts : 3,840
    Windows 3.1 to Windows 10
       #13

    BCDboot will create everything required...
    the partition where moved to a different location on New SSD.
    guess he could use the 12.5GB partition in place of 39MB

    I guess his concern was keeps OEM partition anyway...

    Personally I would use Rescue Media and copy any OEM Dell Windows 7 Recovery Files to D:\ Data Drive
    And clean the New SSD Drive - set up 2 partitions and apply a single partition backup..
    I would not have chosen to Clone the original disk
      My Computer


  4. Posts : 35
    Windows 10
    Thread Starter
       #14

    Kyhi said:
    diskpart
    select disk 1
    select partition 1
    format quick fs=ntfs label="System"
    I can't do a diskpart format. With both SSDs connected:

    Code:
    DISKPART> list disk
    
      Disk ###  Status         Size     Free     Dyn  Gpt
      --------  -------------  -------  -------  ---  ---
      Disk 0    Online         1863 GB      0 B
      Disk 1    Online          465 GB      0 B
      Disk 2    Online          223 GB      0 B
      Disk 3    Online           15 GB  3072 KB
    
    DISKPART> select disk 1
    
    Disk 1 is now the selected disk.
    
    DISKPART> list partition
    
      Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    OEM                 39 MB    31 KB
      Partition 2    Primary            452 GB    40 MB
      Partition 3    Primary             12 GB   452 GB
      Partition 4    Recovery           883 MB   464 GB
    
    DISKPART> select partition 1
    
    Partition 1 is now the selected partition.
    
    DISKPART> format quick fs=ntfs label="System"
    
    There is no volume selected.
    Please select a volume and try again.
    
    DISKPART> list volume
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     R   ESD-ISO      UDF    DVD-ROM     4027 MB  Healthy
      Volume 1     D   Data         NTFS   Partition   1863 GB  Healthy
      Volume 2     E   OS           NTFS   Partition    452 GB  Healthy
      Volume 3         RECOVERY     NTFS   Partition     12 GB  Healthy
      Volume 4         RECOVERY     NTFS   Partition     12 GB  Healthy    System
      Volume 5     C   OS           NTFS   Partition    210 GB  Healthy    Boot
      Volume 6     F   WIFI SD      FAT32  Removable     15 GB  Healthy
    
    DISKPART>
      My Computer


  5. Posts : 3,840
    Windows 3.1 to Windows 10
       #15

    Personally I would copy any OEM Dell Windows 7 Recovery Files to D:\ Data Drive

    And clean the New SSD Drive - set up 2 partitions and apply a single partition backup..
      My Computer


  6. Posts : 17,252
    Windows 11 Pro
       #16

    kyhi said:
    personally i would copy any oem dell windows 7 recovery files to d:\ data drive

    and clean the new ssd drive - set up 2 partitions and apply a single partition backup..
    agreed!
      My Computer


  7. Posts : 35
    Windows 10
    Thread Starter
       #17

    OK, so I've established that my Dell recovery partition is toast and nobody knows what the 39 MB partition is. I guess don't need any Dell recovery anyway since:
    • I make daily image backups
    • I have a Macrium Reflect rescue CD handy
    • Any Dell recovery files would be Windows 7 drivers anyway



    As a reminder, my system uses BIOS and MBR; here are the partitions on my old (current) 240 GB SSD:
    Bootrec /fixboot → "Element not found"-toto.png

    So should I reformat the new (500 GB) SSD and clone just the OS C: partition (expanding it, obv.)? What diskpart commands should I issue to make that new SSD bootable? Thanks again for your help.
      My Computer


  8. Posts : 2,790
    Linux Mint 20.1 Win10Prox64
       #18

    Looking at your current Windows disk layout, it is a mess.
    with a fresh install of Windows 1903, disk layout should be:
    System Reserved = 579MB. The rest is C drive.

    Since you cloned the disk, you might have disk signature collision problem, ie. 2 disks with same disk ID. In addition, you used fixboot/bootrec that might screw up the master boot record. Here's my suggestion:

    While Windows is running, open admin command then type:
    NOTE: Make sure disk 1 is your New disk

    diskpart
    select disk 1
    clean
    create partition primary size=579
    format quick fs=ntfs Label="System Reserved"
    select par 1
    active
    assign letter=R
    exit

    This will clean up everything as a brand new disk then create a new 579MB System Reserved partition.

    While Windows is running, Run Macrium, under disk 3 (disk management shows as disk 2 since it starts with disk 0, in Macrium it starts with disk 1)

    click on clone this disk
    Bootrec /fixboot → "Element not found"-p1.jpg
    click on select a disk to clone to...

    Bootrec /fixboot → "Element not found"-p2.jpg

    a windows pop up, select disk 2 (Your new disk)
    Drag drive c and drop next to the 579MB System Reserved
    Bootrec /fixboot → "Element not found"-p3.jpg
    NOTE: By drag and drop, you actually copy the C Drive to the new disk, not cloning.

    On the new disk, Click on "Cloned partition properties" then select Maximum size ... to resize the new C drive to full capacity

    Bootrec /fixboot → "Element not found"-p4.jpg
    Bootrec /fixboot → "Element not found"-p5.jpg
    Bootrec /fixboot → "Element not found"-p6.jpg

    Click next->Finish

    Once done, shutdown the PC, disconnect disk 1 (Your old disk)
    Next, boot up Macrium Rescue disk, click on Fix Windows Boot Problems.
    Follow the sreen and make sure to put a check mark on the System Reserved partition
    Let Macrium rebuild the master boot record, BCD etc...
    reboot the PC. This should boot into Windows.
    If not, Make sure that your new disk is set to be first boot device in the BIOS.
    Last edited by topgundcp; 11 Oct 2019 at 01:59.
      My Computer


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

    topgundcp said:
    fixboot/bootrec that might screw up the master boot record

    How did or does this happen?
      My Computer


  10. Posts : 2,790
    Linux Mint 20.1 Win10Prox64
       #20

    zbook said:
    How did or does this happen?
    Fixboot/bootrec is not enough. Need bootsect to complete. However, Macrium will do all that:

    Bootrec /fixboot → "Element not found"-screenshot3.jpg
      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 05:11.
Find Us




Windows 10 Forums