daylight time change in Egypt

Keep Windows Server 2019 and Windows Server 2022 on their latest cumulative update and configure them to use Egypt Standard Time; Windows will then apply Egypt’s daylight-saving transition automatically.

Required configuration

1. Deploy the latest monthly cumulative update through Windows Update, WSUS, or your normal patch-management system. DST changes are included in monthly rollups, and newer updates supersede previous DST/time-zone updates; standalone DST packages are no longer provided.^1^
2. Confirm that each Egypt-based server uses the correct Windows time-zone ID:

      tzutil /g
      tzutil /l | Select-String -Pattern "Cairo|Egypt"
   

   The expected ID is Egypt Standard Time, corresponding to (UTC+02:00) Cairo.^2^
3. If another zone is configured, set the correct one from an elevated command prompt or PowerShell session:

      tzutil /s "Egypt Standard Time"
      tzutil /g
      Get-Date
   

   Do not append _dstoff; that suffix disables automatic DST adjustment.^3^

Version-specific status

• Windows Server 2022: Microsoft explicitly documents Egypt’s 2023 DST change in cumulative update KB5087545. A server on KB5087545 or any applicable later cumulative update has that correction.^4^
• Windows Server 2019: Egypt time-zone changes are delivered through the normal cumulative-update mechanism. The available documentation does not identify the exact original Server 2019 cumulative update that first introduced the 2023 Egypt rule, so verify compliance by installing the latest applicable cumulative update rather than searching for or installing an old standalone DST package.^1^
• Egypt’s 2026 calendar edge case: Microsoft’s current advisory identifies the one-hour calendar/meeting issue from April 24–30, 2026 as affecting Windows Server 2016 only. It does not list Server 2019 or Server 2022 as affected.^5^

Expected operational impact

At the transition, local wall-clock time changes by one hour. Review workloads whose schedules are defined in local time, particularly:

• Task Scheduler jobs and backup windows
• SQL Server Agent or third-party schedulers
• Monitoring and report intervals
• Applications that store local timestamps instead of UTC
• Cross-region meetings and integrations

Domain authentication and time synchronization should continue to use synchronized UTC time; changing the displayed time zone is separate from setting the system clock manually. Avoid manual clock changes and registry edits. Microsoft specifically recommends using Windows Update for DST rules, and older Cairo registry-update articles should not be applied to Server 2019 or 2022.

For a fleet check, run:

$servers = Get-Content .\servers.txt
Invoke-Command -ComputerName $servers -ScriptBlock {
    [pscustomobject]@{
        Server   = $env:COMPUTERNAME
        TimeZone = (tzutil /g)
        LocalTime = Get-Date
        UTC       = (Get-Date).ToUniversalTime()
    }
}

The TimeZone result should be Egypt Standard Time; investigate any server showing a fixed UTC offset or a different regional zone.

References

1. Daylight saving time help and support - Windows Client
2. Default Time Zones
3. tzutil | Microsoft Learn
4. May 12, 2026—KB5087545 (OS Build 20348.5139) | Microsoft Support
5. Windows message center