The following lines were added (+) and removed (-):
== DATE AND TIME WONT SYNCHRONIZE ==The Microsoft time server has been known to go down. Also, when your computer time is too far off, it will not synchronize.Issue #1: Forcing the time server to change and synchronize when it fails to do so though the GUI interface. Issue the following commands. The unregister command has to be issued twice. The first time it will return an error. Ignore the error and issue the command again. net stop w32time w32tm /unregister w32tm /unregister w32tm /register reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f net start w32timeYou have forced the time server to be changed from the Microsoft one to the the gov time server with the new value registered and service activated.Issue #2: Time and Date off by too much to synchronize. You will observe the following error: An error occurred while Windows was synchronizing with time.windows.com. For security reasons, Windows can not synchronize with the server because your date does not match. Please fix the date and try again.You have to manually set the time and date close, same day, and time close within minutes. This is prevented due to the belief that it will interfere with the operation of kerberos and possibly other applications sensitive to time and date, mostly though to prevent malicious software from changing your computer time and date without your awareness. Manually set it close, then let sync keep it accurate for you with regular sync operations.