It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Elmofongo: I'm surprised we aren't called little Mexico ;)
avatar
zeogold: I considered that, but when was the last time you saw Mexico annex anything?
Now, Texas, on the other hand...
What do you mean?! Mexico annexed Los Angeles.
avatar
zeogold: Well, I wasn't supposed to tell you this, but...
I'm afraid Puerto Rico's been annexed. You are now Little Texas.
avatar
Elmofongo: I'm surprised we aren't called little Mexico ;)

Anyway the problem is persisting but the Manage to find the correct time zone, at least I got that fixed, but the issues where it goes back 1 hour and staying stuck at the same time after I shut down the PC is still here.
I'm not sure I am understanding you correctly. Are you saying that when you start the computer, it still says the same time as when you last shut it off?

If that's the case, the problem is likely that the CMOS battery on the motherboard is dead. I don't know how old your machine is, but that battery usually lasts about five years, if your machine is about that old or more, you should probably replace it (it's likely a CR2032 battery).
avatar
Elmofongo: I'm surprised we aren't called little Mexico ;)

Anyway the problem is persisting but the Manage to find the correct time zone, at least I got that fixed, but the issues where it goes back 1 hour and staying stuck at the same time after I shut down the PC is still here.
avatar
Maighstir: I'm not sure I am understanding you correctly. Are you saying that when you start the computer, it still says the same time as when you last shut it off?

If that's the case, the problem is likely that the CMOS battery on the motherboard is dead. I don't know how old your machine is, but that battery usually lasts about five years, if your machine is about that old or more, you should probably replace it (it's likely a CR2032 battery).
I think I had this PC since 2013.
If I'm understanding the issue correctly, I have to agree with Maighstir. This is almost always a CMOS battery issue whenever I've heard of something like this. SO I'd change that as a first step.
Did it start to happen recently? Because I remember seeing some reports of DST issues after the recent Windows updates. And the latest non-security batch (as in the "preview" for what will be incorporated in the single November batch) claims to solve some DST issues (but also shoves more telemetry down the throats of those installing it I gather).

If the difference is exactly one hour, must be a DST issue, can't be a battery problem. A battery problem would reset it to a default value probably.

Something that happened to me was having it run consistently slow, on my old computer. Usually 10 seconds per hour, so four minutes per day. Windows learned to update time daily instead of weekly, and kept using it like that, and used it for 7 years without it getting worse or other related symptoms. Also used it for another couple of weeks recently, after it spent close to a year and a half just sitting in a corner. And the time was perfectly right when I turned it back on, confirming what I had noticed before too, which was that the time loss happened only while running and in Windows. For those nearly 2 weeks I used Linux, and no time drift. (Also must say definitely didn't expect the BIOS battery to still hold at all, thought I'd find it having forgotten all BIOS stuff, so obviously including time, yet it didn't.)
Just tell Microsoft your not able to pay the correct regional/scam pricing for stuff and they will be falling over themselves to fix it quick smart! lol
low rated
And your stupid girlie help me threads is driving me cwazy.
Post edited October 24, 2016 by Tauto
Try to install one of those freeware that sync time with internet and see which one works for you.

I used something like this years ago when my bios battery dies
avatar
Cavalary: Did it start to happen recently? Because I remember seeing some reports of DST issues after the recent Windows updates. And the latest non-security batch (as in the "preview" for what will be incorporated in the single November batch) claims to solve some DST issues (but also shoves more telemetry down the throats of those installing it I gather).

If the difference is exactly one hour, must be a DST issue, can't be a battery problem. A battery problem would reset it to a default value probably.

Something that happened to me was having it run consistently slow, on my old computer. Usually 10 seconds per hour, so four minutes per day. Windows learned to update time daily instead of weekly, and kept using it like that, and used it for 7 years without it getting worse or other related symptoms. Also used it for another couple of weeks recently, after it spent close to a year and a half just sitting in a corner. And the time was perfectly right when I turned it back on, confirming what I had noticed before too, which was that the time loss happened only while running and in Windows. For those nearly 2 weeks I used Linux, and no time drift. (Also must say definitely didn't expect the BIOS battery to still hold at all, thought I'd find it having forgotten all BIOS stuff, so obviously including time, yet it didn't.)
I have not updated my PC in awhile.

Right now I have less than 500MB worth of Updates.