WSUS offering Edge v110 to WS2012

JRV 551 Reputation points
2023-02-20T15:25:42.2233333+00:00

WSUS (on WS2012) is offering Edge v110.x to WS2012 servers. Edge 109 was supposed to be the last major rev for WS2012 & R2, with 109 security updates through EOS in October, last I knew.

WIndows Update does NOT offer Edge v110 to WS2012.

The Edge update fails to install. But with the Group Policy enabled to install updates in real time that don't require restarts, it retries over and over until C:\Windows\Temp fills the disk. Had that happen overnight; I will need to check all the WS2012 servers.

MS needs to fix the WSUS catalog so this doesn't happen.

Windows for business | Windows Server | User experience | Other
{count} votes

4 answers

Sort by: Most helpful
  1. Limitless Technology 44,776 Reputation points
    2023-02-21T16:57:59.61+00:00

    In Windows WSUS offering Edge v110 to WS2012

    WSUS (on WS2012) is offering Edge v110.x to WS2012 servers. Edge 109 was supposed to be the last major rev for WS2012 & R2, with 109 security updates through EOS in October, last I knew.

    WIndows Update does NOT offer Edge v110 to WS2012.

    The Edge update fails to install. But with the Group Policy enabled to install updates in real time that don't require restarts, it retries over and over until C:\Windows\Temp fills the disk. Had that happen overnight; I will need to check all the WS2012 servers.

    MS needs to fix the WSUS catalog so this doesn't happen.

    It appears that there may be an issue with the WSUS catalog offering Edge v110 to WS2012 servers, despite Edge 109 being the last major revision for WS2012 & R2. It is not recommended to install updates that are not intended for your specific operating system, as this can cause compatibility and security issues.

    The fact that the update fails to install and continuously retries until it fills up the disk suggests that there may be a problem with the update package itself or with the installation process.

    In the meantime, it is recommended to disable the Group Policy that enables updates in real-time that do not require restarts to prevent further attempts to install the faulty update package. It is also a good idea to check all WS2012 servers to ensure that the disk has not filled up due to failed installation attempts.


  2. Limitless Technology 44,776 Reputation points
    2023-02-21T16:58:14.3433333+00:00

    Double post


  3. Paulius Petkevičius 0 Reputation points
    2023-02-28T08:20:31.5533333+00:00

    Same issue here! Two WSUSes for Server OSes (~1800 client servers on both, some unsupported OSes).

    Microsoft Edge-Stable Channel Version 110 Update for x64 based Editions (Build 110.0.1587.46)

    Microsoft Edge-WebView2 Runtime Version 110 Update for x64 based Editions (Build 110.0.1587.46)

    These and later Edge builds shown as Needed for Server 2008R2 / 2012 / 2012R2, failing to install, error codes 80240016 for Edge-Stable Channel and 80040902 for Edge-WebView2.

    Updates not detected when OSes checks at Windows/Microsoft Update.

    0 comments No comments

  4. Steiger, Christian 0 Reputation points
    2023-03-01T08:19:54.15+00:00

    Same issue here ...

    my personal workaround
    Using WSUS targed groups on old OS in order to seperate them for dedicated update aproval.

    howto:
    WSUS target group seperation for Server 2012 / 2012R2 using GPO + GPO WMI filter and regkey

    regkey
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]

    "TargetGroup"="Server_2012"

    wmi filter
    SELECT * FROM Win32_OperatingSystem WHERE Version like "6.%" AND (ProductType="2" OR ProductType="3")


Your answer

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