win10 restting clock using boot options

[cretsiah]

So i have noticed win10 for some unkmown reason decides to alter time settings backwards of about 15-18hrs on avg if i use the F12 boot options.

 

im not even trying to dual boot as such, just use a live usb stick its getting rediculous that i have to keep resetting the time in windows 10 just because i wanted to have a look at a live usb stick for an hr or 2.

 

no we havent installed anything just running live...

 

 

anyone got any ideas about how to fix this?

it can/ could create serious issues for time stamped file verification...

 

im only using win10 because of one lousy game i cant get right on linux, all the others i wanted are fine

 

[G3R489]

Just thinking about it, if you have an older computer it could be time to change the CMOS battery, usually if you have a pin battery that says CR2032 it’ll last about 10 years, but if it says CR2016 it’ll only last about 4.

 

If not there is other options, like manually setting your computer to read from an ‘internet time sever’, this is an easy cheat way to do it, but it requires an internet connection.
 

If not it could just be that ‘Windows time services’ are a bit out of whack, so it might be worth a quick check in your services.msc file, also check startup type is automatic.

 

If it’s none of those, I’d check with an antivirus that nothings playing with your system.

 

just a few recommendations, hope that helps

[G3R489]

Also sorry, have to add this as forgot to notify of reply’s on my last message. 

[cretsiah]

ill have to check the bios/cmos clock date.... but pretty sure that has been right the whole time, ( although that doesnt mean that battery hasnt had it)

 

it doesnt seem to matter at this stage if i choose internet based clock or internal (cmos/bios clock) for time setting it still does it either way.

 

I was aware of this happening for dual booting systems although i cant remember why,

 

but now at least for me it seems to have an effect even on if a live distro is used.

[G3R489]

2 minutes ago, cretsiah said:

ill have to check the bios/cmos clock date.... but pretty sure that has been right the whole time, ( although that doesnt mean that battery hasnt had it)

 

it doesnt seem to matter at this stage if i choose internet based clock or internal (cmos/bios clock) for time setting it still does it either way.

 

I was aware of this happening for dual booting systems although i cant remember why,

 

but now at least for me it seems to have an effect even on if a live distro is used.

Yeah, give that a check as I find that issue with allot of older systems.
 

And alright, other than VM’s don’t use multi OS so if that’s the case, I’m afraid it’s a problem for google or someone else on here.

However like I said if that’s gone weird and your clock settings are automatic and correct, check the services.msc, and go into the ‘Windows Time’ properties and check that all looks okay, as sometimes that can be stopped for random reasons.

[cretsiah]

so just checked bios clock yep it says everything right....

 

system reboot time is perfectly fine........

 

it is only when you try to boot from another device (aka HHD, SSD, USB) then go back to windows,  that it throws a time hissy fit

 

 

Quote

check the services.msc, and go into the ‘Windows Time’ properties and check that all looks okay, as sometimes that can be stopped for random reasons.

yep well that might be causing it....

 

" Auto Timezone Updater " was disabled

 

I'll see what happens this time

[G3R489]

9 minutes ago, cretsiah said:

so just checked bios clock yep it says everything right....

 

system reboot time is perfectly fine........

 

it is only when you try to boot from another device (aka HHD, SSD, USB) then go back to windows,  that it throws a time hissy fit

 

 

yep well that might be causing it....

 

" Auto Timezone Updater " was disabled

 

I'll see what happens this time

Okay hopefully that helps sort it out, if not keep me updated

[cretsiah]

nope didnt help at all

 

and im not the only one that has this stupid issue, some only have an hour difference mine avergages at 12hrs ( ie if 8pm it will say 8am)

what has got me is it only does if you try to boot something else not if your just rebooting windows 10...

 

it suggests windows 10 is doing a lot (or maybe not enough)  behind the scenes without your consent to have such a stupid issue, dont think i have ever seen  it occur in win98 -win7 and i usually had them set to the local system.

 

 

im so over the little inconveniences of win10 that i am actively looking for a decent replacement, have beeen messing with linux mint for a few weeks, might give POPOS! i try or even manjero, artix, calculate, mx. 

[G3R489]

5 hours ago, cretsiah said:

nope didnt help at all

 

and im not the only one that has this stupid issue, some only have an hour difference mine avergages at 12hrs ( ie if 8pm it will say 8am)

what has got me is it only does if you try to boot something else not if your just rebooting windows 10...

 

it suggests windows 10 is doing a lot (or maybe not enough)  behind the scenes without your consent to have such a stupid issue, dont think i have ever seen  it occur in win98 -win7 and i usually had them set to the local system.

 

 

im so over the little inconveniences of win10 that i am actively looking for a decent replacement, have beeen messing with linux mint for a few weeks, might give POPOS! i try or even manjero, artix, calculate, mx. 

Oh well, worth a try.

 

Im afraid you’ve reached the end of my knowledge, so you’ll have to either see if anyone else comes along or look through google I’m afraid.

 

Sorry I couldn’t help more