Hi Guys,
We've upgraded a client to Windows Server 2022, and all of a sudden my Windows service-applications does not recognise the Windows time zone.
We are on UCT+2 and now all my log entries from the Service-applications are 2 hours behind.
Running the "normal" applications from the Windows desktop is perfectly fine. Clock() reports to the correct time.
I've done a test and inserting a record from the Windows service-application causes the same 2 hours lag-result.
I've never seen this before, and believe it must be a setting or new adoption in Windows Server 2022 - specific to Windows Services.
Anyone experienced this recently?
I've done a lot of Googling and still have no solution yet. Any help will be appreciated.
Seems like others experienced the same, but unfortunately not answer yet ...
https://stackoverflow.com/questions/74277164/service-running-in-a-different-timezone-than-windows-with-a-specific-user
Topic: Urgent Issue: Windows Time Zone (Read 713 times)