2026-06 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5094123) - Error 0x80070057

Question

2026-06 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5094123) - Error 0x80070057

Rajan Kumar Singh 0

Azure sync ahent not installing , the updates on windows 2019 server is failing with (2026-06 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5094123) - Error 0x80070057). Tried DISM or /scannow or everything but unable to install this update and Azure sync agent not getting installed

0 comments

3 answers

Your answer

Answer 1

Jubin Soni 160

Hi @Rajan Kumar Singh , thanks for posting your issue here.

The sfc stalling at 41% points to component store corruption, which is why DISM and the KB keep failing too. Try this sequence:

Mount a Windows Server 2019 ISO and run DISM against it directly:

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\Sources\install.wim:1 /LimitAccess

Reboot, then retry sfc /scannow and KB5094123.

If it still fails, check C:\Windows\Logs\CBS\CBS.log and search for [SR] cannot repair to identify exactly which files are broken. If the corruption is deep, an in-place upgrade repair using the Server 2019 ISO (running setup.exe without wiping data) will rebuild the component store completely and is usually the fastest way out.

Please upvote and accept the answer if it helps!

Rajan Kumar Singh 0 Reputation points

2026-06-28T01:17:15.5533333+00:00

This server is in an Azure VM. We tried disabling the Antivirus, stopping the third-party services, DISM restorehealth, but still not able to get this KB5094123 installed on this server. We have KB5094123 installed on the other Windows Server 2019 and are working with no issues. In this server, we need to update Azure File Sync agents, and this is failing because this server does not have KB5094123, and the Azure File Sync agent will not get updated until the server patch is up-to-date.
Jubin Soni 160 Reputation points

2026-06-28T01:48:19.86+00:00

Have you checked C:\Windows\Logs\CBS\CBS.log and filtered for "FAILED" entries? That should help identify the exact error blocking the operation. Since this is an Azure VM (KB5094123 is a cumulative update), it's also worth verifying whether any Azure Update Manager policies or maintenance configurations at the subscription or management group level are affecting the update process.
Rajan Kumar Singh 0 Reputation points

2026-06-28T02:03:43.5933333+00:00

Under the same subscription and network, there is another VM server 2019. This KB5094123 was installed successfully on that. But not getting installed on this server, where I have to update the Azure file sync agent. Yes, I checked the logs on CBS.log. Below are the failed messages :

Failed to publish WNF_SPLT_SYSTEM_UPDATE_STATE [HRESULT = 0xd0000034 - NTST

Retrieved original failure status: 0x00000000, last forward execute state: CbsExecuteStateStageDrivers

SetProgressMessage: progressMessageStage: 0, ExecuteState: ExecuteStateNone, SubStage: 0

Setting ExecuteState key to: CbsExecuteStateStageDrivers

Failed reading PoqexecCmdline registry key [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Failed to get poqexec cmdline from Components\Configuration. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Clearing original failure status: 0x00000000

Setting ExecuteState key to: ExecuteStateNone

Setting RollbackFailed flag to 0

Clearing HangDetect value

Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone

Startup: Retrying failed packages.

Startup: Processing complete. [HRESULT = 0x00000000 - S_OK]
Jubin Soni 160 Reputation points

2026-06-28T02:24:47.8166667+00:00

The two errors in your CBS log are pointing to a missing PoqExec registry key (HRESULT 0x80070002 - ERROR_FILE_NOT_FOUND) and a driver staging failure (CbsExecuteStateStageDrivers). The missing registry key under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Configuration is the likely root cause, try running reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Configuration" to recreate it, then retry the update. Also run DISM /Online /Cleanup-Image /StartComponentCleanup followed by a reboot before retrying, as the driver staging failure suggests the component store needs cleanup.

If the key is missing on this VM but present on the working server, you can export it from the healthy VM via regedit and import it here, since both are WS2019 under the same subscription, the structure should be identical.
Rajan Kumar Singh 0 Reputation points

2026-06-28T02:46:10.8333333+00:00

I run this reg query on the server where KB5094123 is installed properly.

C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Configuration"

ERROR: The system was unable to find the specified registry key or value.

There is no such entry in the registry
Jubin Soni 160 Reputation points

2026-06-28T02:52:26.25+00:00

The real culprit is likely the CbsExecuteStateStageDrivers failure, which means the update is failing during driver staging. Try these in order: first, run pnputil /scan-devices to force a driver re-enumeration, then reboot. If that doesn’t help, check Device Manager for any devices with errors or missing drivers, a problematic driver on this VM but not the other could be blocking the staging phase.

Also compare HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations between both servers, if this key has stale entries on the failing VM, clear it and retry. Lastly, check if there’s a pending reboot flag at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired that might be blocking the install
Rajan Kumar Singh 0 Reputation points

2026-06-28T03:07:34.4833333+00:00

This all seems good.

Answer 2

Rajan Kumar Singh 0

Yes, this is the Azure File Sync agent. Tried DISM /Online /Cleanup-Image /RestoreHealth , after reboot, also tried sfc /scannow , its getting stuck at 41% . Trying uudating windows server by downloading the KB or from online , get the error ,Windows Server 2019 (1809) for x64-based Systems (KB5094123) - Error 0x80070057). main issue I understand is windows security update is failing, I tried everything, but it's still failing

0 comments

Answer 3

Hi @Rajan Kumar Singh

Thank you for reaching out to Microsoft Q&A.

If by "Azure sync agent" you mean Azure File Sync agent, this behavior is documented by Microsoft.

Microsoft notes that Azure File Sync can fail with 0x80070057 / 0x80c84111 when required Windows updates are missing. The fix is to make sure the latest cumulative update for Windows Server 2019 is installed before installing/registering the agent.

Please try this sequence:

Run health repair from elevated Command Prompt:
- DISM /Online /Cleanup-Image /RestoreHealth
1. Reboot the server.
2. Ensure latest servicing/cumulative updates are installed for Server 2019:
  - Use Windows Update, or download from Microsoft Update Catalog.
    - For manual install, verify prerequisites in the KB article and then install.
    1. Reboot again.
    2. Retry Azure File Sync agent installation/registration.

If it still fails, please share:

Whether this is Azure File Sync agent or Microsoft Entra Connect/Cloud Sync agent
Exact installer/log error (FileSyncSvc, ServerRegistration.exe, or provisioning agent service name)
Output of installed updates check (for example, latest Server 2019 LCU present)

Official Microsoft sources

Microsoft troubleshooting for Azure File Sync states FileSyncSvc can fail with 0x80070057 when required Windows updates are missing, and recommends installing the latest cumulative update for Windows Server 2019 before agent install/registration: https://learn.microsoft.com/troubleshoot/azure/azure-storage/files/file-sync/file-sync-troubleshoot-service-fails-start
Azure File Sync release notes repeat this prerequisite and mention install failures if required Windows updates are not installed first: https://learn.microsoft.com/azure/storage/file-sync/file-sync-release-notes
Microsoft Windows Update troubleshooting checklist recommends DISM /Online /Cleanup-Image /RestoreHealth, installing latest servicing updates, and using Microsoft Update Catalog/manual install when needed: https://learn.microsoft.com/troubleshoot/windows-client/installing-updates-features-roles/troubleshoot-windows-update-issues

Please 'Upvote' (Thumbs-up) and 'Accept' as answer if the response was helpful. This will be helpful to other community members who face the same issue.

Best regards,

Andrew S Taylor