![]() This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. We also checked that Windows 10 clients and they successfully connected to the domain time source, but the date time in the system is still wrong, even if manually resync it (w32tm.exe /resync /computer:domaintimeserver).įrom the System event logs, there are a lot of error info related to the Windows Time, and another strange thing is that we did not use Hyper-V VMs in Windows 10 client machines, but there're some Hyper-V services in the System services. We tried to manually set the correct date time in Control Panel, but after restarting the Windows Time service, the date time reverted back to wrong again. After restarting the computer, some of them might be correct, but after several hours, they became wrongĪgain. ![]() ![]() We are now seeing a very strange problem that the date and time were automatically changed to the old date time when the OS was built. In our environment, we have our domain controllers (Windows Server 2012 R2), and they are also the time source, and all of the Windows 10 We have some of the industrial PCs with Windows 10 Enterprise (build 10586) installed for the testing purpose. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |