Microsoft Windows Server | WI448946

Impact: Jordanian government announced a Daylight Saving Time (DST) change for winter 2022. Originating KB URL: N/A Originating Build: N/A Resolved KB URL: https://support.microsoft.com/en-us/topic/5020023 Date Resolved: 2022-11-08T10:00:00-08:00 Vendor Message History: ======================= Published: 2022-11-08T17:59:41.403+00:00 ---------------------------------------- On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows: 1. Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone. 2. The Jordan time zone will permanently shift to the UTC + 3 time zone. Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later: - 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 using 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 Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device. Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows: - Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off. - Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”. Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly. Resolution: This issue was resolved in KB5020023 (https://support.microsoft.com/help/5020023). Affected platforms: - Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1 - Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 Published: 2022-10-22T01:18:11.66+00:00 ---------------------------------------- On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows: 1. Clocks will not be advanced by an hour at 12:00 a.m. on October 28, 2022 for the Jordan time zone. 2. The Jordan time zone will permanently shift to the UTC + 3 time zone. Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later: - 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 using 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 Jordan might also be affected if they are connecting to servers or devices in Jordan or if they are scheduling or attending meetings taking place in Jordan from another location or time zone. Windows devices outside of Jordan should not use the workaround, as it would change their local time on the device. Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows: - Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off. - Go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”. Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly. Next steps: We are working on a resolution and estimate a solution will be available in late October optional preview releases for the following versions of Windows: - Windows 11, version 22H2 - Windows 11, version 21H2 - Windows Server 2022 - Windows 10, version 21H2 - Windows 10, version 21H1 - Windows 10, version 20H2 (Enterprise and Education editions only) Note: Microsoft plans to release an update to support this change and some versions are estimated to be available before October 28, 2022. However, if an update is not available for the version of Windows you are using, please use the workaround above. Affected platforms: - Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1 - Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2