The devil is hiding in the details…"...You really need to be guided down this path better. People should be asking how big is your data pool (what you want to backup?). - Eg. How much data is on C:\?
- Do you have any other drives or partitions?
- Do you have OneDrive or any cloud software?
- How old is your computer and hard disk?
- How much of this data changes per week? and per month?
- Do you run any database software, or development applications?
- Do you run any virtualisation software (Vmware, HyperV, etc)?
- What are your system specifications please? CPU? RAM? Storage?
and so on..."
My program requirements:
- The Backup program must make an exact digital copy of all system disk partitions,
- All files of the Original disk and the restored Copy must be equal in checksum.
- It is unacceptable to delete original files from the Copy and add new files.
- To create a Backup and to Restore from a Backup, I use a flash drive (or DVD) with a bootable image of the Program (i.e., "Backup from the outside"), therefore, all of the above applies to backup from a bootable flash drive (DVD):
1. Acronis – was good until 2012, for Windows 7… For Windows 10, Acronis program:
– does not see the hidden service partition "Backup (MSR)" 16 Mb(UEFI)
- Windows Embedded, IoT editions, Windows 10 LTSB / LTSC are not supported (Acronis True Image)
- after Recovery, changes the file C:\Windows\bootstat.dat
- after restoring from backup, the program modifies these parts of the Registry: [HKEY_LOCAL_MACHINE\SOFTWARE] and [HKEY_LOCAL_MACHINE\SYSTEM]
2. Terabyte Drive Image
- The program has a complex interface, so an unprepared User can ruin the disks.
- after Recovery, changes the file C:\Windows\bootstat.dat
- the program does not change the Registry, but incorrectly specifies the drive letters during Backup, so before backup, you must manually assign the correct letters to all drives(You can assign the correct letters in the program settings)..
3. EaseUS - creates hidden files on the System disk after Backup:
C:\{XXX }.CBM
C:\EUMONBMP.SYS
... After that, I stopped further checking. …
4. Macrium Reflect
- changes Registry files after BOOTING from a USB flash drive into Computer memory(!)
for v.7.3. modifies this part of the Registry [HKEY_CURRENT_USER]
for v.8 – v.10 modifies these parts of the Registry [HKEY_CURRENT_USER] and [HKEY_LOCAL_MACHINE\SOFTWARE]
- v.8.1 does not copy files C:\pagefile.sys and C:\hiberfil.sys
5 AOMEI Backupper
- After Restoring from Backup, it changes this part of the Registry [HKEY_LOCAL_MACHINE\SYSTEM]
- Starting from version 6, removes(!) before Backup from the original Windows files:
C:\pagefile.sys; C:\swapfile.sys; C:\hiberfil.sys
NOTE:
part of the Registry [HKEY_CURRENT_USER] is a file C:\Users \[Your User]\NTUSER.DAT
part of the Registry [HKEY_LOCAL_MACHINE\SOFTWARE] is a file C:\Windows\System32\config\SOFTWARE
part of the Registry [HKEY_LOCAL_MACHINE\SYSTEM] is a file C:\Windows\System32\config\SYSTEM
P.S. Now I using Macrium Reflect 7.3(BOOT CD), because this program fully meets all the requirements, with the exception of Registry changes.
I hope that Macrium Reflect 7.3 uses the Registry only to correctly assign letters to disk partitions.
My System for test: Windows 10 21H2 LTSC x64 [MSDN]; m/b Z77-HD3(BIOS-MBR); HDD WD 500Gb
Last edited:
My Computer
System One
-
- OS
- Windows 10
- Computer type
- PC/Desktop
- Manufacturer/Model
- Windows 10 21H2 LTSC x64 [MSDN]; m/b Z77-HD3(BIOS-MBR/UEFI); HDD WD 500Gb