Skip to content

Consider dropping Windows Server 2019 / 1809 support #18910

Closed

Description

@tianon

The "extended support" is legit though, so I think we should maybe pick a project like GHA to mirror here and keep support for 2019 roughly as long as they do (they dropped 2016 - actions/runner-images#5994, which is also still in extended support mode).

Oh, well there it is: https://github.blog/changelog/2025-04-15-upcoming-breaking-changes-and-releases-for-github-actions/#windows-server-2019-is-closing-down

We’re beginning the process of closing down the Windows server 2019 hosted runner image, following our N-1 OS support policy. This image will be fully retired by June 30, 2025. We recommend updating workflows use windows-2022 or windows-2025.

Originally posted by @tianon in #18143 (comment)

Activity

  1. tianon commented on May 30, 2025

    @tianon
    MemberAuthor

    In my inbox today:

    The Windows Server 2019 runner image will be fully unsupported by June 30, 2025. To raise awareness of the upcoming removal, we will temporarily fail jobs using Windows Server 2019. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:

    June 3 13:00-21:00 UTC
    June 10 13:00-21:00 UTC
    June 17 13:00-21:00 UTC
    June 24 13:00-21:00 UTC
    What you need to do

    Jobs using the windows-2019 YAML workflow label should be updated to windows-2022, windows-2025 or windows-latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions