[SOLVED] waptua win11 and KB5025239

[guigeek]

Hello,
I'm using WAPT Enterprise 2.3.0.13516 and I'm having a problem with the Windows 11 update KB5025239.
The update remains pending despite being initiated from the command prompt.
The installation never actually starts on the machine itself.

In the logs it downloads:
Downloading https://xxxx/waptwua/windows11.0-kb5 ... 4f954d.psf

and after

C:\Program Files (x86)\wapt\cache\featureondemand_3294af9937b733783476da837b21943dc160faaa.wim put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\fodmetadata_client_792b7158195bd67711324cd21791150c5a8b3264.cab put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\edition_b7d4cae381a5971e5bf48a1246488c4e7861a0b0.wim put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\windows11.0-kb5023527-x64_076cd9782ebb8aed56ad5d99c07201035d92e66a.cab put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\windows11.0-kb5025239-x64_67425bb2f2561481da37d3dcf1a285f7a54f954d.psf put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\windows11.0-kb5023527-x64-baseless_830950f6687cc1b16959f6bfe2ce82798df92201.psf put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\languagepackclient_9bb203c316981be69e7fe22dbb6279ea6c60f072.wim put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\desktopdeployment_13e91e8e23003ac20cf1e15b5d7f543266be4526.cab put to local WUA cache for update
C:\Program Files (x86)\wapt\cache\97350548-a899-4e65-ac73-aa97250bd67f_wsus.aggregatedmetadata_3b0c49185ba6111f26c6487013945d1078e146af.cab put to local WUA cache for update
Copying 9 downloaded files to MS Wua cache
Skipped 07609d43-d518-4e77-856e-d1b316d1b8a8: MSXML 6.0 RTM Security Update (925673)
Skipped 12dda321-a84d-4072-8d6b-90875ed94c09: 2022-08 Security Update for Windows 11 22H2 for x64-based Systems (KB5012170)
Skipped 6d020686-c508-45f5-8efa-67900385e011: 2023-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5022497)
Denied fc5ae207-e126-4617-a7a5-8e2b05f690ef: Windows Malicious Software Removal Tool x64 - v5.112 (KB890830)
Scanning with windows updates rules:
{
"direct_download": false,
"default_allow": false,
"include_potentially_superseded_updates": false,
"filter": "Type='Software' or Type='Driver'",
"download_scheduling": null,
"install_scheduling": null,
"install_delay": null,
"postboot_delay": "10m"
}
Bypassing scan, no change since last successful scan
Writing status in local wapt DB
re-enabling wuauserv previous state: 0
Status: PENDING_UPDATES, 1 pending, 1 discarded

Installed updates: 4
Pending updates: 1
Discarded updates: 1
Reboot required: None

Last install date: 2023-05-10T15:00:29.865650
Last install result: None

WSUSScan cab date: 2023-04-10T23:44:26


Any idea?
It's the same with the same update on other posts.
THANKS !

[sfonteneau]

Hello,

Known issue:

https://learn.microsoft.com/en-us/answe ... by=helpful
https://lists.wapt.fr/pipermail/wapt/20 ... 04817.html

Microsoft has integrated URLs like "origin-prod.dcat.dsp.mp.microsoft.com" into wsusscn2.cab, URLs that responded initially but are no longer responding.

Yesterday was Patch Tuesday.
Therefore, there should normally be a new wsusscn2.cab, but I'm still waiting... it seems Microsoft is quite late this month.

I hope the problem will be resolved in the new version.

Simon

[guigeek]

Okay, perfect, thank you! We'll wait then

[t.heroult]

Thanks for the info, I was just wondering why there wasn't a new .cab file

[sfonteneau]

We wait, we wait ...


https://answers.microsoft.com/en-us/win ... c99?page=1

[t.heroult]

I can't help myself...
Who will have the reference?.

Meanwhile...~2.png (100.77 KB) Viewed 7327 times

[sfonteneau]

Hello,

the new wsusscn2.cab is out. The problematic cab has been replaced by KB502637, and the invalid URLs are gone.

The files are now distributed via dl.delivery.mp.microsoft.com.

The cab is still 9.1 GB, though...

Simon

[guigeek]

Thanks!
That's weird, it still doesn't appear in my KB list.

[sfonteneau]

This is most likely a machine that hasn't yet performed its scan.

To identify it, you can click on "Show clients" on the relevant page.