[RESOLVED] New problem with WUA following the latest update 2.6.0.16767

[TomTom]

Hello everyone,

Since the last WAPT update (version 2.6.0.16767), customers are again experiencing problems scanning and installing Windows 10 updates.
The scan status remains "pending" or "needs scan" as if it's not starting at all. However, the morning before this update, everything was still 100% functional.
Have there been any configuration changes?

Thanks in advance,
Thomas

[TomTom]

Output of the wapt-get waptua-scan command:

Code: Select all

[DEBUG] Logging TSynLog with level=debug to C:\Program Files (x86)\wapt\log\wapt-get.log
2025-01-14 09:52:55,866 DEBUG Default encoding : utf-8
2025-01-14 09:52:55,866 DEBUG Caller: ['', 'waptwua-scan', '-ldebug']
2025-01-14 09:52:55,867 DEBUG Python path ['C:\\Program Files (x86)\\wapt', 'C:\\Program Files (x86)\\wapt\\python39.zip', 'C:\\Program Files (x86)\\wapt', 'C:\\Program Files (x86)\\wapt\\DLLs', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages\\win32', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages\\win32\\lib', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages\\Pythonwin']
2025-01-14 09:52:55,867 INFO Using local waptservice configuration C:\Program Files (x86)\wapt\wapt-get.ini
2025-01-14 09:52:55,869 DEBUG Config file: C:\Program Files (x86)\wapt\wapt-get.ini
2025-01-14 09:52:55,869 INFO Using openssl OpenSSL 3.1.7 3 Sep 2024
2025-01-14 09:52:55,872 DEBUG Thread 9824 is connecting to wapt db
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
2025-01-14 09:52:55,877 INFO User Groups:[]
2025-01-14 09:52:55,879 DEBUG Using host certificate C:\Program Files (x86)\wapt\private\clientpc.fr.hydac.int.pem for repo global auth
2025-01-14 09:52:55,881 INFO WAPT base directory : C:\Program Files (x86)\wapt
20250114 08525555  ! info  SetThreadName 2660 9824=Main
20250114 08525555  !  +    FileIsNewerOrDifferentOnServer https://waptserver/waptwua/wsusscn2.cab C:\Program Files (x86)\wapt\private\cache\wsusscn2.cab
20250114 08525555  !  +         WaptWget_Try https://waptserver/waptwua/wsusscn2.cab
20250114 08525555  !  +                 InitHttpTlsContext(TLSContext 023aee20, Url https://waptserver/waptwua/wsusscn2.cab, ServerCABundle C:\Program Files (x86)\wapt\ssl\server\fr-for-wapt1.ca.crt, ClientCertificatePath C:\Program Files (x86)\wapt\private\nbfrfor000045.fr.hydac.int.crt, ClientPrivateKeyPath C:\Program Files (x86)\wapt\private\nbfrfor000045.fr.hydac.int.pem, OnGetPrivateKeyPassword 023aedd8, OnPeerCertValidate 023aedc0)
20250114 08525555  !  -                 00.000.002
20250114 08525559  !  -         00.059.353
20250114 08525559  !  -    00.059.669
20250114 08525559  !  +    mormot.db.raw.sqlite3.TSqlDatabase(d961a8).DBOpen waptdb.sqlite
20250114 08525559  ! SQL        mormot.db.raw.sqlite3.TSqlDatabase(d961a8) 18us waptdb.sqlite PRAGMA page_size=4096 = true
20250114 08525559  ! SQL        mormot.db.raw.sqlite3.TSqlDatabase(d961a8) 213us waptdb.sqlite PRAGMA cache_size=10000 = true
20250114 08525559  ! SQL        mormot.db.raw.sqlite3.TSqlDatabase(d961a8) 30us waptdb.sqlite select count(*) from sqlite_master = true
20250114 08525559  ! DB         mormot.db.raw.sqlite3.TSqlDatabase(d961a8) "C:\Program Files (x86)\wapt\private\db\waptdb.sqlite" database file (0.9 MB) opened with PageSize=4096 CacheSize=10000 (39 MB)
20250114 08525559  !  -    00.000.623

20250114 08553904  !  +         mormot.db.raw.sqlite3.TSqlDatabase(d961a8).DBClose
20250114 08553904  ! DB                 mormot.db.raw.sqlite3.TSqlDatabase(d961a8) closing [C:\Program Files (x86)\wapt\private\db\waptdb.sqlite] 0.9 MB
20250114 08553904  !  -         00.000.206
20250114 08553904  !  -    00.000.211

[clafon]

We've had the same issue since upgrading to version 2.6.0.16767; some machines remain stuck in "need-scan" or "scanning" despite launching the "Search for Windows Updates to apply" action. The action starts and completes successfully.

[TomTom]

We've had the same problem since upgrading to version 2.6.0.16767; some machines remain stuck in "need-scan" or "scanning" despite launching the "Start searching for Windows updates to apply" action. The action starts and completes successfully.

It's reassuring to know I'm not the only one experiencing all these problems... That said, I think something is missing from the scan's execution...

[sfonteneau]

I'm redeploying a fresh Windows 10 machine with 22H2 to run a full test here.

Nothing has changed with Windows itself, so we're a bit surprised by the problem.
I'll test it and get back to you.

[sfonteneau]

I tried starting from scratch and couldn't reproduce your problem.

The wsusscn2.cab file will be released tonight; could you try it tomorrow?

[TomTom]

Hi Simon,

No better this morning, it doesn't even seem to be downloading wsusscn2.cab on any of our computers...

I'll call you later to discuss it directly.

Thanks,
Thomas

[clafon]

I tried starting from scratch and couldn't reproduce your problem.

The wsusscn2.cab file will be released tonight; could you try it tomorrow?

Test performed this morning, same result... the station remains in "NEED-SCAN" mode. As a result, our entire network has switched to this status

[t.heroult]

Hi,

I'm adding my system to the problem.
This affects ALL Windows 10 (22H2) and 11 (23H2 & 24H2) machines.
They remain in "NEED-SCAN" mode after the scan, and new updates are not being requested.

Windows 7 machines are currently being scanned; we'll see what happens with them.

[sfonteneau]

Hello,

I just tested it on TomTom.

Upgrading the agents with the latest version of WAPT solved the problem in his case: version: 2.6.0.16795-5c1227.

Could you try it and let me know how it goes?

Simon