[SOLVED] Windows Update Fails after Manual CURL update - Windows Server 2022

[Mahindrasys]

Team, We encountered the same CURL issue which is already mentioned by fellow members, After replacing the CURL file inside Windows folder, Windows updates are failed to install since November 2023, below is the output for SFC scan.

2024-09-03 23:41:23, Info CBS Repr: CBS Store check completes
2024-09-03 23:41:23, Info CSI 00000002 CSI Store 3043558325024 initialized
2024-09-03 23:41:23, Info CSI 00000003 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.20348.2641 (WinBuild.160101.0800)'.
2024-09-03 23:41:23, Info CSI 00000004@2024/9/4:06:41:23.440 Starting corruption detection (InnerFlags=2)
2024-09-03 23:41:23, Info CBS FLOW: Entering stage: CheckCsi
2024-09-03 23:41:57, Info CSI 00000005 Hashes for file member [l:8]'curl.exe' do not match.
Expected: {l:32 ml:33 b:664bb48bf3e8a7d7036e4b0029fa10e1a90c2562ad9a09a885650408d00dea1b}.
Actual: {l:32 b:dea302c69b0d7cce227ae5460f946e487fd302518016e5c19d05fa32c2bedd86}.
2024-09-03 23:41:57, Error CSI 00000006@2024/9/4:06:41:57.284 (F) onecore\base\wcp\rtllib\win32lib\delta_library.cpp(350): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl:eltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)
[gle=0x80004005]
2024-09-03 23:41:57, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2024-09-03 23:41:57, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240904055918.log to WER report.
2024-09-03 23:41:57, Info CBS Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-03 23:41:57, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-03 23:41:57, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-03 23:41:57, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-09-03 23:41:57, Error CSI 00000007 (F) Hydration failed with error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: Reverse Delta , IntegrityState Valid: true , RetrievedChecksum: 42562957 , ComputedChecksum: 42562957[gle=0x80004005]
2024-09-03 23:41:57, Error CSI 00000008 (F) Hydration failed for component Curl, version 10.0.20348.1668, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file curl.exe with NTSTATUS -1073283059. Matching Component = Curl, version 10.0.20348.1668, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas = true, GenerateReverseDelta = false[gle=0x80004005]
2024-09-03 23:41:57, Info CSI 00000009 Warning: Unable to repair payload file ([l:8]'curl.exe') for component ([l:65 ml:140]'amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the Sustem File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[Mahindrasys]

is Internet is mandatory to run this application? it got stuck on "checking for updates . . . "

 

[Maxstar]

Hi,

SFCFix should be run in offline environments as well, but if it's stuck on "checking for updates . . . " it may be that the tool is blocked by security or other behaviour blocking software? But I will mention one of the developers here to take note of this issue! cc @Tekno Venus

Here are the manual instructions to apply this fix without using SFCFix.

Open an elevated command prompt and run the following commands:

icacls "%systemroot%\WinSxS\amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6" /save "%userprofile%\desktop\perms.acl" /t
takeown /f "%systemroot%\WinSxS\amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6" /r
icacls "%systemroot%\WinSxS\amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6" /grant administrators:(F) /t

1. Extract the attached Files.zip file.
2. Copy the folder: "amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6" folder into the %systemroot%\WinSxS\ directory and run the following commands.

icacls "%systemroot%\WinSxS\amd64_curl_31bf3856ad364e35_10.0.20348.1668_none_26c540054f7719c6" /setowner "NT SERVICE\TrustedInstaller" /t
icacls "%systemroot%\WinSxS" /restore "%userprofile%\desktop\perms.acl" /t

Afterwards run SFC /Scannow again in an elevated prompt and post the result.

 

[Mahindrasys]

Thanks for the quick reply, i ran the same way, here is the CBS log.

 

[Maxstar]

Here is the next fix for the WOW64 component.

Open an elevated command prompt and run the following commands:

icacls "%systemroot%\WinSxS\wow64_curl_31bf3856ad364e35_10.0.20348.1668_none_3119ea5783d7dbc1" /save "%userprofile%\desktop\perms.acl" /t
takeown /f "%systemroot%\WinSxS\wow64_curl_31bf3856ad364e35_10.0.20348.1668_none_3119ea5783d7dbc1" /r
icacls "%systemroot%\WinSxS\wow64_curl_31bf3856ad364e35_10.0.20348.1668_none_3119ea5783d7dbc1" /grant administrators:(F) /t

1. Extract the attached FilesWOW64.zip file.
2. Copy the folder: "wow64_curl_31bf3856ad364e35_10.0.20348.1668_none_3119ea5783d7dbc1" folder into the %systemroot%\WinSxS\ directory and run the following commands.

icacls "%systemroot%\WinSxS\wow64_curl_31bf3856ad364e35_10.0.20348.1668_none_3119ea5783d7dbc1" /setowner "NT SERVICE\TrustedInstaller" /t
icacls "%systemroot%\WinSxS" /restore "%userprofile%\desktop\perms.acl" /t

Afterwards run SFC /Scannow again in an elevated prompt and post the result.

 

[Mahindrasys]

Wow @Maxstar , You are a real life saver, thanks man, it worked smooth , Thanks again for this entire community and your prompt response.

 

[Maxstar]

Hi,

You're welcome. Glad I could help to resolve this issue...