@itcchs-bob There are a couple of things going on here then. (good you found the root of the issue)
Starting with Win10 20H2 microsoft changed the disk structure where they placed the recovery partition at the end of the disk and marked it as non-movable. In the FOG dev branch FOG version 1.5.9.110 and later has a fix for this locked partition.
There are some disk layouts that also are problematic to shrink. Think about it a 512GB hard drive could potentially have a partition starting location beyond the last block on a 256GB disk. So its always problematic haveing a source disk larger than a destination disk. Can FOG deploy larger to smaller disk? Yes as long as all of the conditions are right.
If I’m doing a one to many image deployment, I always create my golden image on a VM with the disk set to the smallest disk I will every deploy to. So for Win10 I create a 70GB disk, and Windows Server a 120GB disk. This way when deployed the disk always grows to the final size.