hmmm, I think my issue/question is very similar, so I'm going to ask it here.
I am using "Incremental Forever" to backup my boot nvme drive. recently, I had erroneously deleted some IMAP emails, and knew they'd be trapped in my image, inside an OST file. Restoring the OST file didn't work, because before I notice my email deletion error, I had recreated the outlook account (forcing some IMAP folder remapping)... so the existing account on my PC was "different" (even though it connected to the same email account) from that within the Macrium image... it's OST was now incompatible.
Needless to say, Macrium viBoot saved my bacon... this experience kicking off viBoot and Hyper-V education... still so much more to learn.
But when I created my viBoot image, it was based on an incremental further back in the chain... #298 in a weekly chain ending at #300... because I knew that incremental had the OST file I needed to access to export MSG/PST files out of. Booting to it worked like a charm, opened outlook, exported the MSG files I needed, exported the OST as PST just in case.
But this made me think... what happens when #298 gets merged in and disappears during the regular "incremental forever" strategy? I checked my ViBoot folder, it only contained 16Gb of files... a far cry from the 650GB of data of the source image chain, so it must still be referencing the time-bombed image file.
I then thought I'd try the "Backup" option in viBoot... and that triggered my "incremental forever" job... which I promptly aborted... not expecting or wanting the WM to influence my "real" backup chain.
Is the suggestion that the Hyper-V export will somehow bring all the data together (what's in Hyper-V and the incremental macrium chain)? If not, then is there a way to:
1) keep my incremental forever chain going, and
2) somehow export a "Full Macrium backup" based on the incremental #298 point in time?
Because I think a "static" image will make a much better mounting choice for the viBoot/Hyper-V VM... not an incremental (in my case) part of a changing daily chain that will only last a week before it gets merged into the baseline full. Creating a VM off an incremental is a perfect strategy for the quick "grab the files and go" recovery like I originally wanted... but once I started thinking about keeping the VM for a bit longer "just in case"... I started seeing the hole.
@jphughan... I think your idea may be a successful route so long as it shows up in Macrium's drive list during a restore operation... but I'm hoping there's a simpler and/or more "official Macrium" way to do accomplish creating a "full backup" from an "incremental forever" with less steps. Hoping, but not holding my breath
EDIT: Wow... so you have to go to disk management after creating the VHDX to initialize it... but when you get there, you find you could have just created the VHDX in disk management too! And of course once initialized, Macrium sees it too (source/destination).