Alleged corruption found in the $Boot file?

I did a routine CHKDSK on my C: drive (SSD), in Windows 10, 64-bit. Got this beauty:

"chkdsk /scan" is aborting due to corruption found in the $Boot file.
"chkdsk /f" will be required to repair the volume.

Thing is, upon repairing (required a reboot), the alleged errors are still there. Which makes me think that maybe this is false alarm. Samsung Magician found no errors on my disk. And CrystalDiskInfo reports no bad/reallocated sectors, or any errors of any kind either.

I did, at some point, use a utility called Partition Assistent, which transformed my MBR to GPT. Not sure if that could be related (as I hadn't run a CHKDSK since).

There are no file system errors on the drive at all, btw. Just a reported boot file corruption. And no errors found with powershell.

I would have ignored this, if I did not, indeed, get an occassion where Windows 10 won't boot (I know GPT has a lot of redunancy). So, maybe there's something odd, after all.

And suggestions left? Thanks.

indianacarnie said:

You could try running a system file check if you haven't yet. It should repair or replace any corrupted or missing files.

Run SFC Command in Windows 10 - Windows 10 Customization Tutorials

As expected, SFC reported "Windows Resource Protection did not find any integrity violations."

I'm really suspecting Partition Assistent, which transformed my MBR to GPT. Can't prove it, though; but *do* find it a bit troublesome the scheduled Windows CHKDSK (needing a reboot) can't fix the issue.