Cuba’s clock change was cancelled. Windows may still expect it
The Havana zone is staying at UTC−04:00. An outdated seasonal rule can shift meetings even when the underlying clock is correct.
Windows devices using Havana’s time-zone rules may show the wrong local time after Cuba decided to remain on daylight saving time. Microsoft says the country will stay at UTC−04:00, rather than making the change previously expected on November 1.
The Windows release-health message center records the decision announced on October 27 and warns about the effect on Windows time calculations. This is a geographical rule change, not evidence that the computer’s clock hardware has suddenly become inaccurate.
Correct UTC can still produce the wrong local time
A device needs both a reliable time reference and the correct rule for converting that reference into a local display. If the underlying UTC time is right but the time-zone database still expects a seasonal change, the displayed hour can be wrong anyway.
That distinction matters when diagnosing the problem. Synchronizing the clock again does not necessarily repair an outdated conversion rule. Conversely, changing a device’s absolute time to compensate can create a second problem once the time-zone rule is corrected.
Microsoft identifies the Havana zone affected by the old transition schedule. The practical exposure extends beyond computers physically in Cuba: a calendar or planning tool that calculates Havana times from those rules can also present a misleading conversion. That does not mean every calendar product is affected; services can use different time-zone data and update schedules.
Use an explicit offset while the rules catch up
For a meeting or handover involving Cuba, an explicit UTC time is a useful cross-check. Under UTC−04:00, 10:00 in Havana corresponds to 14:00 UTC. An invitation converted using UTC−05:00 would instead point to 15:00 UTC, creating the one-hour disagreement.
Microsoft points affected administrators to interim guidance and says the correction is planned for November security updates. The availability of that correction should be checked for the relevant Windows version; the announcement is not proof that every device already has it.
Until then, the useful habit is to confirm the intended instant with the other participant rather than trusting two apparently authoritative local-time displays. A time-zone name is convenient when its rules agree everywhere. During a last-minute national change, writing the UTC offset beside the appointment can prevent a very ordinary meeting from moving by an hour.
