• 0

Time keeps changing by itself on Windows 7


Question

I'm dual booting Lion and Windows 7 and lately every time i'm using Windows the time changes 9 hours fwd.

I'm not talking about restarts between Windows and Lion . The clock in Lion stays the same all the time but in windows i can set the time to 4:00 and after a few min the time will change it self to 13:00.

First i thought i need a CMOS change but if the time keep staying set on ubuntu i don't think that's the problem.

I've cancelled time sync with microsoft servers etc' but the problem remains.

And Ideas?

18 answers to this question

Recommended Posts

  • 0

Thanks for the comment.

^ I know about that little tweak, that's not the problem I'm facing (and fixed that issue a long time ago). While i'm on Windows i see the clock changes 9 hours ahead. Not after a restart between OS.

Wakers, are you dual booting with another OS?

  • 0

Add the RealTimeIsUniversal key to the registry, restart immediately, then set the clock either in the BIOS or OS X and it should stick.

Did that, I don't think that's the problem. I'm using an hackintosh for 3 years now and added that registry key around that so long time ago.

That tweak is fixing the time differences when you move from Windows to Lion etc', my problem is that the time changes while i'm in windows. I change it to 10:00, the computer changes it to 19:00. That can happen 3 times in 10 min with no restart.

Do you have some wacky daylight savings time patch installed? Or maybe your computer is trying to tell you that it's time to upgrade to Windows 8.

Every daylight \ sync \ time related thingy is disabled. I think i'm gonna wait with Windows 8 for now :)

  • 0

What is your BIOS time? Is it UTC?

What is the output of your time zone settings in windows 7?

C:\Windows\system32>w32tm /tz

Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: 360min (UTC=LocalTime+Bias)

[standard Name:"Central Standard Time" Bias:0min Date:(M:11 D:1 DoW:0)]

[Daylight Name:"Central Daylight Time" Bias:-60min Date:(M:3 D:2 DoW:0)]

Are you a member of a domain? Domain members will sync with domain timesource. Good ref for windows time stuff

http://technet.microsoft.com/en-us/library/cc773263%28v=ws.10%29.aspx

I just run actual ntp client and turn off the built in sync service. There are ports actual ntp client for windows. But if your changing by 9 hours you have something wrong with timezone.

  • 0
On 10/28/2012 at 10:19 AM, BudMan said:

What is your BIOS time? Is it UTC?

What is the output of your time zone settings in windows 7?

C:\Windows\system32>w32tm /tz

Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: 360min (UTC=LocalTime+Bias)

[standard Name:"Central Standard Time" Bias:0min Date:(M:11 D:1 DoW:0)]

[Daylight Name:"Central Daylight Time" Bias:-60min Date:(M:3 D:2 DoW:0)]

Are you a member of a domain? Domain members will sync with domain timesource. Good ref for windows time stuff

http://technet.micro...v=ws.10%29.aspx

I just run actual ntp client and turn off the built in sync service. There are ports actual ntp client for windows. But if your changing by 9 hours you have something wrong with timezone.

It's UTC... I think?

C:\Users\Userid>w32tm /tz

Time zone: Current:TIME_ZONE_ID_UNKNOWN Bias: -120min (UTC=LocalTime+Bias)

[standard Name:"Jerusalem Standard Time" Bias:0min Date:(unspecified)]

[Daylight Name:"Jerusalem Standard Time" Bias:0min Date:(unspecified)]

I'm not a member of a domain (Our computers at work change the time according to the server, that's not the case.)

  • 0

For my part, the time in BIOS is correct. It's just Windows that gets it wrong. I'm not part of a domain either. This behaviour only started happening pretty much immediately after installing Windows 8. The clock will reset itself when the display is turned off after it's been idle. As soon as I wake it up, the time seems to be equal to whatever time it was the computer went into sleep.

I can resolve the issue by going into the clock and forcing it to sync the time again, however this often takes a couple of attempts as the operation will time out.

  • 0

"Time zone: Current:TIME_ZONE_ID_UNKNOWN"

Well clearly that is NOT right.. So yeah you could be having some issues to be sure.

Fix your current timezone - you got something wrong.

I changed mine to Jerusalem and get this.

C:\Windows\system32>w32tm /tz

Time zone: Current:TIME_ZONE_ID_STANDARD Bias: -120min (UTC=LocalTime+Bias)

[standard Name:"Jerusalem Standard Time" Bias:0min Date:(M:9 D:4 DoW:0)]

[Daylight Name:"Jerusalem Daylight Time" Bias:-60min Date:(M:3 D:5 DoW:5)]

And I would verify what your bios is set to.. If its UTC you should know, not think so.

  • 0

Microsoft Windows [Version 6.2.9200]

© 2012 Microsoft Corporation. All rights reserved.

C:\Users\Ian>C:\Windows\system32\w32tm /tz

Time zone: Current:TIME_ZONE_ID_STANDARD Bias: -60min (UTC=LocalTime+Bias)

[standard Name:"Central Europe Standard Time" Bias:0min Date:(M:10 D:5 DoW:0)]

[Daylight Name:"Central Europe Summer Time" Bias:-60min Date:(M:3 D:5 DoW:0)]

C:\Users\Ian>

Can someone help me out here? When I turned my PC on at 0907 this morning, Windows said the time was 0038 (which is probably the time that I turned the PC off). I've noticed that if I have an application running in full screen on the monitor where the clock is, the clock will not update either.

The time is correct in the BIOS and it's a new motherboard (less than 2 months old).

  • 0

Are you actually turning it OFF, or putting it into standby/hibernate?

Clock not updating is not related to the OP issue at all -- I would suggest you start your own thread vs confusing this one with your non related issue.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Louis Rossmann suing Samsung over "990 Pro SSD warranty scam" by Sayan Sen Back in 2023, if you recall, Neowin reviewer Robbie Khan had a dispute with Samsung over his 990 Pro SSD, which was rapidly losing its health. After significant back and forth, the tech giant had finally released firmware to "stop" the issue. Interestingly, its previous flagship at the time, the 980 Pro was also facing problems leading to two consecutive sets of firmware fixes. Three years later, it looks like a similar conflict has now broken out between tech repair entrepreneur YouTuber Louis Rossmann and Samsung, as it has escalated into a threatened lawsuit after the company allegedly refused to appropriately replace a failing 990 Pro SSD that remained under warranty. According to Rossmann, a 4TB Samsung 990 Pro NVMe SSD purchased for approximately $330 less than two years ago, began experiencing major hiccups and issues, even though he claims it had been operated under ideal cooling conditions. It was installed in a RAID 1 array and cooled by a heatsink and dual high-speed fans. However the drive reportedly started dropping out of the array, exhibiting controller-level failures that eventually became not useable in any meaningful way. Rossmann said Samsung’s support process was marked by delays and confusion from the very start. After initially contacting the wrong regional support channel, he was redirected to Samsung’s memory support division where he submitted detailed diagnostics, logs, and proof of purchase. Rossmann runs a repair company and owns an ACE Lab PC-3000 machine, which is a professional-grade data recovery equipment. As such, he had been confident in his diagnostics. Samsung even seemingly acknowledged that later. Regardless, Rossmann claims that his initial support ticket was automatically closed before a full 24-hour response window had elapsed, forcing him to reopen the case and resubmit documentation. The controversy however intensified further from here after Samsung accepted the drive for warranty evaluation but later returned it with a repair report stating that the drive had passed its testing and that the SSD had been verified as functional. Rossmann strongly disputed those claims citing that his own independent testing on PC-3000 showed write speeds reducing to as low as 40–60 MB/s before the drive failed entirely. Samsung subsequently informed him that the SSD had been reset and reflashed, passing internal stress tests. However, the company also stated that replacement units were unavailable due to an industry-wide memory shortage and suggested that a refund process could be initiated if further testing confirmed the fault. Thus, to settle, the company offered a refund of $330, the amount that was initially paid by him to make the purchase. Here, Rossmann pointed out the seeming hypocrisy of the tech giant as in how no Samsung drive was apparently allocated for warranty replacements, but they were abundantly available for retail sales especially when using business accounts. As you can see, Rossmann is indeed right, there are Samsung 990 Pro 4TB SSDs on Amazon currently for $950 (shipped and sold by first-party Amazon US itself), and they are also available on Samsung's own store too, albeit for an even higher price of $1100. Thus Rossmann argues that Samsung’s inability or unwillingness to provide a replacement while the same model remains available for purchase at significantly higher market prices reflects a failure to honor its warranty obligations. He has issued a formal 60-day notice and says he intends to file suit in Texas small claims court, asserting that companies should face greater costs for denying legitimate warranty claims than for fulfilling them. You can check out the full video titled "Samsung's 990 Pro SSD warranty policy is a scam; I'm taking them to court," at the link below. Source and image: Louis Rossmann (YouTube) As an Amazon Associate we earn from qualifying purchases
    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!