[SOLVED] Windows 8.1 Updates running without end

[bottentier]

Hello to forum.
I would like to ask for assistance with a corrupted component store.
Windows 8.1 isn`t able to get updates.
I tried to fix with several options of dism, used sfc /scannow and tweaking windows repair.
Dism seems not to accept wim from recovery drive, esd from downloaded and mounted iso as dvd and/or converted wim from that iso copied on usb "esd-usb" to "restorehealth". Also tried with the original esd on that stick. (windows.iso 8.1 x64)
I know it is not the best start to recover a healthy status of the laptop if someone tried to find a solution without help. It gets more and more worth. ... At the moment it seems like I have "only" 5 problems.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-23 15:12:21.191
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Performed DISM repair due to manifest damage on component "amd64_microsoft-windows-gwx-ins_31bf3856ad364e35_6.3.9600.17738_none_3b5be32f2570afc5". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "amd64_microsoft-windows-gwx-task_31bf3856ad364e35_6.3.9600.17738_none_4cbc19399860846e". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "amd64_microsoft-windows-gwx-uninstall_31bf3856ad364e35_6.3.9600.17738_none_9e2adb1ccf3b5189". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "amd64_microsoft-windows-gwx_31bf3856ad364e35_6.3.9600.17738_none_a170b4f12a0c7680". See CBS logfile for more details.
WARNING: Performed DISM repair due to manifest damage on component "wow64_microsoft-windows-gwx_31bf3856ad364e35_6.3.9600.17738_none_abc55f435e6d387b". See CBS logfile for more details.




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 5
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: 2017-01-23 15:40:44.247
----------------------EOF-----------------------


I attatched 4 files to that post and here ist the explanation what it is about:
DISM is the complete DISM folder.
CBS1 and CBS2 is the complete CBS folder.
CBS-Kopie is the LOG file I copied after the first try to repair.

If you need additional information, let me know.

If someone is interested, I got a number of new bookmarks from the last week ;-))

 

[bottentier]

Hello,
I`m sorry, forgot to tell - possibly crashed drive is replaced and chkdsk has been running. Right now no more errors.

 

[bottentier]

Third post in this thread to prevent misunderstanding .....
chkdsk has no more errors. Windows still does.
Sorry, english isn`t my native language.

 

[bottentier]

UPDATE
Updates,
Updates,
Updates!!


SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-26 11:16:29.182
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-01-26 11:26:21.867
----------------------EOF-----------------------



I`ll be back in some hours to give a description.

 

[bottentier]

Hello forum,

I`d like to give a short description of my solution.

1st, thanks to the first visitor of my thread - Willy2.

Looking at his profile, I recognized his reply at the Guide - Verry Slow Scan Times When Checking for Updates.

https://www.sysnative.com/forums/windows-update/20476-guide-windows-vista-7-8-very-slow-scan-times-when-checking-updates.html

There he linked an article at

http://wu.krelay.de/en/

how to update the update client.
I tried this before, but just to install the newest client caused an endless looking for updates window. On that site Dalai told about his script that would install that client without searching in the update database.
I ran that script and after that I used, without trying to get updates, the tweaking.com windows repair tool. Rebooted in securemode I started direct to repair including the beta options.
The normal time of using that tool was about 1 hour. This time it took at least 3 hours.
Next reboot.
Windows searched for updates - found updates with an ammount of 1,5GB - a few hours more and the above posted sfcfix report showed no more errors.
When I started that tool first, after changing the defect harddrive, I had more than 300 errors.

Meanwhile my brother got his laptop back.
Thank you all for your realy helpful forum!!

bottentier