Winsock2 APIs missing in Windows2019 environment.

[rectified95]

Description

Windows SDK 20348 is available in the Windows2019 image as per https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md#installed-windows-sdks

It includes WInsock2 APIs and structures such as https://docs.microsoft.com/en-us/windows/win32/api/winsock2/ns-winsock2-sock_notify_registration or https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-processsocketnotifications

I have a failing build (https://github.com/libevent/libevent/runs/5861846578?check_suite_focus=true#step:5:342) which uses those APIs, which suggests the right Winsock2.h header is not being used by the pipeline. (I solved the same compilation error locally by installing the new 20348 SDK)

How can I force the compiler to use the proper SDK version knowing that it's installed in the environment? Ideally, this would work OOTB like it does with my local Visual Studio.

Virtual environments affected

• Ubuntu 18.04
• Ubuntu 20.04
• macOS 10.15
• macOS 11
• macOS 12
• Windows Server 2019
• Windows Server 2022

Image version and build link

Failing build:
https://github.com/libevent/libevent/runs/5861846578?check_suite_focus=true#step:5:342
Build definition using the windows-2019 env:
https://github.com/libevent/libevent/blob/master/.github/workflows/windows.yml

Is it regression?

No response

Expected behavior

No response

Actual behavior

No response

Repro steps

Use any of the new APIs from https://docs.microsoft.com/en-us/windows/win32/winsock/winsock-socket-state-notifications
Observe compilation failures in the Github Actions Windows2019 environment.