Windows 8.1 (KB5017367) and Windows 7 (KB5017361) get September Patch Tuesday updates

Next step

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.

Next step

This is expected in the following circumstances:

• If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181.
• If you do not have an ESU MAK add-on key installed and activated.

If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

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.