This is very bad advice.
First up, it's really important to make a clear distinction about whether we are talking about Windows 8 and newer, or Windows 7 and older. The NTFS Health Model got completely redesigned in Windows 8 and the two utterly different systems should not be talked about in the same sentence. You can read all about it here:
Redesigning chkdsk and the new NTFS health model – Building Windows 8
In Windows 8 and Windows 10, chkdsk essentially runs in the background continuously. There is of course a little more to it than that (see link above for full details), but truly there is absolutely no need to force a full manual rescan every month when the disk is being continuously checked as it's used in the background. It'll only stress the disk and put unnecessary wear on your drive.
With regards to Windows 7 and older, which flag the disk as dirty (requiring a full check on next boot), perhaps you could make an argument that performing a forced check each month might help catch disk corruption sooner so you can back-up your data in time. I find seriously problems with this argument though:
1) Once again, it stresses the disk and puts unnecessary wear on your drive.
2) It will still only indicate corruption retrospectively and most of the time not signal a bad drive proactively.
3) Windows will probably find this corruption before you do anyway.
4) There are purpose built tools much better suited to checking a disk's health - SMART, and, you know, actual disk checking tools e.g. SeaTools for Windows, Western Digital Data Lifeguard, etc.
5)
chkdsk can be extremely damaging. Whilst it does occasionally recover file fragments (have you ever been able to open and read one though???), chkdsk's primary stated aim is recover your drive to a non-corrupt state. Back when it was first released hard drive corruption was common from causes like power failure or software bugs. chkdsk fixed your computer for you. Nowadays hard disk corruption is pretty much only caused by hard disk failure, and that's a whole different kettle of fish.
Most of the time chkdsk's "fix" for your drive is to simply delete the corruption. Sure, it does have other fixes in its toolboxes - reindexing orphans for example - but it's primary method of attack against failing blocks (most usually caused by HDD failure), is to mark the blocks as bad and then clean orphans. End result - the data is lost.
Seriously - if my HDD is starting to die, and I don't yet know - I do
not want to find out when chkdsk
deletes all files in any way associated with the corruption. I want to find out when SeaTools for Windows runs some input-output tests on empty space on the disk and tells me the readback wasn't correct.
So, all in all, monthly runs of chkdsk not advised. As with all regular maintenance and security (e.g. disk defrag, virus scans, Windows Update, firewall etc.), Windows 10 handles it admirably on its own and is best left alone to do its thing in peace :)
Addendum: I don't recommend monthly SeaTools for Windows runs either due to very high stress they put on the drive. Keeping an eye on your SMART statistics? There's merit in that. But, of course, they're only for the most part statistics and must also be treated with caution.
