KB5017327

Starting at 12:00 A.M. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by the Chilean government about a daylight saving time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

• ​Time shown in Windows and apps will not be correct.

• ​Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.

• ​Automation that uses date and time, such as Scheduled tasks, might not run at the expected time.

• ​Timestamp on transactions, files, and logs will be 60 minutes off.

• ​Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.

• ​Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

To mitigate this issue, please see Possible issues caused by new Daylight Savings Time in Chile.

We are working on a resolution and will provide an update in an upcoming release.

Note We plan to release an update to support this change; however, there might be insufficient time to properly build, test, and release such an update before the change goes into effect. Please use the workaround above.

After installing this update, file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration > Preferences > Windows Settings in Group Policy Editor.

This issue was addressed in KB5018425. Installation of this update prevents and resolves this issue, but if any workaround was used to mitigate this issue, it will need to be changed back to the original configuration.