Macrium Reflect

Yes. Now that you have the correct MacriumService.exe version correctly installed under "Program Files\Macrium\Common\" the other one under "Program Files (86)\Macrium\Common\" is completely redundant. In fact, that updated service executable that was misplaced by the patch was never actually loaded and used anyhow. Basically, what you just did by running the full installer is equivalent to what I did manually with my ad hoc solution.

 

Wow! Go away for 2-weeks in "de islands, mon" and this whole thread has gotten very lively.

I, too, would like to welcome Arvy back to a very active status here in the Wilders Forums, especially the Wilders Macrium Reflect Forum... but I'm sad to hear he has left (active status anyway) the Macrium Forums... his basis in civility and correctness will be sorely missed. Welcome back, Arvy

And, yea, as has been discussed ad infinitum, there have been many, many issues with the release of v7... and they will continue. Arvy and I have both "regressed" to v6 in the interim and, most likely, will remain there until we see some real progress with the v7 current issues... as well as some REAL FEATURES that prove beneficial to the user.

Now it's time for thread catchup everywhere...!

 

Thanks. Welcome back, yourself.

'Fraid so. Their developers' apparent misunderstandings about how the WTS v2 API actually works isn't encouraging. Nor is Nick Sills' tendency to ignore sloppy package production "time bombs" until they actually blow up in everybody's face. He did the same thing with the MRCBT.SYS installation issue until somebody finally picked up my not-so-gentle hints about their careless handling of start=0x00000000 kernel mode drivers being quite risky. It's basically a prevailing attitude problem as I see it ... not helped by a lot of deliberately dismissive distraction garbage in their forums.

 

@Peter2150 -- To avoid any possible misunderstanding, I was referring to the MRCBT installation issues in their v7 release package that rendered some people's machines completely unbootable even in safe mode. That issue has been corrected since then. There was no similar issue with their separate MRCBT v6 beta package release, but if that's what you're using(?), it's no longer available for download/update and it's not "officially" supported as a v6 add-on AFAIK.

P.S.: If you ever decide to remove it for any reason, be very careful about the device class filter and other related registry entries. It also leaves behind $MRCBT data files in the System Volume Information folder of all drives that can't be deleted even when booted to WinPE "rescue" mode.

 

If you're using the v6 beta MrCbtTools.exe, it should remove the device class filter entry itself okay, but I can't recall whether it actually removed the start=0x00000000 entry for the kernel mode driver or just disabled it in place. In the latter case, it can be dangerously problematic in some circumstances where the driver file itself has been removed. For v7, they ignored my early warnings (thus the initially reported issues), but they eventually took my advice to do it the other way around -- i.e., remove the registry entry completely and leave the driver file behind as a much safer and more generally accepted practice.

Happy to hear it. Curious about your handling of $MRCBT file leftovers in SVI folders. After my own CBT v6 beta tests, I was only able to get rid of them by booting to a Linux OS.

 

Ahh, thanks for the File Assassin tip. I see that you're a fellow fan of "ChrisR's" excellent WinPE projects. I didn't install the File Assassin but I have installed the Reflect v6 PE application files themselves under all of my PE multi-boot (3.1, 5 and 10) builds. Reflect runs fine that way if you disable (rename) its taskbar.exe file to keep that out of the way. The screen resolution can be a bit tricky sometimes and I wish I could disable the "drive letter" reassignments, but I guess I'd better not stray off topic here.

 

If you're interested and tell me the exact name of the WAIKFILES----.EXE file under your main Reflect installation, I can give you a command line for extracting your paid version PE application files to replace the free version in the ISO. Nothing "illegal", just what Macrium's PE builder "wizard" does itself.

 

I was getting a 0x01 Error on one of my computers when imaging.
But, since running "chkdsk C:/r", the error has gone.

Has anyone else ever had that error?

 

That error has been seen by users on the Macrium Forum and many have run "chkdsk C:/r" and cleared it up.

 

I don't know what it fixed, if anything.
But, at least Reflect is working again.

 

How to schedule Macrium backup with Windows Task Scheduler only?
I get everything except "Actions" field i.e what Program/Script & arguments should I enter?

 

@Ya5h Kh4n -- I would strongly recommend using Reflect's own user interface (not the Task Scheduler UI) for all scheduling of backup task definitions or scripts as explained in the v6 User Guide or the v7 User Guide. FYI, however, most of the command line arguments are explained in this KB article. A "-g" switch (undocumented) is also used in Reflect's scheduled command lines in order to trigger Full>Diff>Inc order-of-precedence handling.

P.S.: And another undocumented "-s" switch is also required in order to tell scheduled scripts that the command must be run with elevated privileges. That one must be argument #1. The Task Scheduler "configure for" setting is also critical depending on both Reflect and Windows versioning. Why not use the Reflect UI to create at least one TS entry and see the command pattern there?

 

@layman ,

I had seen that one already. But it didn´t end with anything remotely close to an explanation.

Anyway, I don´t want to bother people with this. I guess it will remain a mystery.

 

I guess, Macrium Reflect v7 Free will be a little late...

 

...and since they do not celebrate Independence day (July 4th) in the UK, you're probably right

But I'm not sure what you're really waiting for in the v7 FREE release... v6 is solid as a rock. Other than possibly an updated code base (which has been questionable under v7), what additional features might you be expecting?

Without adding INCREMENTAL imaging to the FREE edition, the new CBT fast tracking cannot be had. The only single feature which would make the FREE edition even more useful then it is would be the RAPID DELTA RESTORE (RDR) functionality they added when v6 PAID edition came about... other than that, I can't think of anything that would be useful. And even that is only useful for those who do restores often (saving time even for those who only do DIFFERENTIAL imaging).

 

As they never included RDR in the v6 free edition, I'd be doubtful of seeing its addition to v7 free. The v6 free edition did, however, include task scheduling and the v7 changeover to the Task Scheduler v2 API has probably given them more difficulties than almost anything else. Nick Sills has even disagreed with his own developers about some of their questionable understandings about how it actually works. It makes me suspect that getting those misunderstandings sorted out may be responsible for much of the delay. They sure wouldn't want to add a badly flawed free edition to the general circulation given its important role in reputation building to date. Their premature release of the v7 paid editions was sad enough.

 

Despite this post,
there is No definite Release Date for v7 Free .

 

When, and IF, Macrium brings the promised CONTINUOUS INCREMENTAL function to v7 (was supposed to be right after release), it will make your hourly incremental setup easier and will be available through the Macrium UI rather than setting up individual hourly incrementals that you have to do currently. Whether that's worth anything to the user in the form of $s, I can't really comment.

It may even have some sort of periodic automatic merging (like in "Shadow Protect") but that is pure guesswork on my part... they've never released specifications on the new CONTINUOUS INCREMENTAL function.

We'll just have to wait and see...