I should perhaps keep away from this, since I can't give you instructions for how to actually perform the necessary 'fix' (it's a looong time since I used that OS, or indeed even dual-booted with any form of Windows).....but I can tell you why it's happening.
It's all to do with the difference in the way that Windows and Linux, respectively, handle the 'time zone' thing. Linux systems synchronize with GMT; Windows, instead, likes to synchronize with what it calls 'local' time.....which, depending on where in the world you are, can of course be a long way off GMT.
As I understand it, there's two ways around this. You can either perform a Windows registry 'hack' to force it to use GMT instead.....or (which is probably miles easier), just tell Linux to use 'local' time instead.
Now all you need to do is wait for those with more knowledge of the 'nuts'n'bolts' than me to offer their advice as to how you actually do this. Since I run Linux exclusively, I don't, personally, have this problem.
EDIT:- Al obviously posted at the same time as me. He'll put you right.
Edited by Mike_Walsh, 08 March 2017 - 06:44 AM.
Distros:- Multiple 'Puppies'..... and Anti-X 16.1
My Puppy BLOG ~~~ My Puppy PACKAGES
Compaq Presario SR1916UK; Athlon64 X2 3800+, 3 GB RAM, WD 500GB Caviar 'Blue', 32GB Kingspec PATA SSD, 3 TB Seagate 'Expansion' external HDD, ATI Radeon Xpress 200 graphics, Dell 15.1" pNp monitor (1024 x 768), TP-Link PCI-e USB 3.0 card, Logitech c920 HD Pro webcam, self-powered 7-port USB 2.0 hub
Dell Inspiron 1100; 2.6 GHz 400FSB P4, 1.5 GB RAM, 64GB KingSpec IDE SSD, Intel 'Extreme' graphics, 1 TB Seagate 'Expansion' external HDD, M$ HD-3000 'Lifecam'.