Running chkdsk on a BOOTCAMP volume 2019 16" MacBook Pro - Prior to Cloning BOOTCAMP with WinClone

2019 16" MacBook Pro - Catalina 10.15.7 - 4TB NVMe SSD

Boot Camp Assistant install of Windows 10 (21H1)

WinClone 9

With a fresh BOOTCAMP install I can run chkdsk (no parameters) repeatedly without any errors.

If I run chkdsk /b (AS directed by Two Canoes) on the BOOTCAMP volume prior to cloning, one of three things occur  (not consistent)

     ONE - chkdsk /b seems to complete but when Win10 restarts I get the BSOD with the error:

                "Stop code: "BAD_SYSTEM_CONFIG_INFO"

     TWO - chkdsk /b appears to mark 90% of the BOOTCAMP volume as having "bad sectors"

(TechTool confirms there are no issues with SSD.)

     THREE - chkdsk /b seems to complete but subsequent running of chkdsk reports"

                    "The master file table's (MFT) BITMAP attribute is incorrect"

                    "The Volume Bitmap is incorrect."

                    "Windows has checked the filesystem and found problems."

                    "Please run chkdsk /scan to find the problems and queue them for repair"

Online research seems to indicate that running chkdsk /b includes the functionality of chkdsk /r (according to Microsoft) and that running chkdsk /r on todays SSDs has been known to erroneously marks sectors as bad when they are not.  In fact, most sources indicate that there is no reason to run chkdsk /r on an SSD as the SSD controller takes care of monitoring "bad Sectors' and marks them so they are not used.

If, on the other hand, I do a fresh Boot Camp Assistant install and run chkdsk (no parameters) and get repeated results without any errors and then run chkdsk /f to check the file system i am back to:

                    "The master file table's (MFT) BITMAP attribute is incorrect"

                    "The Volume Bitmap is incorrect."

                    "Windows has checked the filesystem and found problems."

                    "Please run chkdsk /scan to find the problems and queue them for repair"

Running chkdsk /scan reports no errors EVERY TIME I run it.  I can alternate between chkdsk and chkdsk /scan and each time chkdsk reports the MFT error and chkdsk /scan reports that there are no errors. How can chkdsk report errors but chkdsk /scan NOT report errors??????

(For what it's worth. I also have a 2014 MBP - El Capitan (10.11.6) PCI SSD - BOOTCAMP install of Windows 10 (1709) and use an older version of WinClone (5). I run chkdsk /b on the BOOTCAMP volume, as WinClone requests, every time I do a clone and it runs without issue or errors... Something is clearly changed with a) newer versions of Windows 10 - b) newer SSDs that is causing these chkdsk errors???)

So....

My question for participants in this forum are:

Does anyone run chkdsk on a BOOTCAMP volume on an SSD with any regularity???

(I do ONLY because WinClone directs us to do so prior to cloning the BOOTCAMP volume)

If so, have you run into any issues similar to those I described above?

Any WinClone 9 users out there with a relatively new mac (with an NVMe SSD) running Windows 10 (21H1)??? Do you run chkdsk (or any other utility) to confirm the integrity of the BOOTCAMP volume prior to cloning??

I'd appreciate any insight or guidance Apple Communities user might have to offer.

Thanks

John