Unable to resize partition when cloning

Don't clone. Create a full disk mode backup and restore it, using the bootable Rescue Media, to the target disk, at which point you will have the option to resize partitions.

Agreed. Please review this thread (https://forum.acronis.com/forum/126072#comment-391792) to learn the difference between cloning and backup/restore, why cloning can be risky and the steps you should take for both, regarldess of the chosen method - but at least you'll be more aware of the differences and limitations and why we recommend backup/restore over cloning.  

Additionally, we don't have much information on your setup, or any other details to help with the issue.  My guess is that at least one of your disks may have some dirty sectors, which would trigger Acronis to want to do a sector by sector backup and if that's the case, your can't go from a larger to smaller drive because it won't fit when sector-by-sector is used (and it will use sector by sector if bad sectors are detected on the disk).  Or, you may have a dynamic disk which is not supported for cloning at all. 

Do yourself a favor and take a full disk backup of the original drive and then restore that image to the new one.  Result is the same, it is much safer and you get a backup in the process, which is your saving grace in case you run into trouble (which many people have been doing lately - especially those with encrypted drives that don't realize the limitations of having encryption on them when wanting to clone or take a backup).

Thank you for the work-around to cloning.  I appreciate it.

But what does the red circle specifically mean next to the partition; it is not mentioned in the documentation, as far as I can tell?  Can True Image find a bad sector, that is not reported by CHKDSK, in a few seconds, before the cloning process even begins?  Sounds implausible.

Acronis scans all of the partitions on the drive - chkdsk only scans the C drive, so yes, Acronis can find bad sectors not reported by chkdsk.  The only way chkdsk can scan those partitions is if you use your Windows installer and boot to the advanced command prompt, assign each partition a drive letter as a mounted volume and then run chkdsk against each partition.  Just running chkdsk also may not be enough by itself.  You can have bad/dirty sectors in the recovery partition(s), EFI partition, etc.

chkdsk /F = Fixes errors on the disk.  

chkdsk /R = Locates bad sectors and recovers readable information (implies /F, when /scan not specified).  

I run chkdsk /F /R on all drives - SSD's too, even though it may not apply, since it doesn’t' hurt the disk.

Again though, cloning has other limitations that you may be running up against - it does not support dynamic disks (RAID, systems that use caching drives in conjunction with spinning drives, or any drive that is set as dynamic in disk management).  There are other limitations such as disks that have different sector sizes (most SSD's and spinning drives over 2TB use 4K sector sizes now, but older SSD's and spinning drives under 2TB typically use 512Gb sector sizes).

I've not seen the red circle before - perhaps you can post a cell phone pic as a screenshot for additional review?

Personally, unless I have no choice, I do not clone.  There is no safety net and plenty of people have caused themselves trouble they did not expect to encounter (forgot they were encrypted and the encryption software locked them out of the drive after the process started and failed, cloned the blank drive to the data drive on accident, left the clone and original drive attached and tried to boot and the bios changed the bootloader on both because it thought it was the same drive).  Backup and restore, especially when started with the recovery media is the safe, smart option to use whenever possible. 

Further to the comments in the previous post, disk utilities avaialbe from the drive manufacturer are also more likely to find issues with HDD/SSD. They are optimised for the particular type of drive. They can sometimes fix things that chkdsk cannot fix.

Ian