Windows Server 2016 Update problem - Error: 1734 - The array bounds are invalid.

[Maxstar]

The CBS logs do not reveal any useful information, but error 0x80244022 means HTTP 503 - the service is temporarily overloaded [WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL]

Is this server connected to an WSUS server?

 

[swagner]

Yes, it is.

 

[Maxstar]

Export the Windows Update log

• Right-click on the Start button and click Windows PowerShell (Admin).
• Copy and paste the following command into it, press enter afterwards

Get-WindowsUpdateLog

• Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
• Attach the logfile WindowsUpdate.log to your next reply.

 

[swagner]

The command is not executable. Path "C:\Program Files\Windows Defender\SymSrv.dll" is missing:

 

[Maxstar]

This is a common issue on Server 2016, but please try the following first.

Run the following command in an elevated prompt and post the result.

net stop wuauserv
net stop cryptSvc
net stop bits
ren %SystemRoot%\SoftwareDistribution SoftwareDistribution.old 
net start wuauserv
net start cryptSvc
net start bits

 

[swagner]

I had to stop wuauserv before, but everything went through. Services startet without errors.

A new try to run window update again yields 0x80244022.

 

[Maxstar]

Please follow these instructions to resolve the SymSrv.dll issue, attached a copy of this file from a clean Server 2016 VM here.

Then run the PowerShell command again and attach the WindowsUpdate log.

 

[swagner]

That worked. Her is the WindowsUpdate log:

PS C:\Windows\system32> Get-WindowsUpdateLog


Converting C:\Windows\logs\WindowsUpdate into C:\Users\adm.xx\Desktop\WindowsUpdate.log ...




    Verzeichnis: C:\Users\adm.xx\AppData\Local\Temp\WindowsUpdateLog




Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----       13.08.2024     11:48                SymCache


Eingabe
----------------
Datei(en):
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.25.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.26.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.27.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.28.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.29.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.30.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240808.212046.810.31.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.2.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.3.etl


0.00%4.78%9.55%14.33%19.10%23.88%28.66%33.43%38.21%42.99%47.76%52.54%57.31%62.09%66.87%71.64%76.42%81.19%85.97%90.75%95.52%100.00%


Ausgabe
----------------
Speicherabbilddatei:           C:\Users\adm.xx\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00000


Der Befehl wurde erfolgreich ausgeführt.






Eingabe
----------------
Datei(en):
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.4.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.5.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.6.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.7.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240812.153636.850.8.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20240813.113406.669.1.etl


0.00%9.25%18.50%27.75%36.99%46.24%55.49%64.74%73.99%83.24%92.49%100.00%


Ausgabe
----------------
Speicherabbilddatei:           C:\Users\adm.xx\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00001


Der Befehl wurde erfolgreich ausgeführt.






WindowsUpdate.log written to C:\Users\adm.xx\Desktop\WindowsUpdate.log


PS C:\Windows\system32>

 

[Maxstar]

Please attach this file: WindowsUpdate.log written to C:\Users\adm.xx\Desktop\WindowsUpdate.log

 

[swagner]

Sorry. Here it is.

The wsus server seems to be unavailable.

 

[Maxstar]

2024.08.13 11:35:53.5124350 1008  8352  WebServices     WS error: Fehler bei der Kommunikation mit dem Endpunkt bei https://wsus.w2005-servername.de:8531/ClientWebService/client.asmx"."
2024.08.13 11:35:53.5124358 1008  8352  WebServices     WS error: Vom Server wurde der HTTP-Statuscode 503 (0x1F7)" mit dem Text "Service Unavailable" zur??ckgegeben."
2024.08.13 11:35:53.5124373 1008  8352  WebServices     WS error: Der Dienst ist vor??bergehend ??berlastet.
2024.08.13 11:35:53.5124384 1008  8352  WebServices     Web service call failed with hr = 80244022.

Are you able to disconnect this server from the WSUS server to see if you can update the system using Windows Update?

 

[swagner]

It might be possible, but will probably require a GPO change.

 

[Maxstar]

Okay, could you also check the following: Fixing Windows Updates Failed with Error 0x80244022 | KC's Blog

 

[swagner]

A closer look at the WSUS server reveiled that the WSUS pool had stopped and it seems it does regulary.
Now, I used the recommended settings from microsoft instead of the default settings (see Windows Server Update Services (WSUS) best practices - Configuration Manager).
WSUS pool is restartet, but still the same error when updating.

Btw. WSUS is accessible from our other servers.

 

[Maxstar]

Ah, please do the following again in an elevated prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
ren %SystemRoot%\SoftwareDistribution SoftwareDistribution.old2
net start wuauserv
net start cryptSvc
net start bits

Check the following folders, just to be sure the are no leftovers.
- %systemroot%\SoftwareDistribution\DataStore
- %systemroot%\SoftwareDistribution\Download

 

[swagner]

When i just checked again without any service stopping/starting i saw that Updates were found *cheers*.

Thank you very much for your patience and successfull as well as professional help.

 

[Maxstar]

That's great news, let me know if there are any remaining issues...