Time differences of one hour are quite common problems. Here’s some ideas:
A difference due to timezones
A timezone difference is between the UTC time used by Windows 10 internally and local time used by Windows Explorer for example.
You can display the time in both Powershell) and the Windows command line. Are they both the same, give or take the time between executing both commands? In this example, they are the same but just displayed with a different format:
Here’s how Powershell can display either UTC and local time.
PS C:\WINDOWS\system32> get-date
Wednesday, 4 December 2019 3:31:56 PM
PS C:\WINDOWS\system32> Get-Date -UFormat "%A %B/%d/%Y %T %Z"
>> $Time = Get-Date
Wednesday December/04/2019 14:49:41 +13
Wednesday, 4 December 2019 1:49:41 AM
Here’s how the Windows command line displays it
The current time is: 13:49:48.50
Enter the new time:
A difference due to the timestamp source used
File timestamps depend upon the file system on the storage partition so that can cause differences:
- NTFS uses UTC
- FAT uses local time
A difference due to daylight saving
This is much less common now. At least since Windows 7.
Timeserver sync issue
In Windows settings, change the time server that you arr syncing to. Or add one if you haven’t already.