It will create a new entry in the Windows registry that will make the operationg system store the time in UTC.Īfter you execute the command, you need to reboot and set the clock to the correct time. Windows 64 Bits Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_QWORD /d 1 This means setting the clock to something other that UTC time will cause 'local time' to be wrong. All adult OSes expect that the RTC will be in UTC, and then the OS calculates the corrects time to display for users based on the time zone and daylight savings time. UTC - World Clock - Single display shows UTC or local 12 hr or 24 hr time. Meeting - links to the World Clock Meeting Planner: Find out the best meeting times between the selected city and other locations. The selected city will be entered as default location where applicable. To change the setting on Windows, open the Command Prompt or Windows Terminal with Admin privileges and execute the command below: Windows 32 Bits Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_DWORD /d 1 The problem stems from a registry hack that allows Windows 7 to use UTC in the CMOS real-time clock (RTC). Click or tap on one of the icons under the clock to use one of the handy tools on. The preferred method to solve the issue is to set Windows to store the time in UTC instead of forcing the other OS to store the time in local time. ![]() If you are dual-booting Windows 10 or 11 and Linux or another operating system that uses UTC to store the system time, you notice that the time is wrong when switching the operating systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |