Understood, and probably a wise decision. I'm still very much at the "experimental" stage with Linux myself ... with a lot of very generous help...
Seeing v7.1.2722 at the top of the Reflect application when it's running in the regular Windows working environment does not necessarily mean...
That EasyBCD trick only works if the Linux OS is installed in a partition on the same physical drive as Windows. Besides, I consider any need for...
If you plan to install Linux and multi-boot with both OSes, you'll avoid confusion if you either install each on it's own drive with its own boot...
Transfer rates are primarily (although not exclusively) governed by the hardware and its connection "pipelines" and ports. Not all USB drives are...
You could try hitting Reflect's WinPE Refresh option, but the only explanation I can think of offhand would be some drive configuration (e.g.,...
That's definitely not normal. Clicking on the "Select a different target disk" option (screenshot 1 below) should provide a complete listing of...
You're dealing with two separate issues. Version numbers should match if you want your Reflect installation to be fully updated and...
Nothing at all needs to be installed on the destination drive (or any other except the backup file source itself, for that matter) in order to...
Do you not have rescue media created with the option to support either boot method -- i.e., either MBR or UEFI booting? If you do, you should be...
In this case it can. In the case of the previous major version change, you're right. The v5 to v6 upgrade changed backup file formats so that...
Of course it does. My old WinPE rescue media created with various Reflect v6 releases can still work with the Reflect 7.1.2722 version that is...
@jima -- Yes, sorry about the misunderstanding. It's actually a Windows Defender feature of the Fall Creators Update not limited to just some...
Well, I did ask about it in my first response to jima's initial post about this issue. As there was no reply to my question about that...
Well, that "saving c:jim/doc/xml (something like that)" message is at the heart of the issue and it really needs more precise verbatim...
You mean that you log into Windows as Jim (a member of the Administrators group) to run Reflect? I'm not being "picky"; it's an important...
Yes, that's what I meant and that is where Reflect saves its backup task definition files by default ... not just their names but the actual XML...
Good. Glad if that helps to clarify things for you. And you're entirely welcome.
It was quite a while after v6.3.1835 that I "upgraded" to v7.1 and I "waffled" a few times after doing it. :)
More likely to be a folder permissions issue than an AV issue IMO. Although Reflect should always run with elevated privileges, I'd take a minute...
To the best of my recollection, the WAIKFiles package file version has always matched the Reflect application version and it still does when...
Not a problem. My only concern is to avoid any possibility of being mistaken here as an advocate, "gatekeeper", "fanboi" or any other kind of...
That's why I said "if you want to". I updated mine because I don't completely trust Macrium's current series of release notes to mention each...
Yes, that shows that you downloaded and ran the full installer for Reflect v7.1.2695. However, you'd need to do the same with the full installer...
That is interesting inasmuch as it shows v7.1.2695 and the current release is or should be v7.1.2722, but the only way I got my WAIKfiles package...
Separate names with a comma.
