Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

my computer is on a domain with about 30 other computers and mine is the only one that hasnt rolled forward to daylight savings time. i have rebooted and all that.

Does anyone have any suggestions? Its a Windows XP machine.

share|improve this question

OK, as ChrisF pointed out in the comments, half of the world (the southern half) is approaching summer, so let me apologize for the northern-hemisphere-centric focus of my original post. It's been a few decades since I was south of the equator; I'll blame my northern bias on that. :)

The point I was trying to get across is that there are differing rules for when DST is applied or removed. There's the official rule, defined by your local government, and that changes once in a while. Then there's the rule that Windows computers follow, which is hopefully a programming representation of the official rule, and which is typically rolled out by Windows Updates.

In general, if your area has already made the switch (whether to or from DST), and your computer doesn't match everyone else's, there are a couple of reasons this could be happening. We have two sets of computers (yours, and all the rest); one set is right, one is wrong. Why?

  1. One set of computers isn't running the Windows Time service,

  2. One set of computers hasn't applied the latest DST update, or

  3. One set is getting its time from a different server (which is giving the wrong time).

Assuming the solitary computer is the wrong one, you should

  • a) make sure the Windows Time service is running,
  • a) check for any Windows Updates you haven't applied, and
  • b) verify that your NTP settings are the same as the other computers

If that doesn't fix it, please update the question with what you've done so far. We will need to look deeper at how Windows sets its time, particularly in a Domain setting, and tools to help troubleshoot.


W32Time is the Windows Time service that provides Windows computers with timekeeping as well as their timezone and DST smarts. The w32tm and net time commands will be helpful; read the link for gory details.

On a Domain, Group Policy comes into play, so problems might actually be with the local Windows Time Service Group Policy.

Remember: Time is complicated. Windows Time doubly so.

share|improve this answer
Grant could be in the southern hemisphere, of course. – ChrisF Oct 6 '09 at 21:37
true. doesn't really change the diagnosis much; you'll boil down to the same possibilities. – quack quixote Oct 6 '09 at 23:45

I know it's obvious, but have you checked that the option to automatically adjust the clock is enabled?

It's on the Time Zone tab of the Date and Time properties dialog.

Another obvious thing to check is that the year on the problem computer is correct. If the start of daylight saving has changed recently and the computer is set to 2007 (for example) it might not be daylight saving yet.

Is there a process running on the affected machine (like Atomic Clock Sync) that's overriding the time?

The key is to look for differences between the machines that work and the one that doesn't.

share|improve this answer
ya have checked and its the same as all the other computers on the network. – Grant Oct 6 '09 at 10:10
just double checked and the date is definetley correct. – Grant Oct 6 '09 at 10:17
hmm no software like that either.... – Grant Oct 6 '09 at 12:23
@Grant - sorry, I'm out of ideas now. – ChrisF Oct 6 '09 at 21:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.