I have noticed a recent anomaly with MR8.1 that, at this point, won't allow me to run an unquestioned comparison... I have no idea what's going on.
While imaging a multi-BOOT System (EFI, MSR, Win10 OS, Win11 OS & Recovery) I experience a very weird anomaly. While imaging between NvMEs (different internal SOURCE and TARGET), The LIVE OS partition images at the expected speed while the non-LIVE OS partition images at a speed 10x lower. This occurs regardless of whether the LIVE OS partition is either Win10 or Win11... makes no sense at all. Both are standard NTFS partitions, one LIVE and one hidden. It almost acts like it's viewing the hidden partition as though it's an unsupported FileSystem. I see the same kind of imaging speed differences between LIVE NTFS partitions and hidden EXT<n> partitions. Macrium (like HBS) must image the "unknown" format (EXT<n>) in a forensic mode, having to read every sector of DATA defined in the partition... this creates a much longer imaging operation for those partition types.
I only bring this up when I noticed Bespoken's latest MR8.1 imaging... his MR8.1 time is double his HBS time, this should not be the case when using identical SOURCE and TARGET devices. Although my anomaly (multi-BOOT) is not the same as Bespoken's, the massive difference between MR8.1 and HBS is the same. Remember, both use the exact same DATA compression algorithms during their imaging processes.
I believe something has changed with MR8.x's Windows interface recently, probably due to a possible Windows update. I have never before seen this type of anomaly and I've used HBS and MR8.1 side by side for years.
Just some food for thought...
While imaging a multi-BOOT System (EFI, MSR, Win10 OS, Win11 OS & Recovery) I experience a very weird anomaly. While imaging between NvMEs (different internal SOURCE and TARGET), The LIVE OS partition images at the expected speed while the non-LIVE OS partition images at a speed 10x lower. This occurs regardless of whether the LIVE OS partition is either Win10 or Win11... makes no sense at all. Both are standard NTFS partitions, one LIVE and one hidden. It almost acts like it's viewing the hidden partition as though it's an unsupported FileSystem. I see the same kind of imaging speed differences between LIVE NTFS partitions and hidden EXT<n> partitions. Macrium (like HBS) must image the "unknown" format (EXT<n>) in a forensic mode, having to read every sector of DATA defined in the partition... this creates a much longer imaging operation for those partition types.
I only bring this up when I noticed Bespoken's latest MR8.1 imaging... his MR8.1 time is double his HBS time, this should not be the case when using identical SOURCE and TARGET devices. Although my anomaly (multi-BOOT) is not the same as Bespoken's, the massive difference between MR8.1 and HBS is the same. Remember, both use the exact same DATA compression algorithms during their imaging processes.
I believe something has changed with MR8.x's Windows interface recently, probably due to a possible Windows update. I have never before seen this type of anomaly and I've used HBS and MR8.1 side by side for years.
Just some food for thought...
