[SOLVED] Windows 8.1 windows update failing

[ferris]

Hello,

First I just want to say thanks for being such a great resource! This site is underrated.

My problem is my windows update isn't working as of a few days ago. I can restart and install updates, and it seems to install it, but when I log on afterwards the update was not installed. I'm worried that I'm not getting security updates, plus I have some new hardware I want to install, and I'm afraid to do so when Windows is a bit unhealthy.

Brief history: This windows installation has had its fair share of problems. I've had some power failures and the odd BSOD, and I'll always run sfc and dism afterwards. Since December 2018 I haven't been able to get a clean run of dism (after a power failure I think). But I didn't have any other problems so I left it. A few days ago (07/07) however my PC locked up while I was playing a game. That lead to a BSOD boot loop, which I escaped by removing my graphics card. Thankfully I have onboard graphics. Since then however my windows update doesn't work.

I have tried every possible invocation of dism. Online, Offline, LimitAccess, using a DVD as a source, using a WIM file as a source, etc. The result is always the same:

DISM.exe /Online /Cleanup-image /Restorehealth


Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

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

SFCFix output:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-07-11 09:12:19.824
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component NetFx4-ServiceModel35_mof_files and file ServiceModel35.mof. File is reported as corrupt by SFC.
CORRUPT: ServiceModel35.mof of component NetFx4-ServiceModel35_mof_files.


CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe
CORRUPT: C:\Windows\winsxs\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     3
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-07-11 10:00:41.345
----------------------EOF-----------------------

CBS logs: CBS.zip

 

[Sysnative Windows Update]

Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

 

[writhziden]

Hello, and welcome to Sysnative Forums. I apologize in advance because there will likely be a slight delay in my initial analysis. I currently have pressing commitments with work this weekend and will probably not be able to fully investigate your update failure until Monday evening. I appreciate your patience.

 

[writhziden]

I spent the past couple days trying to track down replacements for the corrupted files on your system, but I will need a bit more information from you to supplement my efforts:

Retrieve 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.
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 SendSpace and just provide the link here.

 

[ferris]

Thanks writhziden for having a look at this. COMPONENTS.zip

 

[writhziden]

Happy to help. Below are steps for SFCFix:

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip (Also included as an attachment at the bottom of this post)
• 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. If the file is too large to copy and paste into your reply, upload it with the logs that we request in the next steps.

Step 2
System File Checker

1. Click on the Start button/screen 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. Allow any User Account Control box that appears.
3. When the command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, and press enter.
   
   sfc /scannow
4. Once the command finishes, if you see "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them" then proceed to installing updates, and if updates fail, attach your CBS log to your next post. If you see another message from sfc /scannow, proceed to Step 3.

Step 3
Export/Upload CBS log file
You only need to do this if sfc /scannow still reported corruption:

Read More:

1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
   On Windows Vista and Windows 7, click the Start button then click Computer.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Find and double click on the CBS folder.
5. Right-click on the CBS Text Document file, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
9. Attach the CBS.zip file.
   Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.

What to do if your CBS log file is too large to upload

Read More:

In some instances you will be unable to upload your CBS log file to our forum because it is too large.
To work around this problem you need to use a file sharing service to upload your attachment and then provide the link that is generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:

Microsoft OneDrive
Google Drive
Dropbox
ExpireBox
SendSpace
WeTransfer

 

[ferris]

Fixed! Thanks writhziden!!

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-07-17 21:42:01.020
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Lucas\Downloads\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_netfx4-servicemodel35_mof_files_b03f5f7f11d50a3a_4.0.9680.16462_none_b1b338384fdbd7b9\ServiceModel35.mof
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.0.9600.17801_none_c69e2d36e5eacd06
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe

Successfully copied file C:\Users\Lucas\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe to C:\Windows\WinSxS\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe.
Successfully copied file C:\Users\Lucas\AppData\Local\niemiro\Archive\WinSxS\amd64_netfx4-servicemodel35_mof_files_b03f5f7f11d50a3a_4.0.9680.16462_none_b1b338384fdbd7b9\ServiceModel35.mof to C:\Windows\WinSxS\amd64_netfx4-servicemodel35_mof_files_b03f5f7f11d50a3a_4.0.9680.16462_none_b1b338384fdbd7b9\ServiceModel35.mof.
Successfully copied file C:\Users\Lucas\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.0.9600.17801_none_c69e2d36e5eacd06\ieetwcollector.exe to C:\Windows\WinSxS\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.0.9600.17801_none_c69e2d36e5eacd06\ieetwcollector.exe.
Successfully copied file C:\Users\Lucas\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe to C:\Windows\WinSxS\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe.

Successfully restored ownership for C:\Windows\WinSxS\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe
Successfully restored permissions on C:\Windows\WinSxS\wow64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_67618a3620c1c6f2\mshta.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_netfx4-servicemodel35_mof_files_b03f5f7f11d50a3a_4.0.9680.16462_none_b1b338384fdbd7b9\ServiceModel35.mof
Successfully restored permissions on C:\Windows\WinSxS\amd64_netfx4-servicemodel35_mof_files_b03f5f7f11d50a3a_4.0.9680.16462_none_b1b338384fdbd7b9\ServiceModel35.mof
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.0.9600.17801_none_c69e2d36e5eacd06
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-ie-ieetwcollector_31bf3856ad364e35_11.0.9600.17801_none_c69e2d36e5eacd06
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-ie-htmlapplication_31bf3856ad364e35_11.0.9600.19400_none_5d0cdfe3ec6104f7\mshta.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2019-07-17 21:42:02.113
Script hash: ephSO03Al6RGRFdlgSLrMfTnWVSANLl39YXj8ILXdPg=
----------------------EOF-----------------------

SFC is clean.

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 did not find any integrity violations.

 

[writhziden]

Great news, and updates are working again?

 

[ferris]

Yes the update is fine! I was so excited about the clean scan that I forgot about it! Thanks again. I've made a donation to support the site.