Clock issue that keeps resetting despite changing the CMOS battery
LucPALUMBO
-
gugu01 Posted messages 15669 Registration date Status Contributeur Last intervention -
gugu01 Posted messages 15669 Registration date Status Contributeur Last intervention -
Hello everyone!
I'm coming to this forum because I have a clock issue with my setup that I can't resolve.
My PC running Ms Win 10 Pro constantly has the time (and date) getting out of sync (sometimes by several days even!)
I replaced the CMOS battery on the motherboard thinking it would help, but the issue is the same.
I have time synchronization with an NTP time server, and the Windows Time service is set to automatic and started.
While browsing the Windows Event Viewer, I notice "info" messages regularly coming from the source "Time-Service" with the following details:
The VMICTimeProvider time provider has indicated that the current hardware and operating environment are not supported and have been shut down. This behavior is expected from VMICTimeProvider in non-HyperV guest environments. It may also be expected from the current provider in the operating environment used.
Could you please help me in my quest?
Thank you very much in advance because I’m starting to drive myself crazy with this problem.
Thanks.
Luc
I'm coming to this forum because I have a clock issue with my setup that I can't resolve.
My PC running Ms Win 10 Pro constantly has the time (and date) getting out of sync (sometimes by several days even!)
I replaced the CMOS battery on the motherboard thinking it would help, but the issue is the same.
I have time synchronization with an NTP time server, and the Windows Time service is set to automatic and started.
While browsing the Windows Event Viewer, I notice "info" messages regularly coming from the source "Time-Service" with the following details:
The VMICTimeProvider time provider has indicated that the current hardware and operating environment are not supported and have been shut down. This behavior is expected from VMICTimeProvider in non-HyperV guest environments. It may also be expected from the current provider in the operating environment used.
Could you please help me in my quest?
Thank you very much in advance because I’m starting to drive myself crazy with this problem.
Thanks.
Luc
However, I find it a bit "harsh" to replace the CM directly without looking further. Don't you think?
Would you have an explanation for the message I'm seeing in the event manager?
Thank you in advance.
Best regards.
Luc