KB installation and SFC fails

Do the same for the following file:
Code: 
certutil -hashfile %systemroot%\WinSxS\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.2457_none_bd7385c50ef8c1c5\fms_metadata.xml SHA256
 
C:\WINDOWS\system32>certutil -hashfile %systemroot%\WinSxS\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.2457_none_bd7385c50ef8c1c5\fms_metadata.xml SHA256
SHA256 hash of file C:\WINDOWS\WinSxS\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.2457_none_bd7385c50ef8c1c5\fms_metadata.xml:
573f248c322c438fec2a38fc0f6ba980d396a88cdc83ce7d2eaefc074f9a21cc
CertUtil: -hashfile command completed successfully.
 
Please run the following command and post the result.
Code: 
reg query HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-font-staticcache_31bf3856ad364e35_none_efd4d71d01c45884 /s
 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-font-staticcache_31bf3856ad364e35_none_efd4d71d01c45884\10.0
10.0.14393.0 REG_BINARY 01
(Default) REG_SZ 10.0.14393.2969
10.0.14393.2969 REG_BINARY 01
 
All the hash values and also this key looks good, so I don't understand why SFC is still failing in relation to an invalid parameter.

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
 
It used to fail, but after I installed KB4103723 using dism /add-package it has run through without errors. I'm going to run it once more, though, and see if things have changed after the latest changes made.
 
CAOS said:
It took me several days to finally make dism /online /cleanup-image /restorehealth to complete successfully, but after having manually imported a missing kb using dism, it now runs without detecting errors.
Click to expand...
Which KB did you have installed? And could you please provide the CBS log before you installed this KB package?
 
No, the CBS is long gone, but I took some notes while I troubleshot this:

Dism is still failing, now with error 1734 "The array bounds are invalid", but at least this time the cbs log contained something useful:
19 occurrences of references to missing KB4103723
I'll try to download and install that one.

That failed "not applicable for this computer". Now trying with the same kb, but the "delta" instead of "cumulative".

Still not applicable.

C:\Users\plc\Downloads>expand -f:* windows10.0-kb4103723-x64_2adf2ea2d09b3052d241c40ba55e89741121e07e.msu c:\test
C:\test>dism /online /add-package /packagepath:c:\test\Windows10.0-KB4103723-x64.cab

This actually worked!

dism /online /cleanup-image /restorehealth worked too!
 
When this error occurs it is better to remove the remnants of the problematic update! And since you have used the delta version of this update it may explain the decompressing issue that you have at the moment in relation to the invalid parameter.

So there are a few options:
1. Restore the server before installing the delta update (recommended).
2. Try to uninstall the delta version of KB4103723
 
There are no restore points and the KB4103723 doesn't appear in the list of uninstallable updates (no big surprise given how it was installed).

I ran this command to get rid of it:
dism /online /remove-package /packagepath:c:\test\Windows10.0-KB4103723-x64.cab
It completed successfully.

sfc /scannow still fails at 44%
dism /online /cleanup-image /restorehealth still completes successfully.

I've attached the CBS.log, if you want to see what it looks like after those last commands.
 

Attachments

Hmm, please run SFC /Scannow again with Process Monitor running and provide the *.PML trace unfiltered with the latest CBS log.
 
Hi,

Step 1.
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • 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 again with Process Monitor Running.
Code: 
SFC /Scannow
 

Attachments

Please post the log of SFCFix as well to see if it completed without issues?
 
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • 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.

Please run the following commands in an elevated prompt and post the result.
Code: 
reg load HKLM\COMPONENTS C:\Windows\System32\Config\COMPONENTS
reg query HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_75472118cb02d82d
reg query HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_7f9bcb6aff639a28
 

Attachments

C:\test>reg query HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_75472118cb02d82d

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_75472118cb02d82d
S256H REG_BINARY 47C0DE3BA43D9DBD5E5F9EA79E2E658C162AA3EB335771E0CBCB53B1A8511B4A
identity REG_BINARY 4D6963726F736F66742D57696E646F77732D466F6E742D464D532C2043756C747572653D6E65757472616C2C2056657273696F6E3D31302E302E31343339332E302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853
c!microsoft-w..-deployment_31bf3856ad364e35_10.0.14393.0_5b528a78ae0515e9 REG_BINARY
c!microsoft-w..-deployment_31bf3856ad364e35_10.0.14393.0_a3797c15c780c2a3 REG_BINARY
f!fms_metadata.xml_1f2380fbad942f19 REG_DWORD 0x3
f!fms.dll REG_DWORD 0x3


C:\test>reg query HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_7f9bcb6aff639a28

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-font-fms_31bf3856ad364e35_10.0.14393.0_none_7f9bcb6aff639a28
S256H REG_BINARY 108F8CEAA82D5FC3F565FA1250E1B9777533D15698228654804157AC5763F021
identity REG_BINARY 4D6963726F736F66742D57696E646F77732D466F6E742D464D532C2043756C747572653D6E65757472616C2C2056657273696F6E3D31302E302E31343339332E302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D776F7736342C2076657273696F6E53636F70653D4E6F6E537853
c!microsoft-w..-deployment_31bf3856ad364e35_10.0.14393.0_d09a20e7966b05f3 REG_BINARY
c!microsoft-w..-deployment_31bf3856ad364e35_10.0.14393.0_906d9653103c9af9 REG_BINARY
f!fms.dll REG_DWORD 0x3
 

Attachments

Please find it attached to this message. SFC is still aborting at 44% btw.
 

Attachments

You must log in or register to reply here.

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

Back
Top