Windows Time is constantly out of sync

I went ahead and contacted AOL, (sent an E-mail to AOLHelp) but to be honest, I don't think their support has been all that good since DSL became popular, and that they started offering free service. What was that, like around 2003?

JOSHSKORN said:

I went ahead and contacted AOL, (sent an E-mail to AOLHelp) but to be honest, I don't think their support has been all that good since DSL became popular, and that they started offering free service. What was that, like around 2003?

Yes. Unless you get their paid service (which they still offer) they will not provide phone support. I did get a response to my email about 2 weeks after I sent it but it was not helful except to the extent I knew they read they email.
So is your clock still in sync with 9.7?

poolmon said:

So is your clock still in sync with 9.7?

I just checked, it was about 2 1/2-3 minutes fast still with AOL 9.7, but much better than with AOL 9.8.
@Edward, would it work if I tried replacing the Windows Time server entry with the time server used in NetTime?

JOSHSKORN said:

I just checked, it was about 2 1/2-3 minutes fast still with AOL 9.7, but much better than with AOL 9.8.
@Edward, would it work if I tried replacing the Windows Time server entry with the time server used in NetTime?

I doubt changing the setting will help, but it seems like you have nothing to lose by trying it. I noticed with 9.8 I had the biggest time fluctuation when I left AOL Desktop open all day. If I closed it when not using AOL the fluctuation was substantially reduced.

poolmon said:

I doubt changing the setting will help, but it seems like you have nothing to lose by trying it. I noticed with 9.8 I had the biggest time fluctuation when I left AOL Desktop open all day. If I closed it when not using AOL the fluctuation was substantially reduced.

Is there a way to prevent AOL Desktop from modifying the system time via Local Security Policy? If so, would that fix anything?

JOSHSKORN said:

Is there a way to prevent AOL Desktop from modifying the system time via Local Security Policy? If so, would that fix anything?

That's above my pay grade. I'll have to the response over to someone more in the know.

TairikuOkami said:

Change time server to time.nist.gov, windows one fails too often.

Yeah this does seem to solve the problem... kinda weird how I'd never had issues with the default one til I switched to a new am3+ board
and it decided gmt+12 should be at the gmt+7 time ...

Hi

Sorry to hijack this post. I also had the same problem. My clock seems to be out of sync. Or rather it does not sync as frequent as it should or something. It would sometimes be like 1 or 2 hrs behind...which i presume that was it last sync time then I think it got interrupted or something and hence the clock is like 1 or 2 hrs behind.

I am using time.nist.gov.

Previously I was using the windows.time. That was like a few minutes behind/or ahead. Even after i manually sync it, it still has that problem. So it should not be a syncing issue. More like the windows time server issue.

For time.nist.gov., I just though that the sync might be interrupted. Is there a way we can verify this? Oh is a new Asus laptop with windows 10 preinstalled.

thanks guys.

That's what you get from using this modern equipment. My clock always works - as long as there is sun. LOL

Use this server instead nist.gov.

Code:

pool.ntp.org