@bond007fink The Could not adjust the bad sector list error generally indicates that NTFS metadata (bitmap / bad cluster map) is in an inconsistent state. FOG relies on ntfsresize and partclone to safely shrink and copy NTFS volumes, and if those tools cannot reliably map the filesystem, the capture will correctly fail.
This can occur even when the drive is physically healthy. A filesystem marked dirty will prevent offline resize operations. In that case, FOG is behaving as designed — failing here is preferable to deploying a potentially corrupt image to multiple systems.
We are seeing this more frequently after recent Windows updates, which appear to be leaving or reasserting the NTFS dirty bit.
Please boot the source machine into Windows and run a full filesystem and encryption check. Make sure to adjust the drive letter if your system volume is not C:.
chkdsk /x /r /f C: manage-bde -ff C:Also ensure hibernation is disabled, as it can leave NTFS in a state that prevents offline resizing:
powercfg -h offIf capture succeeds when resizing is disabled, that further confirms this is a Windows filesystem state issue rather than a FOG defect.
FOG cannot safely work around filesystem states imposed by other vendors. Ignoring NTFS safety checks would risk data integrity, and that is not something FOG should or will do.