Windows 8.0 x64; Image Version: 6.2.9200.16384; Corruption; Please help

[Steveg722]

10:11 AM 2/9/2022

Hi PeterJ

FYI, I just uploaded this file
dism - Copy (32);220209_0750;AfterScanHealth.log

to my GoogleDrive page.

Its a copy taken at 7:50 AM today of my C:\Windows\Logs\DISM\dism.log file
that shows the detailed results (& lists the (16) "corrupt files" reported by the CMD_ADMIN;Dism /Online /Cleanup-Image /ScanHealth job run on 15r at 7:46 AM this morning.

LINK=
dism - Copy (32);220209_0750;AfterScanHealth.log


It would not upload here with "Attach files" here but thought you might find it helpful.


Steve

 

[PeterJ]

Provide the Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again. Note: If you find that you need to reboot and are unable to because this is a server then try Option#2 below.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to Gofile or WeTransfer and just provide the link here.

---

Option#2 (only if you are unable to follow the previous instructions)

• Please download the Freeware RegBak from here: Acelogix Software - Download products
  You will find it at the bottom of the page that the link brings you to.
• Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
• Click the New Backup button. Accept the defaults and simply click Start.
• When it says Finished successfully, click the Close button.
• This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
• This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
• Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
• Now right-click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
• Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Gofile or One Drive or WeTransfer and then just provide the link in your reply.
• You can close any open windows you have as well as the RegBak program now.

 

[Steveg722]

220210_0656 EST


Good morning PeterJ



Components Hive; per your request.

>15r;C:\Windows\System32\config\components.zip
220210_0649; 9,243KB


Look forward to your findings & proposed next steps.


Have a good one;
Thanks;
Steve

 

[PeterJ]

The 16 corrupted files are not mentioned in the components hive. Lets look somewhere else in the registry.

Export registry as hive

• Click on the Start button and in the search box, type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  
• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, please upload to WeTransfer and just provide the downloadlink here.

 

[Steveg722]

10:04 AM 2/14/2022 EST

Windows 8.0 x64; Image Version: 6.2.9200.16384; Corruption; Please help

Good morning PeterJ

Thanks for your feedback re "The 16 corrupted files are not mentioned in the components hive".

Per your request, please find ATTACHED the REGEDIT ComponentBasedServicing KEY exported as= ComponentBasedServicing


Thanks again for helping me
Steve

 

[PeterJ]

The fix below will replace 14 out of 16 corrupted files. We will deal with the 2 others later.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the file SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• 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.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Run the command Dism /Online /Cleanup-Image /ScanHealth in a elevated commandprompt.
When completed, copy the file C:\Windows\logs\dism\dism.log to your desktop.
Zip the copied file and attach the zipped dism.log to your next reply.

 

[Steveg722]

9:00 PM 2/14/2022 EST


Greetings PeterJ

Per your requests in Post#26;

Post#27; ACTIONS; Step1; >Just ran the SFCfix.exe/SFCfix.zip job you proposed in Post#26; You should find the resulting (SFCFix;220214_2003.txt as) SFCfix.txt file ATTACHED (& hopefully PASTED) to this Post#27
Post#27; ACTIONS; Step2; >Ran the command Dism /Online /Cleanup-Image /ScanHealth in a elevated commandprompt you proposed in Post#26
Post#27; ACTIONS; Step2; Retrieved (dism - Copy (34);220214_2040;AfterScanHealth.log AS DISM.log), ZIPPED, & Uploaded as DISM.zip
UPLOADED=SFCFix.txt
UPLOADED=DISM.zip


>BELOW ARE PASTED CONTENTS OF SFCFix;220214_2003.txt

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-14 20:03:12.755
Microsoft Windows 8 - amd64
Using .zip script file at M:\15r;WinBACKUP;201115_1042\15r;MAINT\SFCfixJOBs\220214_2000\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.20521_none_09ca69e5dda43c4a
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.16420_none_093fccd0c4878329
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.20534_none_d6e808234a20e915
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.16433_none_edc09573307153ce
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20544_none_f761e85d3a8d94ff
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20534_none_f760e8133a8e7ba8
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16442_none_0e3a8c7520dde617
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16433_none_0e39756320dee661
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20544_none_a6028e59ae9806d2
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20534_none_a6018e0fae98ed7b
Successfully took permissions for file or folder C:\Windows\winsxs\msil_system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_ae56cd5b31dcd6be\system.runtime.handles.dll
Successfully took permissions for file or folder C:\Windows\winsxs\msil_system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_7030242013e00517\system.net.webheadercollection.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_netfx4-system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_4aa421caa806d4ff\system.runtime.handles.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_netfx4-system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_b3a8cad9c9e824de\system.net.webheadercollection.dll

Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.20521_none_09ca69e5dda43c4a\uxtheme.dll to C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.20521_none_09ca69e5dda43c4a\uxtheme.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.16420_none_093fccd0c4878329\uxtheme.dll to C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.16420_none_093fccd0c4878329\uxtheme.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.20534_none_d6e808234a20e915\jscript9.dll to C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.20534_none_d6e808234a20e915\jscript9.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.16433_none_edc09573307153ce\jscript9.dll to C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.16433_none_edc09573307153ce\jscript9.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20544_none_f761e85d3a8d94ff\ieframe.dll to C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20544_none_f761e85d3a8d94ff\ieframe.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20534_none_f760e8133a8e7ba8\ieframe.dll to C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20534_none_f760e8133a8e7ba8\ieframe.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16442_none_0e3a8c7520dde617\ieframe.dll to C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16442_none_0e3a8c7520dde617\ieframe.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16433_none_0e39756320dee661\ieframe.dll to C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16433_none_0e39756320dee661\ieframe.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20544_none_a6028e59ae9806d2\mshtml.dll to C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20544_none_a6028e59ae9806d2\mshtml.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20534_none_a6018e0fae98ed7b\mshtml.dll to C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20534_none_a6018e0fae98ed7b\mshtml.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\msil_system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_ae56cd5b31dcd6be\system.runtime.handles.dll to C:\Windows\winsxs\msil_system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_ae56cd5b31dcd6be\system.runtime.handles.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\msil_system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_7030242013e00517\system.net.webheadercollection.dll to C:\Windows\winsxs\msil_system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_7030242013e00517\system.net.webheadercollection.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\amd64_netfx4-system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_4aa421caa806d4ff\system.runtime.handles.dll to C:\Windows\winsxs\amd64_netfx4-system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_4aa421caa806d4ff\system.runtime.handles.dll.
Successfully copied file C:\Users\Helen\AppData\Local\niemiro\Archive\amd64_netfx4-system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_b3a8cad9c9e824de\system.net.webheadercollection.dll to C:\Windows\winsxs\amd64_netfx4-system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_b3a8cad9c9e824de\system.net.webheadercollection.dll.

Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.20521_none_09ca69e5dda43c4a
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.20521_none_09ca69e5dda43c4a
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.16420_none_093fccd0c4878329
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-uxtheme_31bf3856ad364e35_6.2.9200.16420_none_093fccd0c4878329
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.20534_none_d6e808234a20e915
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.20534_none_d6e808234a20e915
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.16433_none_edc09573307153ce
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.0.9200.16433_none_edc09573307153ce
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20544_none_f761e85d3a8d94ff
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20544_none_f761e85d3a8d94ff
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20534_none_f760e8133a8e7ba8
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20534_none_f760e8133a8e7ba8
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16442_none_0e3a8c7520dde617
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16442_none_0e3a8c7520dde617
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16433_none_0e39756320dee661
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16433_none_0e39756320dee661
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20544_none_a6028e59ae9806d2
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20544_none_a6028e59ae9806d2
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20534_none_a6018e0fae98ed7b
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_10.0.9200.20534_none_a6018e0fae98ed7b
Successfully restored ownership for C:\Windows\winsxs\msil_system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_ae56cd5b31dcd6be\system.runtime.handles.dll
Successfully restored permissions on C:\Windows\winsxs\msil_system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_ae56cd5b31dcd6be\system.runtime.handles.dll
Successfully restored ownership for C:\Windows\winsxs\msil_system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_7030242013e00517\system.net.webheadercollection.dll
Successfully restored permissions on C:\Windows\winsxs\msil_system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_7030242013e00517\system.net.webheadercollection.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_netfx4-system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_4aa421caa806d4ff\system.runtime.handles.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_netfx4-system.runtime.handles_b03f5f7f11d50a3a_4.0.9200.18155_none_4aa421caa806d4ff\system.runtime.handles.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_netfx4-system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_b3a8cad9c9e824de\system.net.webheadercollection.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_netfx4-system.net.webheadercollection_b03f5f7f11d50a3a_4.0.9200.18155_none_b3a8cad9c9e824de\system.net.webheadercollection.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 20 datablocks.
Finish time: 2022-02-14 20:03:22.224
Script hash: uWCX0TiUxmkHm/jy0K3tayqhsW+YLd8opVjSqraW0BA=
----------------------EOF-----------------------


>BELOW ARE PASTED RECENT/RELEVANT LINES re "Checking System Update Readiness" FROM dism - Copy (34);220214_2040;AfterScanHealth.log AS DISM.log

2022-02-14 20:36:13, Info DISM DISM Package Manager: PID=8212 TID=9244
=================================
Checking System Update Readiness.

(p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac\ieframe.dll
(p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597\ieframe.dll

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 2
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 2
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 1735 seconds.
- CDISMPackageManager::Internal_Finalize


With your help, appears your prediction was correct that we now have the # of "corrupt files" now reported by DISM=2


Look forward to your feedback on progress/current status, & your thoughts as to how to resolve the "last 2 apparently corrupt files".


Could NEVER have done what we've done without your help!


Thanks,
Steve

 

[Steveg722]

9:32 AM 2/15/2022 EST

Good morning PeterJ

Not sure if this data might be helpful to you re "the last 2 corrupt Payloads" BUT figured I'd share it since it might possibly help you in some way.
FROM MY NOTES

220214_2124;SEARCHED=C:\Windows\WinSxS;SEARCHEDFOR=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac
ITEMSFOUND=2
FOUNDITEM=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac
WINEXP;WINEXP; SIZE=ABSENT; M=160504_0326; C=ABSENT
PROPERTIES; SIZE=26 bytes (26 bytes); M=ABSENT; C=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:45 PM
Folders: 1
Files: 1
Size: 26 bytes
SHA1 checksum for data: 6B8F9404C6A2F520048817D2DE79AC151A1780BF
SHA1 checksum for data and names: 49825ED66D109033BED94FCA0D2EDCDCF7C9742A
>FOUNDITEM=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac.manifest
WINEXP; SIZE=258KB; M=130717_1306
PROPERTIES; SIZE=257 KB (263,892 bytes); M=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:38 PM; C=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:38 PM
Name: wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac.manifest
Size: 263892 bytes (257 KiB)
SHA1: 1EC717BF920811A086523A9E66700A678C0CB9B7

220214_2131;SEARCHED=C:\Windows\WinSxS;SEARCHEDFOR=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597
ITEMSFOUND=2
>FOUNDITEM=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597
WINEXP; SIZE=ABSENT; M=160504_0326; C=ABSENT
PROPERTIES; SIZE=26 bytes (26 bytes); M=ABSENT; C=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:45 PM
Folders: 1
Files: 1
Size: 26 bytes
SHA1 checksum for data: 8E046088B6C1B2AF0419DCEB8E282DF621E4F495
SHA1 checksum for data and names: E1D26373AAD93A2E67DF16A5D6AD36625C62B2BA
>FOUNDITEM=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597.manifest
WINEXP;WINEXP; SIZE=258KB; M=160504_0326; C=ABSENT
PROPERTIES; SIZE=257 KB (263,892 bytes); M=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:38 PM; C=Wednesday, ‎July ‎17, ‎2013, ‏‎1:06:38 PM
Name: wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597.manifest
Size: 263892 bytes (257 KiB)
SHA1: 9AC78D0A1C65337F4E773229D0788D4E26E93C59


Have a great day,
Thanks,
Steve

 

[PeterJ]

Remove Update Manually

1. Click on the Start button and in the search box, type Command Prompt.
2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
3. When command prompt opens, copy and paste the following command into it, then press enter.
   wusa /uninstall /KB:2740448
   
4. Let me know if it says it was successful or if there are any errors.

 

[Steveg722]

5:15 PM 2/15/2022 EST


Hi PeterJ


Sometimes things are never simple but again, thanks for helping me deal with these "corruptions"

CMD_ADMIN
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>wusa /uninstall /KB:2740448

C:\Windows\system32>

5:00 PM 2/15/2022
WINPOPUP; Windows Update Standalone Installer
Update for Microsoft Windows (KB2740448) is required by your computer and cannot be uninstalled.


Understand I don't understand much about how DISM identifies a "corrupt Payload" to report BUT SEEMS to me we have evidence that the 2 DISM complaints relate to "a MISSING ieframe.dll file" in each of 2 "Folders" in C:\Windows\WinSxS. (Only files in those 2 folders currently are a FOLDERNAME.manifest file).
>Since Windows doesn't seem to allow us to "Uninstall KB:2740448", is there any way to know which Version of ieframe.dll is "missing fr ea of those 2 Folders?" & where we might find "clean copies of the 2 missing? files"?

Wish I could help more but obviously, we're dealing with transmission issues with Windows which is interesting but way beyond my normal neighborhood.


Please digest & share back your thoughts/proposals on what to try next.


Thanks,
Steve

 

[PeterJ]

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt 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.
• Attach that file to your next reply.

 

[Steveg722]

9:42 PM 2/15/2022 EST

PeterJ

Per your instructions in prior Post#31...

SFCFixScript.txt
over
SFCFix.exe

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-15 21:33:20.829
Microsoft Windows 8 - amd64
Using .txt script file at M:\15r;WinBACKUP;201115_1042\15r;MAINT\SFCfixJOBs\220215_0548\SFCFixScript.txt [0]

UPLOADED=SFCFix.txt

Steve

 

[PeterJ]

It looks like the 2 folders are missing. Lets have a look with another tool.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Attach the logfile Fixlog.txt to your next reply.

 

[Steveg722]

8:37 PM 2/16/2022 EST


Good evening PeterJ

Not understanding you Re "It looks like the 2 folders are missing."; Please take a look at evidence shared in my Post#28
Seems that verified the 2 folders "cited by DISM as having corrupt contents" are currently PRESENT BUT neither now include the apparently "expected"

ieframe.dll file (Instead, they both just have a *.manifest file).

REF per DISM.log; Checking System Update Readiness.

(p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac\ieframe.dll
(p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597\ieframe.dll

8:15 PM 2/16/2022
WINEXP;SEARCH=C:\Windows\WinSxS;SEARCHFOR=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac;FOUNDITEMS=2
wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac
wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac.manifest
NOTFOUND=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.20486_none_f7708be13a8211ac.ieframe.dll

WINEXP;SEARCH=C:\Windows\WinSxS;SEARCHFOR=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597;FOUNDITEMS=2
wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597
wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597.manifest
NOTFOUND=wow64_microsoft-windows-ieframe_31bf3856ad364e35_10.0.9200.16390_none_0e4a8b6320d11597.ieframe.dll

Nonetheless, as you requested in your Post#33, I ran the FRST64.exe app with the fixlist.txt file in same Folder.
Did have to tell Windows to "Run it anyway".
Hit "Fix"
Resulting NOTEPAD showed up as "fixlog.txt"; SavedAs fixlog2.txt; UPLOADED & ATTACHEDAS=fixlog.txt

Seems we're together stuck having to determine RootCause & resolve the last 2 items causing DISM to report "corruption"; Still seems to me I'm not sure why (DISM reports as 2 "ieframe.dll files found missing in 2 existing Folders"); Is it because the files are "absent" OR is it because something somewhere is telling DISM "they should be there"?

UPLOADED=Fixlog.txt

Look forward to your thoughts & proposed next steps to get this resolved.


Thanks,
Steve

 

[PeterJ]

The 2 folders are there but the file ieframe.dll inside these folders is not. Another file is also missing inside both folders.
Update KB2740448 isn't available anymore to download to extract the missing files.
As these is an old update for IE10 I think we can safely remove all references from the registry.
Please do following to start with.

FRST Registry Search

1. Click the Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Server Manager or Windows Features dialog.
   Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
   
5. Right-click on the file FRST64.exe and choose Run as administrator.
6. Copy and paste KB2740448 into the Search box and click the Search Registry button.
7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
8. You may close any remaining open windows now.

 

[Steveg722]

9:00 PM 2/17/2022

Hi PeterJ

>So thanks for clarifying your postion/now we agree re DISM reports "2 files as corrupt" (2 reported Folders are present but 1 file in ea

(ieframe.dll) is reported as "corrupt" but is actually missing; Further, you advise more 1 or more fileS are "missing in those 2 Folders" but you did not share those missing filenames or how your determined that.

>Understand your Post#35, your advised "there is no way today to download/reinstall WinUpdate=KB2740448 for Windows 8; Instead, you are proposing to manually take some steps to "remove all references to it in the Registry's (Compoenent Hive); Not sure IF I do that, what you are proposing I must/should do to make associated cleanups under C:\Windows\WinSxS (or do I just leave things there as the are)?
Q1>Would appreciate your response please.

Per your request in Post#35, ran FRSTC64.exe per your instructions and have ATTACHED/UPLOADED=SearchReg.txt

Look forward to your feedback/lessons/proposals.


Thanks,
Steve

 

[PeterJ]

Do not remove anything by yourself. Following fix will remove the found registry-items related to KB2740448.

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Run the command Dism /Online /Cleanup-Image /ScanHealth in a elevated commandprompt.
When completed, copy the file C:\Windows\logs\dism\dism.log to your desktop.
Zip the copied file and attach the zipped dism.log to your next reply.

 

[Steveg722]

9:21 PM 2/18/2022 EST


PeterJ

Executed your instructions as/per your Post#37

>Still curious; please share your thoughts/ideas re "What's to become of/by what means/& how the KB2740448 remnants under WinSxs will be addressed?

> saw a good result per DISM per Copy (35)AfterDISMscan.log

2022-02-18 19:41:40, Info DISM DISM Package Manager: PID=10512 TID=7268
=================================
Checking System Update Readiness.


Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 0
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True


Please find ATTACHED=
>Fixlog.txt
>dism - Copy (35)AfterDISMscan.log AS dism.zip
AS UPLOADED, BOTH SET TO READONLY

Look forward to your REPLY.


Thanks
Steve

 

[PeterJ]

"What's to become of/by what means/& how the KB2740448 remnants under WinSxs will be addressed?

The DISM log is clean now so there is no need to fix the missing files in the WinSxS folder.
We will do a final check.
Run the command sfc /scannow in a elevated commandprompt.
Provide a screenshot of the result.

 

[Steveg722]

11:56 AM 2/19/2022 EST

Good morning PeterJ

>Per your Post#39 INSTRUCTIONS,
>Ran command sfc /scannow in a elevated commandprompt
>RESULT=
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

Please find
ATTACHED=CBS - Copy (54);220219_0959;AfterSFCscannow.log AS CBS.log

So seems DISM & CBS Logs are not longer reporting "corruption";

Q1; Would you consider this online Win OS image as "clean"?
(ie, ready to save an image copy and then install the update for Windows8.1?)



Thanks for all your help,
Steve