The "Programmer v4.8.0" from "nRF Connect for Desktop v5.4.0" does not appear to use the Windows system time correctly, and this problem has appeared for us with the new UTC-7 "Pacific Time" time zone. (This is not the old UTC-8 "Pacific Standard Time" -- it is a new time zone first used November 1, 2026.) The Canadian province of British Columbia is (so far) the only area within this time zone, and so Windows currently shows this time zone as "Pacific Time (British Columbia)".
On two machines set to the new "Pacific Time (British Columbia)" and running Programmer v4.8.0, the log timestamps and the file modification times are one hour behind. Oddly, Programmer is the only application that I've seen that has had a problem with the time zone having been changed.
For example, the screenshots below show what the Windows File Explorer sees as the file's timestamp, as well as what Programmer v4.8.0 shows.
Windows File Explorer:
Programmer v4.8.0
While one can adjust and expect Programmer to be showing incorrect times, it would be nice if it did not. 
Thanks
