WSUS offering Edge v110 to WS2012

Question

WSUS offering Edge v110 to WS2012

JRV 551

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.

JRV 551 Reputation points

2023-02-21T16:34:21.0266667+00:00

Not 100% certain that's what filled the disk. Don't know what else did it, but it may be coincidence as other WS2012 servers did not have enormous TEMP folders.

But now at another site where WSUS, this time on WS2019, is offering Edge 110.x to a WS2012 machine.
JRV 551 Reputation points

2023-02-21T16:37:03.7166667+00:00

Not 100% sure that the repeated Edge install was what filled the disk. Other WS2012 servers offered Edge did not have bloated %windir%\TEMP folders.

However, today I'm at a site with a WS2019 WSUS and one remaining WS2012 server, and that server is being offered Edge v110.x, and failing each time.
JRVcr 21 Reputation points

2023-02-23T15:26:47.0133333+00:00

At another site today with WSUS 2012 & 3 2012 servers, all offered Edge 110, and none have reported to WSUS since first failed install attempt.

I did try deleting the SoftwareDistribution folder on one server yesterday and reset WSUS authorization. After that it was reporting again. Not sure if the WSUS reauth was needed, but I do know that WSUS reauth alone doesn't fix it.

Latest install failure was today, so MS has not fixed the catalog yet.
JRVcr 21 Reputation points

2023-02-23T22:12:30.6066667+00:00

Have now confirmed that deleting %windir%\SoftwareDistribution is all that's needed to restore reporting. WSUS Authorization does not need to be reset.
TK 300 Reputation points

2023-02-27T22:10:55.46+00:00

We are seeing the same problem.
JRVcr 21 Reputation points

2023-02-27T22:50:25.7966667+00:00

Clarifying, resetting WU doesn't stop it from being offered. But in our case, about 2/3 of 2012 machines stopped reporting to WSUS after Edge 110 tried and failed to install. Resetting WU fixed reporting.
Paulius Petkevičius 0 Reputation points

2023-03-15T07:01:08.93+00:00

Microsoft Edge-Stable Channel Version 111 Update (and Edge-WebView2 Runtime) still offered for Server 2008 and Server 2012 when pointing to WSUS. Installation fails with error code 6BA.

I wonder how long will it take MS to notice this :)
JRV 551 Reputation points

2023-03-15T13:19:15.7333333+00:00

Paulius, you read my mind. If I'd had time I'd have posted this yesterday. Although I think it's possible they don't care and will never address it. WSUS is icky on-prem stuff.
Paulius Petkevičius 0 Reputation points

2023-03-22T13:18:04.7866667+00:00

Seems like build 111.0.1661.44 (release date 2023-03-16) is not offered for legacy OS anymore :) Cheers.
JRV 551 Reputation points

2023-03-22T15:12:20.8166667+00:00

You're right, Paulius! Even though it's icky old on-prem, and only affected antique OS's, they fixed it!
TK 300 Reputation points

2023-03-22T15:15:20.14+00:00

I am not seeing a fix. In March, the latest Edge 111 is still being offered to our 2012 R2 servers that already had Edge installed. It's only a small number, but we are having to manually update those servers.

4 answers

Your answer

JRV 551 Reputation points

2023-02-21T16:34:21.0266667+00:00

Not 100% certain that's what filled the disk. Don't know what else did it, but it may be coincidence as other WS2012 servers did not have enormous TEMP folders.

But now at another site where WSUS, this time on WS2019, is offering Edge 110.x to a WS2012 machine.
JRV 551 Reputation points

2023-02-21T16:37:03.7166667+00:00

Not 100% sure that the repeated Edge install was what filled the disk. Other WS2012 servers offered Edge did not have bloated %windir%\TEMP folders.

However, today I'm at a site with a WS2019 WSUS and one remaining WS2012 server, and that server is being offered Edge v110.x, and failing each time.
JRVcr 21 Reputation points

2023-02-23T15:26:47.0133333+00:00

At another site today with WSUS 2012 & 3 2012 servers, all offered Edge 110, and none have reported to WSUS since first failed install attempt.

I did try deleting the SoftwareDistribution folder on one server yesterday and reset WSUS authorization. After that it was reporting again. Not sure if the WSUS reauth was needed, but I do know that WSUS reauth alone doesn't fix it.

Latest install failure was today, so MS has not fixed the catalog yet.
JRVcr 21 Reputation points

2023-02-23T22:12:30.6066667+00:00

Have now confirmed that deleting %windir%\SoftwareDistribution is all that's needed to restore reporting. WSUS Authorization does not need to be reset.
TK 300 Reputation points

2023-02-27T22:10:55.46+00:00

We are seeing the same problem.
JRVcr 21 Reputation points

2023-02-27T22:50:25.7966667+00:00

Clarifying, resetting WU doesn't stop it from being offered. But in our case, about 2/3 of 2012 machines stopped reporting to WSUS after Edge 110 tried and failed to install. Resetting WU fixed reporting.
Paulius Petkevičius 0 Reputation points

2023-03-15T07:01:08.93+00:00

Microsoft Edge-Stable Channel Version 111 Update (and Edge-WebView2 Runtime) still offered for Server 2008 and Server 2012 when pointing to WSUS. Installation fails with error code 6BA.

I wonder how long will it take MS to notice this :)
JRV 551 Reputation points

2023-03-15T13:19:15.7333333+00:00

Paulius, you read my mind. If I'd had time I'd have posted this yesterday. Although I think it's possible they don't care and will never address it. WSUS is icky on-prem stuff.
Paulius Petkevičius 0 Reputation points

2023-03-22T13:18:04.7866667+00:00

Seems like build 111.0.1661.44 (release date 2023-03-16) is not offered for legacy OS anymore :) Cheers.
JRV 551 Reputation points

2023-03-22T15:12:20.8166667+00:00

You're right, Paulius! Even though it's icky old on-prem, and only affected antique OS's, they fixed it!
TK 300 Reputation points

2023-03-22T15:15:20.14+00:00

I am not seeing a fix. In March, the latest Edge 111 is still being offered to our 2012 R2 servers that already had Edge installed. It's only a small number, but we are having to manually update those servers.

Answer 1

Limitless Technology 44,776

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.

Arthur B Benedetti White 0 Reputation points

2023-02-22T21:10:55.7133333+00:00

we have an auto approval for all definitions and edge updates to All servers so would need to work some kind of exclusion to not have those updates sent to server 2008 and 2012, IS microsoft really not working on updating the update that is in the catalog that comes down to our WSUS servers
JRVcr 21 Reputation points

2023-02-22T21:28:42.67+00:00

...and worse, most (not all) 2012 servers at 2 sites (so far, I have one more 2012 site to visit tomorrow) have stopped reporting to WSUS once the update started trying to install. Coincidence or causation I don't know.

I've tried deleting a couple test servers from WSUS and resetting their WSUS authorization, but so far still not reporting.

Still only 1 computer whose C: filled due to TEMP folder, fortunately. Inclined to think of that as coincidence at this point. It's now excluded from the v110+ updates, is no longer trying to install it, and its TEMP folder is nearly as empty as it was after I cleared it.

I have 1 2012 server that is not reporting to WSUS effective with arrival of the buggy WSUS update catalog, and it is still trying to install the update. It has also been put in a WSUS group for which the update has not been approved, but in addition to not reporting, it doesn't seem to be polling the server for approved updates. Probably need to reset Windows Update on that server.

And may need to reset WU on the other non-reporting servers, too; the large number of repeated failed installs may have damaged it. That's more destructive so I'm waiting to see if resetting WSUS auth helps.

Contemplating removing the Policy that forces Edge Update to use WSUS, too, and let it revert to unmanaged Windows Update for Edge updates for the time being.

Working on replacing these 2012 servers ahead of EOS, but being delayed by this bug.

Answer 2

Limitless Technology 44,776

Double post

JRV 551 Reputation points

2023-02-21T17:01:32.6533333+00:00

Terrible forum system.

Answer 3

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.

Answer 4

Steiger, Christian 0

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")

Larry Brown 0 Reputation points

2023-03-23T01:40:01.1533333+00:00

Anyone know if this is resolved yet in WSUS?
JRV 551 Reputation points

2023-03-27T13:19:00.9233333+00:00

Some of us (me included, WS2012 WSUS & servers) are reporting it is resolved. Some are not.

Share via

WSUS offering Edge v110 to WS2012

4 answers

Your answer