make trying to remove more verbose

the cleaner now prints
Trying to remove E052D8A6-224A-4C32-8D37-2E0AE162364D

It should print the name too
It should be in a form easily parsed by scripts

one option is something like this
blacklist name (or guid if there is no name)
in addition to
remove name (or guid if there is no name)

Also, since sometimes we need both, can you handle an RE of the form
re|guid

i.e. the extended re format, which would be nice in that it's easier to find it.

Consider also outputting in CSV format?
CSV is nice as it allows blank fields:
operation,guid,name
remove,x,E052D8A6-224A-4C32-8D37-2E0AE162364D
blacklist,y,E052D8A6-224A-4C32-8D37-2E0AE162364E

In any event the error message should have a solid anchor
so that awk/grep/sed pipelines can easily create the blacklist and update remove commands. It's close, just not quite there, says your first user.

Would be a real nice thing to be able to say
Given this set of remove, comment, and blacklist, did I cover all the DXEs and if not what did I miss.

Start by locating the cleaner entry point that emits “Trying to remove” and inspect how remove and blacklist operations are represented. Clarify which output format, extended regex behavior, and coverage reporting are required before changing the output; done should be demonstrated by tests showing stable, script-parsable records containing the operation, GUID, and name.