Solved Incorrect time solution

[tech291083]

Hi,

I have often come across this issue of Windows 7/8/10 not showing the correct time despite all the right settings in place. Under those circumstances, I had no other option, but to replace the CMOS battery. But is it possible for Windows 7/8/10 to show the correct time for a period of one year or more, if the computer is never ever connected to the Internet or any other network (after the installation of Windows 7/8/10), which could possibly provide time via some sort of synchronization/Internet time server?

Is setting the time in BIOS after installation enough for Windows 7/8/10 to show the correct time without ever connected to the Internet ?

Thanks.

 

[Alejandro85]

The time Windows shows actually comes from the BIOS (the real-time clock) and is the BIOS who is responsible for keeping it in time, while the OS just limits to show it.

If the CMOS battery is dead there is nothing you can do, the time will reset itself to a "default" point, pretty much at every reboot. With a full battery however, setting it once (be it in BIOS or in Windows, it's the same) should keep it correct for quite a while.

Corrections from an authoritative NTP server are often necesary because, in real life, clocks aren't that stable as they should, specially the relatively simple computer clocks. CMOS batteries deplete over time, not all clocks run at the same speed and they can lag/go behind the official time and may require corrections from time to time, either manual or automated.

If the problem shows up abruptly it's often sign of a faulty battery and replacing it should fix it. But if it desyncs slowly over time, then an adjustment is necesary, because.... well.... high precision timing is not the desing goal of computers

 

[tech291083]

The time Windows shows actually comes from the BIOS (the real-time clock) and is the BIOS who is responsible for keeping it in time, while the OS just limits to show it.
Very nice explanation indeed. I thought that CMOS battery would never show the correct time, no matter how good its condition was. Now, I am thinking of doing a little experiment by buying a good brand new CMOS battery, setting it to the local time and then installing Windows 7 to the HDD and finally I will not connect to the Internet for at least a month or more, no matter what, but I will use the PC. This will help me understand how long a CMOS battery can show the correct local time without actually taking any help from any time server. I am not sure what is going to happen, but at least I will have some peace of mind and something new to learn. Thanks a lot again.
If the CMOS battery is dead there is nothing you can do, the time will reset itself to a "default" point, pretty much at every reboot. With a full battery however, setting it once (be it in BIOS or in Windows, it's the same) should keep it correct for quite a while.

Corrections from an authoritative NTP server are often necesary because, in real life, clocks aren't that stable as they should, specially the relatively simple computer clocks. CMOS batteries deplete over time, not all clocks run at the same speed and they can lag/go behind the official time and may require corrections from time to time, either manual or automated.

If the problem shows up abruptly it's often sign of a faulty battery and replacing it should fix it. But if it desyncs slowly over time, then an adjustment is necesary, because.... well.... high precision timing is not the desing goal of computers

Very nice explanation indeed. I thought that CMOS battery would never show the correct time, no matter how good its condition was. Now, I am thinking of doing a little experiment by buying a good brand new CMOS battery, setting it to the local time and then installing Windows 7 to the HDD and finally I will not connect to the Internet for at least a month or more, no matter what, but I will use the PC. This will help me understand how long a CMOS battery can show the correct local time without actually taking any help from any time server. I am not sure what is going to happen, but at least I will have some peace of mind and something new to learn. Thanks a lot again.

 

[file3456]

Dorkify it via GPS!

The decoded Morse code is: 73 73 DE KF7SEY SK E E

73 is amateur (ham radio) speak for "regards." DE means "this is." so DE KF7SEY. SK means end of message in Morse code or Silent Key, meaning a person that is no longer alive. the E E is explained here: CW: when I supposed to send "E E"? - Amateur Radio Stack Exchange


Anyway...

.-.. --- .-..


Amazon.com

 

[TechnoMage2016]

Worse than the RTC being out of sorts from a low CMOS battery, the entire motherboard may just decide to roll over and play dead! Over the years, I've been given several PC's, where I was told, "It's DEAD!". Once I'd get it home and do a little examination, I'd find that the only thing DEAD was that little CMOS battery. Once I'd put in a new battery, and set the date and time, etc. the PC would boot up and run like New!

My spec on whether a battery is good or not is....If it measures 3.0 vdc or better, on my Digital Volt Meter, it's good, but if it's anywhere Below 3.0 vdc it's on its way Down and should be replaced with a new one. Those CR2032 batteries are so cheap these days, it's not worth messing around with one that's not showing a full charge.*

* For years, when I was running my own Computer Shop, every PC that came in, that I had not seen before, got a New CMOS Battery. Better SAFE than Sorry! Eh?

Happy Holidays, Mates!
TM

 

[Barman58]

I believe that most of the modern UEFI BIOS's ( or at least those in High Spec Motherboards ), have a two way connection with the OS so can now keep the time synchronised from the time checks performed by the OS. These BIOS's also have the ability to change some BIOS settings from within the OS, rather than requiring to reboot into the BIOS for every change

 

[file3456]

That makes sense given what UEFI is all about.

It is why I don't particularly care for UEFI in terms of security. That whole interface between the OS and the motherboard worries me. Okay, bad choice of words.. LOL You know what I mean. It's like the motherboard has it's very own API in a layer 3 & 7 of the OSI with the OS. I feel the two should be segregated in some secure fashion. And perhaps it is. I just haven't read enough about the wonders of UEFI.

Just for the heck of it, I did a search for "UEFI" for CVEs and they're out there. CVE -
Search Results

In contrast, here's the search term "BIOS'. CVE -
Search Results

Of course both search terms "UEFI" and "BIOS" are ubiquitous so it kinda makes it hard to narrow down the old BIOS CVEs unless you look at each CVE and what they are for, or look before 2007 when UEFI wasn't used. And for that, there are only four listed at the mitre.org website. There could be more.