Windows use utc

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Ask Question. Asked 9 years ago. Active 5 years, 6 months ago. Viewed 23k times. Community Bot 1. Franco Pini Franco Pini 83 1 1 gold badge 1 1 silver badge 3 3 bronze badges. What version of Windows? This question is asking for help reversing changes explained in a procedure documented in an Ask Ubuntu answer and in the Ubuntu community wiki.

Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. More from the IDG Network. How to identify, prevent and remove rootkits in Windows Best new Windows 10 security features: Improvements to Intune, Windows Right on Time? Ryan McGuire CC0. What is UTC and why is it important to security? Context: We are having limit, off-by-one style errors, and I thought 'aha: move all the things to UTC' but then realised that I am just going through the code converting a bunch of DateTime objects to use a UTC timezone, and this struck me as a waste of time.

Your use case allows storing a local time with an offset. IMO there is no need to store in UTC, as you can always translate the point in time into any other local time. In fact it gives you even more, as you have additionally the information about the local time.

Technically there is an advantage in storing the date as UTC and the offset separately: You can sort on a string, which gives you an advantage in e. DBS which don't support date fields with offsets properly e. If you consider systems which don't allow storing an offset, the actors will have to agree on a common timezone. UTC seems to be a very stable candidate with good timezone translation support. One example for this is Exif where you can only store a local date without any timezone information.

Another example is the hardware clock in a multi OS computer. First, is that with global users of some of the applications I work on, local time varies per user, so local time for a user that entered the data may not be local time for a user viewing the data later. Second, timezones change. They are subject to the whims of governments. You can always figure out the correct local time, but I just view it as more work than just converting UTC to local.

The point is you must always store DateTime either in UTC or with in offset, but never store DateTime "local centric", or without the offset. In other words:. For instance, this could happens if you don't really care of time zone and at the end the previous time could happen to be stored as:. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Why does this happen? Your computer stores the time in the hardware clock on the motherboard. Even if the computer is turned off, the clock will record the time.

By default, Windows assumes that the time is stored in local time, while Linux assumes that the time is stored in UTC and applies an offset. This can cause one of your operating systems to display the wrong time in a dual-boot situation.

Do not follow the two options described below, otherwise, they will not speak the same language! If possible, we recommend that you let Linux use local time.

Letting Linux use local time like Windows is probably the best option.