Win 10 and the Year 3000

[Michael]

Hello all,

 

I've had this happen twice now -

 

- Two completely different notebooks, although they were/are both Toshiba's - moderate in age

- Different Domains/Networks

- Different but very similar Windows 10 Images

- Windows 10 Edu, build 10240 up-to-date

- Time Server implemented on DC, talking to a real Time Server externally

 

Randomly the month is correct, March, but the Year was/is 3000+

 

Obviously this means the computer can't logon, as it's well out of the 5 minute limit difference between it and the DC. Interestingly the DC doesn't seem to be over-riding the time when it should, as with 99% of other devices (which is the whole point).

 

The only conclusion I can come to were both notebooks were low/flat on power, yet that's obviously what the watch battery is for - unless it's just a pure coincidence? I can't think of any other explanation.

 

The only workaround is to change it in the BIOS, then logon locally, as it changes again. It's just really strange behaviour. Any ideas would be welcome