Yes, that's an okay (if somewhat overly WinRE partitioned) Windows Disk Management image for your "Drive 0", the same one on which your Windows OS is installed. But that does not show us anything about the USB flash drive that you want to use (and were using?) as a "dual purpose" rescue and backup destination device. Plug in your flash drive, if it isn't already, and show us that one.
Booting ISOs is easy. In fact, Grub4DOS can do it directly. No mounting, extraction or formatting required.
Yup. So can Easy2Boot. Lots of options. Depends on whether you want to create a bootable UFD from an ISO file or just boot the ISO in place "as is".
Woaw, this is impressive... http://www.easy2boot.com/add-payload-files/list-of-tested-payload-files Sorry, a bit off topic...
Well, not exactly. Those screenshots do show the file and folder structure and your backup image having been split into 4 GB files as one would expect for a FAT32 partition. However, what I was actually suggesting was a Windows Disk Management screenshot for that USB flash drive just like the one that you posted for your "Drive 0". That would show you how much of that 256 GB flash drive is actually formatted and available for backups and how much of it is unallocated.
https://www.macrium.com/version-7 Makes it sound like v7.1 has been released, does it not? But when I "Check for updates" my copy of Reflect says no updates found. It also doesn't seem to highlight the talked-about option (can't remember what it was called - continuous incrementals or something) to run multiple incrementals per day. I tried using the Downloader application to download a new full installer package using my software key and it only pulled v7.0.2199. I guess if nothing else this might mean we're very close to v7.1.
It sometimes seems to take quite a while for Macrium's download servers to get updated and/or for changes to get registered with whatever CDN service they're using. I find the MIG part of that notice quite interesting where it says that it will "only grant write access to Macrium Reflect 7.1 and any image tools created by us." Almost sounds as if the new version will be running as its own Windows client name (like "NT SERVICE\TrustedInstaller") with specially assigned privileges. I may be forced to install v7.1 temporarily when available just to try it out. I may be wrong, but I think I may sense a potential for some possible "rescue" issues if that's the exclusionary methodology to be employed.
Yup. That shows that your USB flash drive has been formatted as a single 231 GB FAT32 partition. Thus, it has all been made available as a destination for backup image files in the same partition as Reflect's WinPE rescue boot installation. So, apart from the 4 GB file size limitation, the only remaining issue is the one that you raised initially about updating that WinPE rescue build (i.e., rebuild and reinstall it with newer Reflect releases) while also leaving those existing backup images in place. Have you now been able to do that successfully? __ P.S.: If you need it, I can give you a method for manual extraction of the Reflect WAIKFILES package.
Had one hell of a time trying out ViBoot on my current Windows 10 installation. Display and performance issues, the desktop was grey. And Microsoft account errors... Should've used a local account. But my main question is: What about licensing? I currently have Windows 10 Education installed, but booting from Hyper-V uses a different/virtual motherboard... Can something go wrong here?
To quote the relevant KB article: "Macrium viBoot enables you, to instantly create, start and manage Microsoft Hyper-V virtual machines using one or more Macrium Reflect image files as the basis of the virtual machine storage sub-system." I suppose that it's use on one machine with a Reflect backup image from some other machine could possibly raise some licensing issues depending on whether you bought and have retained currently valid licenses for both of them. But that question would be handled best with a direct inquiry to Macrium support.
When you boot the virtual machine using viBoot and a Macrium image, Windows won´t be activated. This is not a problem, since it is a temporary process whose only purpose is to check that the image is bootable and possibly to update it. The advantages of viBoot are that it makes the process simpler and the image doesnt´have to be restored completely to a virtual drive before booting it.
Yes, good point about Windows activation. I assumed, perhaps incorrectly, that @J_L was asking about possible Reflect licensing issues. As for possible updating, AFAIK viBoot won't allow any changes to the backup image itself but stores any changes in a separate file that doesn't get integrated into the backup image.
Do you not understand, Froggie, that your concerns about non-fulfillment of promises made that you more recently reposted in their own forum have already been adjudicated and explained away as inconsequential, if not totally irrelevant, by "The Unofficial Mouthpiece" thus relieving Macrium management of all responsibility for any direct response or actual follow-up of those promises.
I may be a permenant v6 user. So far there is no new feature worth money to me. Nick needs to put a lid on marketing. I just got another email enjoining me to upgrade to 7. The only new feature is this MIG. Whoopie, look at the cost of the upgrade. I have accomplished the same thing for $13US. It's called Pumpernickel. Also I see they are still reporting absurd speed improvement with the new CBT. I have been using it with v6 for over a year, and it is excellent, but nothing like the gains they advertise.
I hope not, but there certainly does seem to be a concerted effort to "out shout" long-time participants who depart too far from certain lines of argument and "unofficial" responses there. Any actual "official moderation" seems to be a last resort. It was only when that reached the actual censorship level that I felt unable to continue posting there with any personal integrity. As you say, something has changed and I don't know exactly what either, but I suspect very high level (inter-)corporate involvement. An OEM bargain driving priorities maybe?
