[6.9.2] Invalid Access Timestamp on File

I'm not entirely sure where this problem is coming from.

I have a few Windows 10 desktop machines.  All connect to an unRAID server where I save all my files.  I also have an older Windows machine where I back up all of the data from the unRAID server to that older Windows machine.

On one of the Windows 10 machines I can open various files from the unRAID server but when I save those files the "last access timestamp" is set to the "max date" (https://en.wikipedia.org/wiki/Year_2038_problem).  See the attached file.  This causes problems with the synchronization program that I use.  If I copy the file from unRAID to this Windows 10 machine and edit it there then the "last access timestamp" is set correctly.  I can copy the file back to unRAID where my synchronization program will pick it up.

On my other two Windows 10 machines if I open the same files and save them the "last access timestamp" is set correctly.  So for some reason one of the Windows 10 machines is "weird".

All three Windows 10 machines have the exact same version of Windows (19042.1288) and all three Windows 10 machines have the "last access" turned on (system managed).

C:\Users\Tim>fsutil behavior query disablelastaccess
DisableLastAccess = 2  (System Managed, Disabled)

Is it possible that this is some lingering problem from the Linux 2038 fix in version 5.10 (https://linux.slashdot.org/story/20/10/17/2237236/linux-510-solves-the-year-2038-problem-until-2486) or is there something wrong with this one "weird" Windows machine?  There's even a program out there to manually fix this timestamp problem (https://backupchain.com/i/file-date-repair-tool-v1-0-fixes-broken-invalid-time-stamps).  The fact that this program exists proves that I'm not the only person to have this problem and yet if you search Google you don't find very much info about it.  I'm stumped.

Thanks,

Tim.