Windows version is installing security updates.

milena petrovic 0 Reputation points
2026-05-22T09:51:04.7333333+00:00

The Microsoft Windows Bios version must be updated as the earlier version 22H2 is depreciated. Pushback is reoccurring on the Bios update already installed on a device and which is paused since October 10 2025.

Surface | Surface Go | Install and update

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-22T09:52:48.67+00:00

    Windows 10 version 22H2 is an operating system version, not a BIOS/UEFI firmware version. BIOS (or UEFI) updates are separate from Windows feature updates and are not labeled as “22H2.” Any statement that “the Microsoft Windows BIOS version must be updated because 22H2 is deprecated” is mixing up OS lifecycle status with firmware.

    Key points for this scenario:

    1. Windows 10 22H2 deprecation and security updates
      • Windows 10 support (including 22H2) ends on October 14, 2025. After that date, Windows 10 no longer receives free security updates, technical assistance, or security fixes from Microsoft.
      • Until that end-of-support date, Windows 10 22H2 continues to receive cumulative and security updates (for example, KB5065429 in September 2025 and KB5066791 in October 2025).
      • These updates are OS-level and do not represent BIOS versions.
    2. BIOS/UEFI vs. Windows version
      • Firmware (BIOS/UEFI) on Surface and other devices is provided as separate firmware updates, typically delivered via Windows Update under “firmware” or “Surface” categories.
      • Firmware versions do not use Windows feature labels such as “21H2” or “22H2.” Therefore, a “BIOS 22H2” requirement does not exist in the provided information.
    3. Surface firmware and configuration
      • On Surface devices, firmware features such as Secure Boot and TPM are managed in BIOS/UEFI, but these are independent of the Windows 10 22H2 lifecycle.
      • Access to BIOS/UEFI on supported Surface models is done at startup (for example, by using hardware buttons as documented for earlier Surface Pro devices), and changes there affect security features, not OS support dates.
    4. Interpreting the “pushback” on BIOS update
      • If a device is already running Windows 10 22H2 and is still within support (before October 14, 2025), it can continue to install security updates without any special BIOS version requirement indicated in the context.
      • Any recurring message or process that appears to “push back” on a BIOS update while citing Windows 10 22H2 deprecation is likely misinterpreting the OS end-of-support notice as a firmware requirement.
    5. Recommended handling
      • Ensure all available Windows Updates are installed, including any offered firmware/Surface updates, while Windows 10 is still supported.
      • Plan to move the device to Windows 11 on supported hardware because Windows 10 support ends on October 14, 2025.
      • Treat references to a “Windows BIOS 22H2” as an incorrect conflation of OS versioning with firmware; there is no BIOS update dependency for 22H2 deprecation in the provided material.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. S.Sengupta 32,031 Reputation points MVP Volunteer Moderator
    2026-05-23T00:23:18.1566667+00:00

    The repeated BIOS/firmware update prompt appears to be related to a Surface firmware update cycle rather than directly caused by Windows 10 22H2 deprecation itself. The Windows 10 end-of-support notice may be getting interpreted together with pending Surface firmware requirements for Windows 11 compatibility.

    Since other systems connect successfully through Remote Desktop, the issue seems specific to the new Surface device configuration and/or pending firmware state.

    • Complete all pending Surface firmware and driver updates using the official Surface Driver & Firmware package rather than relying only on Windows Update

    • Ensure the device is fully updated to Windows 11 and rebooted properly after firmware installation

    • Access Surface UEFI/BIOS once during startup to confirm firmware initialization completes successfully

    • Disable UDP transport for the RDP client on the Surface, as newer Surface devices sometimes encounter Remote Desktop negotiation issues with modern transport settings

    At this stage, the problem does not appear to require changes on the remote workstation itself.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.