Just a heads up for Macrium Reflect users who have updated to Windows 10 1511 (TH2). The update may have changed the sizes of the C: and Recovery partitions, so a new backup set will have to be started with a Full. It should be automatic if you have a Differential or Incremental backup scheduled you should get a full.
Great, Froggie. I assume she can tell it to save ALL folder Backups (The Free will do it too, but no file/folder option). I know she can extract a file from an Image (so can FREE), but she wants a backup of a few data folders as well, since we only do a full image about once a month. To be honest, it sure seems like Reflect costs a lot more than I thought. Free does all I want, but my wife wants more. Isn't that always the case?
I just did the Image after my 1511 Upgrade and it was 11GB larger than before! That tells me that my update left big upgrade files on my system that I no longer need. Does anyone know where they may be? UPDATE...I guess it is $Windows-BT and WS along with Windows.old!
Start/All Apps/Windows Administrative Tools/Disk Cleanup Select <C:\> and say OK. A list of optional file groups to "cleanup" will show up and left over upgrades and previous Systems should be there... feel free to SELECT them and get rid of them. That's how I got rid of all the old "upgrade from" stuff when I came from either W7 or W8.1...
MPSAN, After Disk Cleanup your C: drive used space will be less than before the upgrade. 1 GB in my case.
OK I did this to get rid of windows.old, BT and WS...just change lines for directory you want from elevated CMD Prompt. takeown /F C:\Windows.old\* /R /A icacls C:\Windows.old\*.* /T /grant administrators:F rmdir /S /Q C:\Windows.old\ Disk Cleanup wanted me to remove a bunch of driver packages and ESD files but not sure I should do that. I may try to remove them as I believe the driver packages they refer to are old packages and they keep the current ones.
Does anyone know if Macrium Reflect Home works on Microsoft Surface Pro 4 using its "Add Recovery Boot Menu" option?
WARNING: If you're running a Legacy-MBR system and are not using a MicroSloth SYSTEM RECOVERY PARTITION, the Windows 10 1511 Update will definitely change the size of your ACTIVE Windows partition... this in turn may cause REFLECT to do funny things since the partition you're protecting has just changed in size. If you're not currently BOOTing through a MSRP, the new 450mB MSRP partition created during the update process will be neutered (wasn't made ACTIVE for BOOTing purposes). The now shrunken ACTIVE BOOT Windows partition will still be BOOTable, just smaller This is exactly what happened during the Windows 8.1 to Windows 8.1 Upgrade 1 update. Windows created a new 450mB System Reserved Partition by carving away enough storage to do this from the ACTIVE Windows partition. Havoc was cause for Rollback RX users as well as most imagers that "think" they know how large the partition they are protecting is. I just witnessed this... errr, anomaly and following the change. Be careful with this upgrade.
Thanks for the warning. LOL, for folks like me who only do full disk image backup/restore from boot media, there is no problem with any Windows OS upgrade, as long as the file system is still NTFS.
My Win10 (MBR/Legacy) partition was resized 450 MB smaller and a Recovery partition was created in the space. This happened on a few other computers too but on other computers this didn't happen and there was no extra partition. You can move the Recovery files back into the the Win10 partition and delete the Recovery partition, or leave it alone. Your choice.
just to clarify - if you are using macrium or other imaging programs (as opposed to RX), then you might end up with a neutered MSRP partition which is useless and wastes space but otherwise there is no damage? Your macrium will work as before, old images, chains...?
That is correct... no damage to what exists in the way of images. But Macrium will not continue existing schedules/chains due to the fact that the partition being imaged has changed in size... it will state in cannot find a matching image for that chain any longer, a new chain will have to be started.
What do you mean by "neutered"? (English is not my native language) I had Windows 10 installed in 1 partition spanning my entrire SSD, but indeed I now see a 450 MB Recovery Partition at the end (thanks for the tip!).
Neutered means neither ACTIVE or PASSIVE. It was actually a bad reference 'cause I thought originally it was the MicroSloth System Reserved Partition and when that's in use, it's usually ACTIVE in the BOOTing path. Clearly it's only the MicroSloth SYSTEM RECOVERY PARTITION... no BOOT path involvement at all, sorry.
As I pointed out in my post above, the recovery partition size is increased and the size of C: is decreased during the update. if you did not have a recovery partition before then one will be created. The recovery partition is the first partition after C: If you are using UEFI boot and GPT you will have a system partition at the start of the drive (this has not changed). You will also have a 128MB (32MB on smaller discs) reserved partition (MSR) before C: (this has not changed). It is worthy noting that the MSR just sets aside a chunk of file system for Windows to use if it needs it. There is no data in the MSR. If you have deleted it you can get it back using partitioning tools or DISKPART (the MSR is not visible in WIndows DIsk Managemen tool). As the size of partition C: has changed you will need to start a new backup set with a "Full" to image this. If you want to include the MSR partition you will have to ensure it is selected. I think it just shows as an unformatted partition in Macrium Reflect.
Due to resizing, my hardware ID changed, and macrium had to be re-activated online after the Win 10 update.
That surprises me very much. That partition resizing will not change the hardware ID of the disk involved, and as such, should not change the hardware ID of the SYSTEM itself. If it did, that's a real issue with W10, not Macrium. If the Macrium Hardware ID changed then there's an issue there. It's a disk utility, and as such, is designed to handle both disk size changes as well as partition size changes without the need to re-Activate. At least it's easy to remedy through Macrium SUPPORT.
I just did my first backup after the update and Reflect didn't warn me, create a new full backup or did anything else... I just got a 40gb incremental. Should I be worried?
Marcelo, if your system already had the 450mB RECOVERY PARTITION previously, or had at least 450mB of unallocated space available, I believe the update would not have affected your imaging activities. Since REFLECT didn't warn you of any backup set change, your imaged partition did not change in size.
I just updated Win 10 to the new (updated) build. When I went to do an inremental to an external it created an new full chain and said it could not find an existing chain of backups. Is that normal or did something go wrong I should be concered about? Thanks
If your system has not included a MicroSloth RECOVERY PARTITION before that was at least 450mB, it does now. And that partition was created by carving off 450mB from your current Windows partition. After doing that, Reflect will no longer see the same size partition it has been managing during your incremental processing. It has no choice but to start a new chain with the smaller partition in its first new image. Check your partition structure...
