The “Modified Time” file attribute of NTUSER.DAT changed
Last Updated March 12, 2019
The “Modified Time” file attribute of NTUSER.DAT changed after a Manual or Scheduled scan
You may find the “Modified Time” file attribute of NTUSER.DAT changed after a Manual or Scheduled scan but Symantec Endpoint Protection did not make the change. When Symantec Endpoint Protection scans the profile, it will load NTUSER.DAT to scan the user registry hive. Symantec Endpoint Protection does not modify NTUSER.DAT, it only loads and scan.
If you want to confirm that Symantec Endpoint Protection is not changing the Timestamp on NTUSER.DAT, use Procmon to record the processes. By examining the Procmon this will allow you to validate that Symantec Endpoint Protection is not making the change.
Examine the QueryBasicInformationFile and SetBasicInformationFile from the Procmon and you will see the Lastwrite and Changetime.
Example: instead of WRITEFILE look for querybasicinformationfile:
The following Microsoft article references Modified time on Windows 7 and 2008. It seems to be happening again in Windows 10.
The "Modified time" file attribute of a registry hive file is updated when an application loads and then unloads the registry hive file without making any changes on a computer that is running Windows Server 2008 R2 or Windows 7