[SOLVED] Windows Server 2019 manual curl.exe fix has caused Windows updates to fail from November 2023

[DanielW1006]

Running sfc /scannow returns the following:
2024-06-27 11:24:30, Info CSI 000067e8 [SR] Could not reproject corrupted file \??\C:\Windows\System32\\curl.exe; source file in store is also corrupted
2024-06-27 11:24:30, Info CSI 000067e9@2024/6/26:23:24:30.080 Primitive installers committed for repair
2024-06-27 11:24:30, Info CSI 000067ea@2024/6/26:23:24:30.080 Primitive installers committed for repair
2024-06-27 11:24:30, Info CSI 000067eb Hashes for file member [l:8]'curl.exe' do not match.
Expected: {l:32 ml:4096 b:e6f66d659242aa7d6dd3c1967714c6cd3e0b11aaa235e7f7a150a3316dae8e61}.
Actual: {l:32 b:8dceda68623b9daf35e7d49f083bc178dcc4a68f8756e405c97f03b0525029eb}.
2024-06-27 11:24:30, Info CSI 000067ec [SR] Cannot repair member file [l:8]'curl.exe' of Curl, version 10.0.17763.4252, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2024-06-27 11:24:30, Info CSI 000067ed [SR] This component was referenced by [l:81]'Package_6768_for_KB5031361~31bf3856ad364e35~amd64~~10.0.1.9.5031361-12332_neutral'
2024-06-27 11:24:30, Info CSI 000067ee Hashes for file member [l:8]'curl.exe' do not match.
Expected: {l:32 ml:4096 b:e6f66d659242aa7d6dd3c1967714c6cd3e0b11aaa235e7f7a150a3316dae8e61}.
Actual: {l:32 b:ec8bf6762f75fdd8254e8e22fbd3ce9de6015939d9875160ada0c00f8374674e}.
2024-06-27 11:24:30, Info CSI 000067ef Hashes for file member [l:8]'curl.exe' do not match.
Expected: {l:32 ml:4096 b:e6f66d659242aa7d6dd3c1967714c6cd3e0b11aaa235e7f7a150a3316dae8e61}.
Actual: {l:32 b:8dceda68623b9daf35e7d49f083bc178dcc4a68f8756e405c97f03b0525029eb}.
2024-06-27 11:24:30, Info CSI 000067f0 [SR] Could not reproject corrupted file \??\C:\Windows\SysWOW64\\curl.exe; source file in store is also corrupted

Any assistance to repairing the corrupt curl file is appreciated. Please note that I would like to avoid installing a new version of Windows Server 2019 if possible, so surgically repairing the file is ideal.
Operating system details are below:
Windows Server 2019 Standard
Version 1809
OS build 17763.4974

 

[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 System File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[DanielW1006]

SFC result below:
C:\Windows\system32>SFC /Scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

CBS log and SFCFix.txt attached

 

[Maxstar]

Hi,

Here's the next fix.


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 System File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[DanielW1006]

SFC result below:

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

SFCFix document is attached

 

[DanielW1006]

Thank you for your help! I've just restarted the server after applying your fix and can confirm that the Windows Update service is operational again. I'll make sure to not try to attempt to patch the cURL files manually next time. Thank you again

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved...