AOMEI Backupper version update

This new version 8.0.0 has a refreshed GUI and some other changes.

• Brand-new user interface and interaction experience: A fully refreshed visual design with a more intuitive layout and streamlined workflows makes every use smoother, easier, and more efficient.
• Added "Lock": When enabled, a password is required each time AOMEI Backupper launches, effectively preventing unauthorized access and comprehensively safeguarding your backed up data and privacy.
• Fixed some known bugs.

After using Ventoy , with latest AoMEI 8 on it , I can only boot AoMEI in Wimboot ( after choosing AoMEI in Ventoy ). When choosing " normal boot" , the program wont start and PC shows a black screen !
What goes wrong , HOW(??) to fix it..........??
Made the backup-ISO within the AoMEI program , it downloaded a PE from the AoMEI-site to make the backup-ISO.

Just tested this - what a total disappointment - apart from some pathetic animations, virtually no difference to previous version apart from lock function (which I would not use anyway).

It still has the major weakness on partition backups that you can only restore one partition at a time.
Why it needs to differentiate between partition and disk backups is a mystery to me.

It STILL does not have any drag and drop capability to reorder partitions during a restore. You have to do it in a clumsy restore one partition at a time (multiple restores in effect).

To quote Bill - this is "Much Ado About Nothing".

FYI: I tend to agree with the review of Version 8.0.0. I have had a few irritating issues with both this and the earlier version 7.5.
I think a lot of the internal software uses VC8 run-time and this is 2005 vintage as far as I can tell. I am unsure if it is currently in step with the current Windows11 security updates.

Cloning works efficiently enough, however, power/tech users need to be aware of a couple of irritating gremlins:
1) If you have identical internal disks, and say clone from C to E, you often see big differences in the target size after. It turns out that unless you drop into "Restart Mode" (WinPE), it uses VSS to copy, that have unexpected restrictions. There are registry entries under FilesNotToSnapshot under BackupRestore (inside HKEY_LOCAL_MACHINE\SYSTEMCurrentControlSet\Control) that stop Outlook *ost and *oab plus others from being copied. There may be other things missed.
2) At the end of ANY clone, Backupper makes the assumption I want to boot from the cloned disk, messes with the BCDBOOT part of the BCD, and reboots into the wrong disk (i.e. changes the boot order). The SSD slots might have different performance, so I want to have the original DISK 0 booted from!
3) After cloning, the cloned disk is left mounted, which is not good security from a Ransomware perspective. My old Paragon software ALWAYS unmounted the clone, and I NEVER had a boot order issue. I now have to rename the clone, then remove the drive letter with Disk Management.

NOTE: that last issue caused a BIG problem recently, when I forgot to un-mount the cloned disk, and a Windows update kicked in, that needed 2 reboots.
The KB5070773 update started on the booted C disk, but after its first reboot, tried to complete the WinRE update on the WRONG DISK. This left the Partition Table for the Recovery Partition locked on the C drive, that stopped any new disk clone working.

Fortunately, AOMEI support were very helpful, and provided a very useful procedure to delete and recreate the Recovery Partitions on both drives.
You need to download the latest Windows 11 ISO and mount it, and 22 complex commands later, it is done!

I have put in a request to AOMEI to have a tick-box to unmount the cloned target disk at clone completion.

By the way, I have found that if you run "Create Bootable Media" in the TOOLS UI, it DOES create a bootable DVD, BUT the "makedisc.exe" routine inside that tool hangs at 99%m but DOES eject the disk. I thinks its cleanup is failing in a hard loop. That DVD DOES have BACKUPPER integrated, and DOES create an exact clone copy, of identical size, as the OS is not getting in the way, as it runs inside the WinPE, so presumably uses XCOPY.