Macrium Reflect

Here you go.

 

It shows Volumes 1 and 5. Looks like I need a better test to determine the Recovery partition that's being used. But I assume it's the Recovery partition just created.

Can anyone help?

 

What's it saying about;

Code:

RAM Defects
-----------
identifier              {badmemory}

??

 

It's a standard entry. Nothing of concern.

 

Thanks!

 

I updated to Windows 10 Anniversary Update yesterday, and it seems my Reflect scheduled backups are broken.
Reflect says that it run successfully, but there is no image file, and I didn't see it run.

 

It is a known problem. See earlier posts.
Try running manually until Macrium issues a fix - else revert to 1511

 

So, are you saying that Reflect doesn't yet work with the Anniversary Update yet?
What 1511?

I can't believe that Macrium wouldn't have been onto this problem earlier.
Insiders would have had this for awhile.

 

See posts following here.
By 1511 I mean the pre-AU version of Win 10.
I agree I would have thought this would have been sorted before AU came out.

 

Pete is correct with his above observations. Turns out each Insider Preview along the path to this Anniversary Release has had different issues with the "new" Windows Task Scheduler (which Macrium uses exclusively). What's been happening is issues have been identified along the way and repaired in the subsequent release... just to lose that fix in the release following the repaired one. Something happened within the MicroSloth code base maintenance system that allowed these "fixes" to get lost in subsequent releases.

This issue is really not on Macrium, it's on MicroSloth... Macrium is scrambling like crazy to get this whole thing fixed with M$. And it wasn't just the Task Scheduler as you should see in the previously posted links about this "Anniversary" disaster. Something serious happened within their Quality Control structure... serious enough where they may wind up rolling the whole update backwards until they figure out what happened.

Windows 10 is not doing well at the moment...

 

This really strikes me as funny...

Not so long ago when Rollback RX had this disaster with Windows updates, all the same folks on this forum who now blame M$ had no problem blaming HDS exclusively for this issue. The universal opinion at this time was that HDS should have known in advance, M$ provided insider preview versions to software manufacturers, so M$ was completely innocent. My point that an Operating System manufacturer had no business changing the partition structure of a HDD during an automatic update without asking users for permission was totally discarded.

Now a similar thing happens to Macrium, and everyone is blaming M$. Double standards? Again I think that changing the task scheduler (knowing very well that many third party software depends on the task scheduler) is something that should not be done without proper warnings, but this is just how arrogant this company is.


Cheers
manolito

 

Hi Mab! It really shouldn't be funny at all. These two situations are like apples & oranges.

...and at that point, they were. They issued the final "preview" edition (no "rings" at that time) appx. 12-days in advance of the official release. Any product manufacturer worth their salt would have taken that preview and did their final testing. HDS did not, and that's why their product blew up on the day of the release... not only with their users but with their own in-house machines.

I totally agree with you but they did it (I hate that arrogance as well). Most partition dependent products (Macrium included) discovered the anomaly and warned their users of the issue... HDS did not.

Once again I don't disagree with the mentioned arrogance... BUT, it's not a "similar thing."

Almost all product vendors (except maybe HDS) are tied to the MicroSloth available Windows 10 rings.. FAST, SLOW & PREVIEW. Even in the Macrium camp, the scheduler issue was discovered quite a while ago and reported back to MicroSloth, not only by Macrium but by a lot of their ring members. A release or two later it was fixed, followed by a subsequent release (in the rings) that was broken once again. As far as I've been able to tell, it was working fine at least up the next to last FAST ring release.

All of a sudden, the Windows 10 Anniversary Edition arrives and not only breaks the Task Scheduler but many other aspects of the OS... Macrium (and many others) got burned. This is not what happened to HDS... they could have easily been aware of their particular issue (and issued appropriate warnings), but were not. I really do not consider these two issues similar at all.

Even this time around there was no warnings from HDS but it wasn't their fault. Many of their users did the Anniversary Update and the system update did not go well. We, as users, know very well it's suicidal to try and do a major OS update with RBrx still installed and alive on the system... there's just too many possible issues. But there are many RBrx users that believe that RBrx is the perfect tool for "monitoring" OS updates... they just don't realize the difference between small periodic monthly updates/fixes and a major OS upgrade. Hopefully, by now, they are at least protecting themselves against these potential "anomalies via an imaging solution. If not... "Hell hath no fury like an OS' scorn (arrogance)."

 

WOW, my full image backup went up 10GB when I upgraded to Windows 1607!!!

 

MPSAN, I believe those are needed to go backward to 1511 if, in the next 10-days, you choose to do that. After that, it should go away (or you can make it go away using "Disk Cleanup").

 

Because I was unable to update Windows 1511 to 1607 I decided to do a clean install. However, now installing Macrium Reflect fails with error 2203...

And I really need to extract some data from my 1511 image... How can I do that when being unable to install Reflect?

(I have a DOS partition with a Reflect ISO that I can boot using grub4dos, but is there a way within Windows?)

 

I may leave it alone for now. So far all is OK except it deactivated my Office 2013. I tried an older OPA backup file and it reactivated Office again. Glad I had that tool.

 

Did you make a bootable recovery disk or USB disk? If so, can't you use that?

 

The ISO in the DOS partition acts like that.

 

Just my 2 pennies......for such a very expensive product, they rely on a "cheap" scheduler rather than having implemented their own scheduler like Acronis, Symantec System Restore, and even freeware Veeam Endpoint Back (and probably many more)?? So, can you blame M$? Yes. But can you also blame Paramount not having their own scheduler? IMHO: Yes too.

 

And today it installs without any error…

 

As per this Macrium Windows 10 Upgrade Issues thread.

This has been posted.

I see I now have a new unallocated partition on both of my hard drives.

1. What is it for?
2. Do I have to select it in my Reflect XML definition?

I have already changed my "Retention Rules Apple To" setting, as suggested.

 

Hadron,

Can you post screenshots of Disk Management?