[SOLVED] Server 2019 WindowsUpdate fails with 0x800703f1 on two servers [Server 1]

Knoskoloz · Sunday at 10:31 AM

No other security software as far as I'm aware of. If there used to be one it would have been Eset Antivirus.
Attached the CBS.
Thanks again mate.

Maxstar · Sunday at 10:34 AM

Okay, please run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

Knoskoloz · Sunday at 10:45 AM

C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.17763.5830

Abbildversion: 10.0.17763.5830

[==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen.
Der Vorgang wurde erfolgreich beendet.

C:\Windows\system32>

it worked without error

Maxstar · Sunday at 10:58 AM

Please run also the following command and post the result:

Code:

DISM /online /cleanup-image /AnalyzeComponentStore

Knoskoloz · Sunday at 4:46 PM

Hello,
I got this:
C:\Windows\system32>DISM /online /cleanup-image /AnalyzeComponentStore

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.17763.5830

Abbildversion: 10.0.17763.5830

[===========================99.6%========================= ]

Informationen zum Komponentenspeicher (WinSxS):

Von Windows-Explorer gemeldete Größe des Komponentenspeichers : 17.66 GB

Tatsächliche Größe des Komponentenspeichers : 16.32 GB

Freigegeben für Windows : 6.17 GB
Sicherungen und deaktivierte Features : 9.83 GB
Cache und temporäre Daten : 309.49 MB

Datum der letzten Bereinigung : 2023-07-17 00:14:43

Anzahl von Paketen, die freigegeben werden können : 5
Bereinigung des Komponentenspeichers empfohlen : Ja

Der Vorgang wurde erfolgreich beendet.

Maxstar · Monday at 3:20 AM

Hi,

Please run the following command and post the result, if it fails attach a new copy of the CBS logs.

Code:

DISM /online /cleanup-image /StartComponentCleanup

Knoskoloz · Monday at 3:39 AM

Hello,

C:\Windows\system32>Dism.exe /online /Cleanup-Image /StartComponentCleanup

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.17763.5830

Abbildversion: 10.0.17763.5830

[===========================99.0%========================= ]
[==========================100.0%==========================]
Der Vorgang wurde erfolgreich beendet.

Update still gives a 0xd0000022

Thanks again

Maxstar · Monday at 3:41 AM

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

Code:

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.

Knoskoloz · Monday at 4:08 AM

Hi,

attached the log

Maxstar · Monday at 4:12 AM

Please take a screenshot of the Windows Update Seetings screen, it seems it's an Dynamic (GDR) Update which is failing?

Knoskoloz · Monday at 4:26 AM

The update KB5043050 is failing.

Are these the screenshots you need?

Maxstar · Monday at 4:31 AM

Yes, please run the following command in an elevated prompt and attach services.txt to your next post.

Code:

WMIC SERVICE GET caption, name, startmode, state > "%userprofile%\desktop\services.txt"

Knoskoloz · Monday at 4:40 AM

Here it is

Maxstar · Monday at 4:44 AM

Please run the following commands and post the result:

Code:

sc start wlidsvc

wat a few seconds a run:

Code:

sc qc wlidsvc
sc query wlidsvc

Knoskoloz · Monday at 4:48 AM

C:\Windows\system32>sc start wlidsvc

SERVICE_NAME: wlidsvc
TYPE : 30 WIN32
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x7d0
PID : 4268
FLAGS :

C:\Windows\system32>sc qc wlidsvc
[SC] QueryServiceConfig ERFOLG

SERVICE_NAME: wlidsvc
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\Windows\system32\svchost.exe -k netsvcs -p
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Anmelde-Assistent für Microsoft-Konten
DEPENDENCIES : RpcSs
SERVICE_START_NAME : LocalSystem

C:\Windows\system32>sc query wlidsvc

SERVICE_NAME: wlidsvc
TYPE : 30 WIN32
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

Maxstar · Monday at 4:50 AM

Great, please attempt to update again and post the result. If it fails attach a new copy of the CBS logs.

Knoskoloz · Monday at 5:05 AM

Still fails.
I attached the log.
Thanks for keeping up the hard work.

Maxstar · Monday at 5:09 AM

Are you able to disconnect this server from the WSUS server so you can try to update using Windows Update itself?

Knoskoloz · Monday at 8:34 AM

Hello,

thanks mate it worked.
I switched from wsus to windows update and everything worked like a charm.
Thanks for everything!

Maxstar · Monday at 8:42 AM

Rich (BB code):

2024.09.16 09:35:33.0841661 7236  5584  Handler         *FAILED* [D0000022] UUP GDR: Completed
2024.09.16 09:35:33.0864105 7236  5584  DownloadManager *FAILED* [D0000022] GDR
2024.09.16 09:35:33.1925814 7236  5584  DownloadManager *FAILED* [D0000022] Error occurred while downloading update EFE7A171-E601-412A-B2E7-ABEFE4F1509B.1; notifying dependent calls.
2024.09.16 09:35:33.2269036 7236  6128  DownloadManager * END * Download Call Complete. Call 14 for caller UpdateOrchestrator has completed; signaling completion.
2024.09.16 09:35:33.2280367 7236  6128  Agent           Effective power state: AC; IsOnAC: Yes.
2024.09.16 09:35:33.2280455 7236  6128  IdleTimer       WU operation (DL.UpdateOrchestrator, operation # 123) stopped; does use network; is not at background priority
2024.09.16 09:35:33.2280500 7236  6128  Agent           Released network PDC reference for callId {920ED80D-CFE2-4637-BA78-55E55D6DC238}; ActivationID: 123
2024.09.16 09:35:33.2286029 1192  4788  ComApi          *RESUMED* Download ClientId = UpdateOrchestrator
2024.09.16 09:35:33.2286076 1192  4788  ComApi          Download call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0)
2024.09.16 09:35:33.2286152 1192  4788  ComApi          ClientId = UpdateOrchestrator: Exit code = 0x00000000; Call error code = 0x80240022
2024.09.16 09:35:33.2286167 1192  4788  ComApi          * END *   Download ClientId = UpdateOrchestrator
2024.09.16 09:35:33.2286733 7236  6472  Agent           WU client calls back to download call {920ED80D-CFE2-4637-BA78-55E55D6DC238} with code Call complete and error 0xd0000022
2024.09.16 09:35:33.2288952 1192  4712  ComApi          Download call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0)
2024.09.16 09:35:33.2289024 1192  4712  ComApi          * END *   All federated downloads have completed. ClientId = UpdateOrchestrator (cV = WVagyBT2wUSlE1Q7.10.1)
2024.09.16 09:36:04.4777145 7236  6128  Misc            Got WSUS Client/Server URL: https://wsus01.<domainname>.local:8531/ClientWebService/client.asmx""
2024.09.16 09:36:04.4792199 7236  6128  ProtocolTalker  WSUS certificate store is empty
2024.09.16 09:36:04.4792220 7236  6128  WebServices     WSUS TLS cert-pinning mandatory: No
2024.09.16 09:36:04.4792239 7236  6128  WebServices     Proxy Behavior set to 1 for service url https://wsus01.<domainname>.local:8531/ClientWebService/client.asmx
2024.09.16 09:36:04.4792636 7236  6128  ProtocolTalker  OK to reuse existing configuration
2024.09.16 09:36:04.4792670 7236  6128  ProtocolTalker  Existing cookie is valid, just use it
2024.09.16 09:36:04.4792681 7236  6128  ProtocolTalker  PTInfo: Server requested registration
2024.09.16 09:36:04.4873337 7236  6128  Misc            Got WSUS Reporting URL: https://wsus01.<domainname>.local:8531/ReportingWebService/ReportingWebService.asmx""

Hi,

You're welcome. Glad to hear the updates installed succesfully using Windows Update.

The access denied (0xd0000022) error only affects the WSUS server as we can see in the excerpt above. I've removed the domain name, but I would check the last purple link to see why this server cannot update using WSUS? Maybe it will show the issue about the access denied issue?

[SOLVED] Server 2019 WindowsUpdate fails with 0x800703f1 on two servers [Server 1]

Active member

Attachments

Windows Update Moderator, Security Analyst

Active member

Windows Update Moderator, Security Analyst

Active member

Windows Update Moderator, Security Analyst

Active member

Attachments

Windows Update Moderator, Security Analyst

Active member

Attachments

Windows Update Moderator, Security Analyst

Active member

Windows Update Moderator, Security Analyst

Active member

Attachments

Windows Update Moderator, Security Analyst

Active member

Windows Update Moderator, Security Analyst

Active member

Attachments

Windows Update Moderator, Security Analyst

Active member

Windows Update Moderator, Security Analyst