Reflect Backup Files / Sets not Shown in Recovery Environment
-
Reflect Backup Files / Sets not Shown in Recovery Environment
I booted to the Macrium Recovery Environment for Reflect v8 for my PC which has a system drive C and another drive D for Reflect backups. I can browse to find the backup files on drive D in the recovery environment. However, when I add the path D:\Reflect Backups no backup files or sets are shown, Why is nothing shown when the files exist and the path is correct?
Update. I discovered the issue is that my backup drive has disk letter X which the Macrium Reflect environment uses as its boot drive letter. My drive X then gets reassigned to another letter. I have no problem if I choose a drive letter other than X. I reported the issue to Macrium.
Last edited by Steve C; 22 Jun 2021 at 13:49.
-
-
Are you sure you do not have a backup - mounted as a virtual drive and therefore showing a random letter in your case X
-
Are you sure you do not have a backup - mounted as a virtual drive and therefore showing a random letter in your case X
No since I set the drive to be X:
-
-
Steve C
I am sorry, I must be misunderstanding what your apparent problem that you have asked for help in the Macrium forum is.
If like me you have Macrium RE as a boot option in bcd
as below on my dual boot
Microsoft Windows [Version 10.0.19043.1052]
(c) Microsoft Corporation. All rights reserved.
C:\windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume4
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {34da881c-84ca-11eb-8ec8-1c6f65ff401e}
displayorder {34da881f-84ca-11eb-8ec8-1c6f65ff401e}
{current}
{0b04c33c-84cd-11eb-b626-1c6f65ff401e}
toolsdisplayorder {memdiag}
timeout 10
Windows Boot Loader
-------------------
identifier {34da881f-84ca-11eb-8ec8-1c6f65ff401e}
device partition=D:
path \windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
osdevice partition=D:
systemroot \windows
resumeobject {34da881e-84ca-11eb-8ec8-1c6f65ff401e}
nx OptIn
detecthal 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 {34da881c-84ca-11eb-8ec8-1c6f65ff401e}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
-------------------
identifier {0b04c33c-84cd-11eb-b626-1c6f65ff401e}
device ramdisk=[C:]\boot\macrium\WinREFiles\media\sources\boot.wim,{ramdiskoptions}
path \windows\system32\boot\winload.exe
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\WinREFiles\media\sources\boot.wim,{ramdiskoptions}
systemroot \Windows
detecthal Yes
winpe Yes
then the last entry for the boot loader shown on my mine is Macrium and as you see it is a ram disk - the letter allocated is usually X.
I will be interested to see the reply from the macrium experts.
-
Yes, I chose the worst drive letter which is X! Reflect should prevent users from using drive X or ensure their recovery drive boots to a drive not already in use.
I received this reply from Macrium:
Thanks for your feedback,
The letter "X" is for the RAM drive in the rescue media so Reflect expects not to have backups stored on it.
I understand your point and I have passed it onto our development team for evaluation.
Just to clarify, as a workaround don't use "X" as the backup drive letter.
Last edited by Steve C; 24 Jun 2021 at 08:48.
-
The letter "X" is for the
RAM drive in the rescue media so Reflect expects not to have backups stored on it.
as I said
then the last entry for the boot loader shown on my mine is Macrium and as you see it is a
ram disk - the letter allocated is usually X.
-
Just to be contrary I now use Z and all is fine!
-
Steve
Cheers
Good Yorkshire - phrasing there.
Thought it had to be the ramdrive letter.
Brilliant software IMHO = must be best of the free ones.
It has never let me down and has solved issues on multi boot systems more than once.
-