This NUC is running a basic install of Windows 10 IoT Enterprise LTSC 2021, with Microsoft Store functionality restored to allow install of UWP apps. This morning I applied my usual post-install registry tweaks to Windows on this NUC. One of those tweaks instructs Windows to allow the hardware Real-Time Clock to remain set to UTC:
Code: Select all
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=hex(b):01,00,00,00,00,00,00,00
So far I haven't run into any issues with any apps that I run in Windows on my own PC with this tweak enabled. However, I noticed this morning after applying this setting on the Intel NUC running HDHomeRun RECORD, that today's HDHomeRun log file is apparently affected by this change:
- Leading timestamps in the log file entries were initally rolled back by eight hours following the post-tweak reboot
- "System: server time = " entries started showing "(correction of 28800s)" or thereabouts (i.e. 8 hours)
- Timestamps around that initial "correction" entry of approx. 8 hours were reverted to what they were prior to applying the tweak
Some questions:
1. What exact method does HDHomeRun use on Windows use to query "server time"?
2. If using the RTC, should that be changed to instead query Win32tm or something similar?
3. Where does "current time" get stored after it's corrected?
Thanks in advance for your replies. In the meantime I will remove this registry tweak from the DVR. It's not needed there anyway since that hardware will be dedicated to DVR service and will not be dual-bootable for the foreseeable future.