Robert in CA wrote:
I'm trying to find the file but man it's difficult. I don't know
where you looked but I have no idea where to look on C: and
I'm opening all the folders looking and finding nothing. So
I tried to do a search on XML

https://postimg.cc/n9HWwjHL

then I tried XML Validation and it found nothing.

https://postimg.cc/JGYFPzS1

I thought of using Agent Ransack to look but it hasn't found anything.
I used XML Validation -Error -'disk''1''partition'1' is not valid- as
the file name.

https://postimg.cc/VdJgsBH8

Thoughts, suggestions,
Robert.

Look under "Disk Image" in Macrium Reflect, then "Backup Definition Files".
Those are file names in the list. The list has:

File Name Path
--------- ----

We can use one of your old pictures for inspiration.

https://postimg.cc/XB0wq709

The word "activated" in Agent Ransack, might dig up the first file.
It depends on which file you've been using, as to what word
would make a good search term. For the second one you could
try "1-2-20" as a search term, as I don't think the hyphen is
part of regex or something, and Agent Ransack probably won't
get confused by that.

Once you open the file with Notepad (and not Internet Explorer like
Windows wants to do it), you can search in Notepad for

"The source of the backup"

to find the beginning of the section with the list of
what is to be backed up. You can see how the entries
have "balancing" declarations, the closing indicator
using the "/" . The "/image_entry" closes off the first stanza.
Notice the extensive usage of "comments" in the form of !-- .
The first stanza has three comment lines, the comments not
being needed for the second stanza.

image_entry id="1"
!-- disk is the 1 based index of the disk to be imaged --
!-- id is the disk signature and is used in place of the disk index if specified --
disk id="13796CED"1/disk
!-- partition is the 1 based index of the partition on the disk --
partition1/partition
/image_entry

image_entry id="2"
disk id="13796CED"1/disk
partition2/partition
/image_entry

It is saying, quite plainly, that it uses the "disk id" field,
to identify a disk by name, in preference to the numeric ID
(which varies according to what SATA port or SATA cable is
used). The order of discovery might depend on cable order, so
the 1 part might not be as accurate. It assumes you went
around swapping disk cables, but it also assumes the
disk is still in the machine ("13796CED" which is the diskID
of the disk in my machine used to make up an example to show you).

Now, on your screen, if you go back to Reflect and select
"Disk Image" "Create a backup", the current value of the
"disk id" of your disks is shown in the graphic display
there, for each drive. So the current values won't seem
a mystery.

I hope this is sufficient for you to "verify" the text in
the XML, aligns with the graphic screen contents
(the "current situation").

You can make a brand new fresh backup definition if you
want. Part of the purpose of checking the file out, is
so you can understand in your own mind, what change you
made that threw it off. It's better for you to see it,
than for me to keep making bad guesses :-) You have the
evidence, I don't.

Paul