Page 1 of 1

WUA Error

Published: May 5, 2023 - 11:40 AM
by smandel
Good morning,

For some time now, updates have stopped installing on my 2016 and 2019 servers managed by WAPT.
No problems with my 2012R2s.
Here is the error, which is identical on all servers:

Code: Select all

Ensure wuauserv Auto Update option is disabled
Download all updates
Scanning with windows updates rules:
{
 "direct_download":false,
 "default_allow":true,
 "include_potentially_superseded_updates":false,
 "filter":"Type='Software' or Type='Driver'",
 "download_scheduling":"2h",
 "install_scheduling":"",
 "install_delay":"",
 "postboot_delay":"10m"
}
Windows updates rules have been changed
Looking for updates with filter: Type='Software' or Type='Driver'
   Connecting to local update searcher using offline wsusscn2 file...
   Offline Update searcher ready...
Waiting for WUA search to complete
WUA Search completed !
Done searching
re-enabling wuauserv previous state: 0
(-2147352567, 'Une exception s’est produite.', (0, None, None, None, 0, -939523070), None)
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\waptservice\service.py", line 1907, in run
    self.running_task.run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 710, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\enterprise.py", line 244, in _run
    self.result = wua.download_updates(self.force, uuids=self.uuids)
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 1290, in download_updates
    self.scan_updates_status()
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 914, in scan_updates_status
    for update in self.updates():
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 849, in updates
    search_result = self.update_searcher().EndSearch(search_job)
  File "C:\Windows\TEMP\gen_py\3.8\B596CC9F-56E5-419E-A622-E01BB457431Ex0x2x0\IUpdateSearcher3.py", line 45, in EndSearch
    ret = self._oleobj_.InvokeTypes(1610743817, LCID, 1, (9, 0), ((9, 1),),searchJob
pywintypes.com_error: (-2147352567, 'Une exception s’est produite.', (0, None, None, None, 0, -939523070), None)

0x80020009 (Une exception s’est produite.): 0xc8000402 ((unable to get meaning for error code 0xc8000402))
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\waptservice\service.py", line 1907, in run
    self.running_task.run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 710, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\enterprise.py", line 244, in _run
    self.result = wua.download_updates(self.force, uuids=self.uuids)
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 1290, in download_updates
    self.scan_updates_status()
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 914, in scan_updates_status
    for update in self.updates():
  File "C:\Program Files (x86)\wapt\waptwua\client.py", line 849, in updates
    search_result = self.update_searcher().EndSearch(search_job)
  File "C:\Windows\TEMP\gen_py\3.8\B596CC9F-56E5-419E-A622-E01BB457431Ex0x2x0\IUpdateSearcher3.py", line 45, in EndSearch
    ret = self._oleobj_.InvokeTypes(1610743817, LCID, 1, (9, 0), ((9, 1),),searchJob
pywintypes.com_error: (-2147352567, 'Une exception s’est produite.', (0, None, None, None, 0, -939523070), None)
I tried enabling and disabling the Windows Update service with the scan, but it didn't help...

THANKS.

Re: WUA Error

Published: May 5, 2023 - 12:57
by sfonteneau
Hello,

I'm running an internal test with a Windows Server 2019 Standard, and it's working for now.


After some research, I

found that error code -2147352567 corresponds to 0x80020009 and
error code -939523070 corresponds to 0xc8000402.

Some Google searches mention problems with Windows Update channels. Have there been any changes in this area?

Are all 2019 and 2016 servers affected?

One common method is to delete the contents of %windir%\SoftwareDistribution\DataStore to clean up Windows Update.

Re: WUA Error

Published: May 9, 2023 - 10:15 AM
by smandel
Hi Simon,

yes, deleting the contents of the "SoftwareDistribution" folder seems to solve the problem.
I hadn't thought of that...

Thanks!