Tranquil IT Forum

Good morning,

We have the following version of WAPT:

• Debian

• WAPT Server version: 2.6.0.16552

• WAPT Agent version: 2.6.0.16552

• WAPT Setup version: 2.6.0.16552

• WAPT Deploy version: 2.6.0.16552

• WAPT Enterprise Edition

We are encountering errors when running WUA on our PCs for Windows updates.
Our WUA had the install_scheduling=2h option; at each scan launch, we had CPU spikes for 20 minutes. This is related to the analysis of our Bitdefender EDR at each WUA action.
We also noticed that each time we launched the program, we had a 700MB download for no apparent reason.

Are there any compatibility issues between Bitdefender and WAPT, and how can they be fixed?
Can we optimize our WUA to make it more "efficient"?
Do you need more information?

Sincerely,

gavit wrote: ↑Dec 19, 2024 - 4:05 PM Our WUA had the install_scheduling=2h option. Each time we launched the scan, we experienced CPU spikes for 20 minutes. This is related to the scan of our

Launching the installation every 2 hours might be a bit resource-intensive; a wsusscn2.cb file is normally only released once a month. Installing once a week is sufficient.

In this specific case, WAPT starts and communicates with the Windows Update engine to request an installation. If your EDR is using up resources, you should contact them to see what can be done.

However, you are experiencing strange behavior when re-downloading the wsusscn2.cab file

Can you check on your machine that you do indeed have "C:\Program Files (x86)\wapt\private\cache\wsusscn2.cab"?

The sum of this file should currently be:

SHA256: 4f98dfa834804636aff6826bbc713a5c51bab5bd10c243b332f4572d2942f3b3
SHA1: 245c3d96a847d4e741b264a509768b22fb717753

Can you also provide your Wua configuration?

Good morning,

We have excluded all .cab files from our EDR and the analysis problem is no longer present; we are in parallel with Bitdefender support to correct this problem.

Regarding the .cab download, we have checked and it is every 6-7 days.

On our machines we do indeed have "C:\Program Files (x86)\wapt\private\cache\wsusscn2.cab" with the following sum:

• SHA256 4f98dfa834804636aff6826bbc713a5c51bab5bd10c243b332f4572d2942f3b3

• SHA1 245c3d96a847d4e741b264a509768b22fb717753

Current WUA configuration Thank you for your help!

So I didn't quite understand; are the problems still occurring?

Is the download still working?

Hello,

Regarding the slowness during EDR analysis and "install_scheduling," excluding all .cab files is resolved. However, if we specifically trust: C:\Program Files (x86)\wapt\private\cache\wsusscn2.cab and C:\WINDOWS\SoftwareDistribution\ScanFile*\Source.cab, this error still occurs.

Can we improve our [waptwua] configuration?

Thank you in advance.