[SOLVED] KB5023702 fails to install. SFC stuck at 75%

cjr307

Member
Joined
Apr 18, 2023
Posts
7
hi team,

I have a server that fails to install the KB5023702. it gets to like 3% hangs and fails. attempting to run sfc /scnnow and it also fails at 75% After reading other forums here i have attached the CBS.log file, components scanner.txt, and the components file. DISM online repair appears to function OK. I cannot run SFCFIX on the server, as 3rd party software is not allowed. Can anyone assist with this one? thanks in advance :-)

Server running 2019 Core as a virtual Machine
 

Attachments

Hi and welcome to Sysnative,

Here are the steps to manually fix this issue:
Warning: This fix is specifically for this system. Do not use this on another system.

1. Load the COMPONENTS hive with the following command in an elevated command prompt.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. Delete the corrupted registry key using the following command.
Code:
reg delete HKLM\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5 /f
3. Re-add this key using the attached Regfix.zip and merge the reg-file into the registry.
4. Download the file amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.zip.
5. Extract this ZIP-file and replace this folder "amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5" in the C:\Windows\WinSxS directory.
6. Note: you'll need to use ICACLS on the folder above to replace the payload files.
 

Attachments

Thanks for the reply Maxstar! i have completed the steps as instructed. Below are the next steps I have taken and still recevie a failure :-(

1. Load components hive.
2. deleted regkey
3. added regkey that was downloaded
4. replaced amd64 files in winsxs directory using icacls
5. re-attempted the install of KB5022702 - Failed :-(
6. cleared the windows update cache running below steps
7.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
8. rebooted server
9. re-attempted the install of KB5022702 - Failed :-(
10. Get-windowsupdatelog shows error - Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x800f0986
11. ran sfc /scannow - 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.
12. ran DISM.exe /Online /Cleanup-image /Restorehealth received error:

DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.4010

[===========================86.8%================== ]
Error: 0x800f0954

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
11. ran component scanner
12. attached files for review.

Please advise on next course of action. thanks
 

Attachments

Hi,

Here's the next fix.
Warning: This fix is specifically for this system. Do not use this on another system.

1. Load the COMPONENTS hive with the following command in an elevated command prompt.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. Delete the corrupted registry key using the following command.
Code:
reg delete HKLM\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138 /f
3. Re-add this key using the attached Regfix.zip and merge the reg-file into the registry.
4. Download the file amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138.zip.
5. Extract this ZIP-file and replace this folder "amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138" in the C:\Windows\WinSxS directory.
6. Note: you'll need to use ICACLS on the folder above to replace the payload files.
 

Attachments

completed these steps as oulined below. KB5023702 Failed :-(

1. reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. reg delete HKLM\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138 /f
3. added regfix.reg to the registry
4. copied amd folder into c:\windows\winsxs using icacls
5. reboot
6. attempt to install KB5023702 from manual download from Microsoft Update store - Failed
7. 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.

8. ran DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.4010

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
9. ran get-windowsupdatelog
10. Ran componentscanner.exe
11. logs attached for review.
12. Thanks again :-)
 

Attachments

Code:
2023-04-21 19:24:21, Error                 CSI    00000019 (F) Hydration failed for component Microsoft-Windows-Audio-DSound, version 10.0.17763.4131, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file dsound.dll with NTSTATUS -2146498170[gle=0x80004005]
2023-04-21 19:24:21, Error                 CSI    0000001a@2023/4/21:18:24:21.075 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2023-04-21 19:24:21, Info                  CSI    0000001b Hashes for file member [l:10]'dsound.dll' do not match.
 Expected: {l:32 ml:4096 b:72847adb59de6f64636558918aecf897747766035656003fe3052bd072a31fdc}.
 Actual: {l:32 b:3be44cb2c0f2ca03a368f87a400d2e60d40ca484ecd2ce1aa3fff34f4df14f52}.

2023-04-21 19:24:21, Error                 CSI    00000023 (F) Hydration failed for component Microsoft-Windows-Audio-DSound, version 10.0.17763.4131, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file dsound.dll with NTSTATUS -2146498170[gle=0x80004005]
2023-04-21 19:24:21, Error                 CSI    00000024@2023/4/21:18:24:21.130 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2023-04-21 19:24:21, Info                  CSI    00000025 Hashes for file member [l:10]'dsound.dll' do not match.
 Expected: {l:32 ml:4096 b:1bc9aa174e6c8545c457cf39abfc1631f05de15423537d5814c7eaf5e9fea5e0}.
 Actual: {l:32 b:6c9282de6ee250b8fd6c9b44fb438494a2fab0aba86e92b4d2f7f2c4eca70fb6}.

Hi,

Here's the next fix.
Warning: This fix is specifically for this system. Do not use this on another system.

1. Load the COMPONENTS hive with the following command in an elevated command prompt.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. Download the attached Regfix.zip and merge the reg-file into the registry.
3. Download the file WinSxS.zip.
4. Extract this ZIP-file and replace both folders in the C:\Windows\WinSxS\ directory.
 

Attachments

Thanks Maxstar! below are the steps:

1. load components
2. installed regfix
3. copied folder infrastructure into c:\windows\winsxs with icacls
4. reboot
5. attempted re-install of KB5023702 from manual download from Microsoft Update store -Failed :-(
6. reboot
7. 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.

8. ran DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.4010

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

9. componentsscanner.exe
10. logs attached
 

Attachments

Hi,

Open an elevated command prompt and run the following command.
Code:
reg Save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" "%systemdrive%\SBS.hiv"
Zip "SBS.hiv" and attach it to your next post.
 
Could you please check the following *.manifest files exist in this directory: C:\Windows\WinSxS\Manifests.

amd64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.1_none_4961a83d9a0c4afc.manifest
amd64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.4131_none_a6415185139fe3e0.manifest
wow64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.1_none_53b6528fce6d0cf7.manifest
wow64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.4131_none_b095fbd74800a5db.manifest
 
Confirmed they are there. Appended Date Modified to them for reference:

amd64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.1_none_4961a83d9a0c4afc.manifest-6/10/19
amd64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.4131_none_a6415185139fe3e0.manifest-3/17/23
wow64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.1_none_53b6528fce6d0cf7.manifest -6/10/19
wow64_microsoft-windows-audio-dsound_31bf3856ad364e35_10.0.17763.4131_none_b095fbd74800a5db.manifest -3/17/23

i would think that since you sent newer files wouldnt these dates have changed? Let me know if you need the files. thanks
 
Please merge the attached Regfix first, reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

what kind of evil sorcery did you just conduct? it worked! a few corrupted component and reg files? what the heck and a total head scratcher! Your a genius! thank you so much for your help on this!
 
Hi,

You're welcome. Glad to hear it worked and thanks for the kind words..
I'll mark this thread as solved..
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top