Macrium Reflect

Discussion in 'backup, imaging & disk mgmt' started by Stigg, Nov 23, 2013.

  1. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    No, the C:\Boot folder is definitely created by Reflect. If you delete that folder and build Rescue Media, you'll see it come right back. The item I'm now not sure about is the Bootmgr file. It's definitely a Windows file, not a Reflect file, since as I said above it has existed since Windows Boot Manager was introduced in Vista to replace NTLDR. But individual BCD entries do not have their own files, and in fact on modern UEFI systems, Windows Boot Manager lives on the EFI partition anyway, not the Windows partition. So I'm not entirely sure why that file is ending up on the root of C on some systems with Reflect installed.
     
    Last edited: Dec 16, 2021
  2. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    4,092
    Location:
    Mexico
  3. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    Reflect creates the entire C:\Boot folder. Perform a clean install of Windows in a VM or something. It won't have a C:\Boot folder. Then install Reflect and open Rescue Media Builder. You'll now have a C:\Boot folder. So the entire C:\Boot folder is created by and meant for Reflect, not Windows as you said.
     
  4. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    4,092
    Location:
    Mexico
    Now i'm very intrigued with this statement of yours :)

    These are two IFL /IFW images I have as backups:
    Windows 7 x86 backup image from a clean install, MR was never installed in there

    Cboot-lappy.png



    Windows 10 Education x64 backup image, MR was never installed in there

    Cboot-pc.png


    Edit:
    MR 7.3.6391 Free installed on my W7 x86 laptop and Rescue Media created

    Cbootmr.png

    Cbootmr2.png

    Am I missing something?
     
    Last edited: Dec 16, 2021
  5. Minimalist

    Minimalist Registered Member

    Joined:
    Jan 6, 2014
    Posts:
    14,648
    Location:
    Slovenia, EU
    I use Macrium Reflect, and created boot ISO and all I got in boot folder is macrium subfolder without all other subfolders as shown above.
    I also moved boot folder to other partition (using settings in Macrium) so ATM I have no boot folder on my C: drive (should be there if it's part of a system).
     
  6. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    4,092
    Location:
    Mexico
    :argh:
    I know what's going on...

    I use to consolidate winre partition and Windows partition.

    Not sure but I think that's the reason.
     
  7. Minimalist

    Minimalist Registered Member

    Joined:
    Jan 6, 2014
    Posts:
    14,648
    Location:
    Slovenia, EU
    Yes that should explain it :)
     
  8. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    The boot folder and the bootmgr file were not there on the C partition and appeared only after the Macrium installation. When I uninstalled Macrium, the boot folder was removed, but the bootmgr file remained.

    If it makes any difference, my system is Windows 11, and I have Macrium 8 Trial.
     
  9. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    @Mr.X Yes, if you ever stored an extracted WinPE or RE environment on your C partition, that would result in a Boot folder, because a root folder called "Boot" is indeed part of a standard WinPE/RE environment -- which is why you'll find a Boot folder on the root of actual Rescue Media and regular Windows installation media. But it's not part of a standard full Windows environment. And of course it's entirely possible for other applications to decide to use a folder with the relatively generic name of "Boot", so Reflect isn't necessarily the ONLY way to end up with a folder of that name on your Windows partition.
     
  10. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    7,168
    Location:
    USA
    True because if you open the boot folder the folder inside is named Macrium.
     
  11. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,348
    Just updated Macrium 8.06.392 on a pc (HP Z420) I am not using all the time. It was still on V7 and I updated to a new version and then was offered Version 8. On this pc I am using the free version. Update went through and thought it best to redo the rescue media ( boot menu, usb and cd)
    Both CD and rescue stick have problems - generally I can boot up into the rescue environment but at times I am being asked about missing drivers. Problems are that the attached drives (relevant for image source) cannot be seen and mouse and keyboard
    are having issue. I tried a tested and working stick I had done a few weeks ago and retested today done for my normal pc (HP z1) and using this on the Z420 worked fine for mouse and keyboard but required a storage controller. I downloaded storage driver from HP and it let me install and then it worked.

    I redid the creation of the stick and now I am even more confused. It seems various ports work for booting up or in live mode but only USB 3 ports are working in recovery mode for reading. Is this normal? I am still getting the attached error message but just ignore it now and assuming I am using the relevant ports, things work. IMG_2813.jpg
     
  12. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    I guess the bootmgr file is a Windows file with "hidden" attributes. Am I right? Does Macrium's Rescue Media Creation use the bootmgr file? I wonder if Macrium changes the bootmgr file's hidden attributes for the Rescue Media Creation and leaves it unhidden.
     
  13. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    7,168
    Location:
    USA
    An interesting thought but I don't know how to verify it. I just checked the creation date on the boot folder and it is October 2016 which is when I purchased Macrium. The evidence so far makes me want to agree that Macrium created this.
     
    Last edited: Dec 20, 2021
  14. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    The Bootmgr file has both Hidden and System attributes set, which is why it doesn't appear if you simply choose to show hidden files. You also have to disable "Hide protected operating system files".
     
  15. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    Just fyi, Reflect Rescue has a built-in screenshot capability that you can access by clicking the camera icon in the taskbar. The result will be a file that is both smaller and more legible.

    In terms of the USB ports, being able to use them for booting is separate from being able to use them after the booted OS has loaded. This became an issue for Windows 7 users on newer systems with USB 3.x ports because the WinPE 3.1 kernel has no native support for USB 3.x, so people who tried to boot their systems from flash drives that contained unmodified Win7 install media and were plugged into a USB 3.x port landed in an environment where Windows Setup could not see the flash drive it had just booted from. The reason is because at boot time, the system firmware controls the USB ports, but when an OS loads, that gets handed off to the OS -- at which point the OS will need to support it in order to maintain access to those ports and the devices plugged into them.

    In terms of why you're having an issue, more information would be helpful. What version of WinPE/RE are you using for your Rescue Media build? What version of WinPE/RE is your previous, working Rescue Media build using (boot it and check the title bar along the very top of the interface to check)? Do you have the "Use host drivers for USB devices where possible" option checked? Have you tried building with WinPE 10/11 and NOT checking that option?
     
  16. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    On my Win 11, the bootmgr file is there on the C partition without enabling Show hidden files and without disabling Hide protected operating system files.
     
  17. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    Ok, I'm not sure how to account for that. It's certainly possible to remove those attributes from that file to cause it to appear as a normal file, but I haven't seen that happen automatically myself, even on systems that have Reflect installed.
     
  18. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    The bootmgr file should be read-only, hidden, and protected operating system file, right? How to make it a protected operating system file?
     
  19. aldist

    aldist Registered Member

    Joined:
    Nov 8, 2017
    Posts:
    915
    Location:
    Lunar module
    There are probably plenty of ways, I use the Attributes Editor 0.9.3.0 Portable, built into the Explorer toolbar.
    12.png
     
  20. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    If you don’t want to use a third party application, open Command Prompt as admin and enter this:

    attrib +s +h c:\bootmgr
     
  21. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    The command made the bootmgr file a hidden and protected operating system file. Is the bootmgr file originally a read-only file too?
     
  22. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    798
    Location:
    US
    Not to my knowledge, since there are scenarios where it would be appropriate to modify it.
     
  23. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    Thank you for your support and time.
     
  24. aldist

    aldist Registered Member

    Joined:
    Nov 8, 2017
    Posts:
    915
    Location:
    Lunar module
    This is the default, I have not changed any attributes
    07.png
     
  25. khanyash

    khanyash Registered Member

    Joined:
    Apr 4, 2011
    Posts:
    2,241
    OK, I have enabled the read-only option. bootmgr Properties-Advanced-File attributes-The two options are enabled-Are these the "Archive" option in your screenshot?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.