Help: Windows 7 System Clock is Running Fast
Written by Alan Friday, 2 September 2011 07:00
Many users may not have experienced it, but there is a bug which causes the Windows 7 system clock to gain time at a pretty quick pace. It’s seems to only effect the 64-bit edition, but if you have had this problem in the 32-bit version then let us know in the comments below. The problem should have been fixed long ago, but it continues to persist. Just the other day, I purchased a new laptop with Windows 7 64-bit and had it happen – and this came with SP1 installed!
If you have this happen on your new PC then you will know it pretty quickly – my system clock gained almost 12 hours in the first 24 hours I owned it. You can, of course, reset the clock, but it will just gain the time back. You will actually need to reset the clock, but that comes later.
As always, Microsoft has a “fix”, which is really just a work-around. I am not even sure it’s an official work-around, but it did come from a forum moderator on the Microsoft Answers website. It’s actually pretty easy to handle, even for novices.
Click Start => All Programs => Accessories => Right click Command Prompt => Run as Administrator.
Run the following command:
net stop w32time
net start w32time
Restart your computer, then reopen the Command Prompt, again as an administrator.
Now follow these instructions:
1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command
Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the
password, or click Allow.
2. Type the following command, and then press ENTER:
The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
If you have any out-of-date files then allow them to be fixed, restart the computer again, and run the System File Checker one more time to make sure everything is up to date.
You may still need to adjust your system clock manually (I did, but not everyone has to). Once this process is done you should have no more problems with a fast-running system clock. Mine has not gained one second since.