What's new

[SOLVED] Windows Update Failure..for a long time. Windows 8.1

StormierNik

Well-known member
Joined
Nov 26, 2018
Messages
49
So uhh.. i only recently noticed that a windows update of mine has been failing for a rather long time. I think i had checked before, and gone forward in the issue but came across a roadblock and temporarily gave up, then forgot about it.

The update number is KB2976978, and as far as i can tell that goes as far back as 2014 from when it was supposed to install. Now, i don't mind how long itll take to install 4 years worth of updates but when running sfc /scannow, it did its attempt at repairs but couldn't fix everything. I've seen threads for similar issues but they say the solutions are per user.

I haven't gone any further than the sfc /scannow and not sure if i should run that DISM stuff. Here's the CBS.log for whatever's wrong in the meantime. View attachment CBS.zip
 

StormierNik

Well-known member
Joined
Nov 26, 2018
Messages
49
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-11-26 19:03:13.728
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 F-Secure.Qt_4_6_2 and file QtSql4.dll. File is reported as corrupt by SFC.
CORRUPT: QtSql4.dll of component F-Secure.Qt_4_6_2.


WARNING: Failed to get store name from identity name with return code 2 for component F-Secure.Qt_4_6_2 and file QtHelp4.dll. File is reported as corrupt by SFC.
CORRUPT: QtHelp4.dll of component F-Secure.Qt_4_6_2.








SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
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.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-11-26 19:19:02.583
----------------------EOF-----------------------

Ignore the attachement i just realized i had to put the whole folder
 

Attachments

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Hello and welcome! Do you still need assistance?
 

StormierNik

Well-known member
Joined
Nov 26, 2018
Messages
49
Yes! Thank you for answering. As another update, after the steps taken here when i tried to open my nvidia control panel, it told me that i had "no nvidia device detected". So i tried to system restore prior to doing all of those steps, but after some time taken for it it said the files weren't changed because it couldn't restore for some reason. I fixed the control panel issue by just reinstalling the same newer driver again but i thought that information about the failed restore might be important. I don't think that reversed any of the steps though based on what it told me.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Can you please attempt the update now and attach CBS.log after it fails.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put
    Code:
    tags around the log to break up the text.
 

Attachments

StormierNik

Well-known member
Joined
Nov 26, 2018
Messages
49
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-11-30 21:31:00.935
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Nikolas\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.cat
Successfully took permissions for file or folder C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.mum


Successfully copied file C:\Users\Nikolas\AppData\Local\niemiro\Archive\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.cat to C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.cat.
Successfully copied file C:\Users\Nikolas\AppData\Local\niemiro\Archive\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.mum to C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.mum.


Successfully restored ownership for C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.cat
Successfully restored permissions on C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.cat
Successfully restored ownership for C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.mum
Successfully restored permissions on C:\windows\servicing\Packages\Package_for_KB3008923~31bf3856ad364e35~amd64~~6.3.1.3.mum
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2018-11-30 21:31:02.294
Script hash: xpcd1/of2M3CY26Bruhe61n9bTpiNc0KAd9/giOrRjo=
----------------------EOF-----------------------
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Good. Retry updates now and attach CBS.log if any fail.
 

StormierNik

Well-known member
Joined
Nov 26, 2018
Messages
49
Under details it shows the update thats labeled as "important" and automatically checked to update as Windows 8.1 update KB2976978

But it also shows under optional that there are much newer updates seemingly of the same kind as follows:
KB3072019
KB3084905
KB3102429

For now i'll try the same update as before, which was the KB2976978 listed as important. There are other optional updates as well that aren't listed under the same format, just in case that may or may not be important to know
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
Top