Windows 11, version 24H2 update history

All users

If you are trying to setup your device for the first time, you might face issues with the language selection page during the Out of Box Experience (OOBE). During the OOBE flow, you will observe that irrespective of the language selected in the language selection page, the button which displays ‘Continue in <language being translated>’ gets incorrectly translated and displays as ‘Continue in English’ in the selected language.

For instance, if you have selected ‘Español’ as your language, you will observe the display button gets translated as ‘Continuar en inglés’. However, after clicking the ‘Continue in English’ button and proceeding further, the installation and next steps will continue to be in your selected language and the OOBE flow will complete without any interruption.

Important You might be impacted by this issue only if you are setting up your device for the first time through OOBE. It occurs only when the device manufacturer used an image based on the August 2024 non-security preview update (KB5041865) or September 2024 security update (KB5043080) to install Windows.to install Windows. This issue does not apply if you are applying the August 2024 non-security preview update or later updates released via the Windows Update release channel and Microsoft Update Catalog website.

This issue was resolved in the Windows non-security preview update released on September 30, 2024 (KB5043178). Devices manufactured with this update, or later updates will not experience this issue. If your device was affected by this issue, installing this or later updates will prevent you from facing this translation issue in the rare case you need to go through OOBE again. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.

Enterprise users

After a fresh install or an In-place upgrade to Windows 11, version 24H2, you might face issues with connecting via DirectAccess. You might observe that the DirectAccess connection is not completing and remains in a ‘connecting’ state. Additionally, you can determine if you are affected by this issue by following the below steps:

• Open Windows PowerShell in administrator prompt. This can be accomplished by opening the Start menu and typing ‘powershell’ and selecting from the results on the right side of the start menu.

• Type the text ‘netsh interface httpstunnel show interface’ and press enter

• If your device is experiencing this issue, you’ll observe that the output includes the following text:

  • Last Error Code          : 0x57

  • Interface Status         : failed to connect to the IPHTTPS server. Waiting to reconnect

You are more likely to face this issue if your device is remotely connecting to a corporate intranet using DirectAccess. Home users of Windows using Home or Pro editions are unlikely to face this issue as DirectAccess is more commonly used in enterprise environments.

Note: Enterprise customers that require DirectAccess are recommended to evaluate Always On VPN (AOVPN) until a fix becomes available.

This issue is addressed in KB5044384.