[SOLVED] [7SP1 x64] WU DOESN'T work, plus a bunch of corrupt DLLs

BrianDrab said:
Thanks. Please do the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...

Hi Brian,

Here is the CheckSUR.log:



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-17 23:42


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972
(f) CSI C Mark Deployment Missing 0x00000000 c!0821253b661..112862867be_31bf3856ad364e35_6.1.7601.23037_87f371331c00d062 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da


Summary:
Seconds executed: 3084
Found 2 errors
CSI C Mark Deployment Missing Total count: 2

Looks like the same result as previous.

Best,
Jed
 
Looking at the date/time stamps of the files it appears that the CheckSUR log was BEFORE the fix.

Code: 
Checking System Update Readiness.
 Binary Version 6.1.7601.22471
 Package Version 26.0
 2018-03-17 [COLOR=#FF0000]23:42[/COLOR]

Code: 
SFCFix version 3.0.0.0 by niemiro.
 Start time: 2018-03-17 00:[COLOR=#FF0000]23:47[/COLOR].964
 Microsoft Windows 7 Service Pack 1 - amd64
 Using .txt script file at C:\Users\Jed\Desktop\SFCScript.txt [0]

As a result please run SURT again just to be sure.

Step#1 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
BrianDrab said:
Looking at the date/time stamps of the files it appears that the CheckSUR log was BEFORE the fix.

Code: 
Checking System Update Readiness.
 Binary Version 6.1.7601.22471
 Package Version 26.0
 2018-03-17 [COLOR=#FF0000]23:42[/COLOR]

Code: 
SFCFix version 3.0.0.0 by niemiro.
 Start time: 2018-03-17 00:[COLOR=#FF0000]23:47[/COLOR].964
 Microsoft Windows 7 Service Pack 1 - amd64
 Using .txt script file at C:\Users\Jed\Desktop\SFCScript.txt [0]

As a result please run SURT again just to be sure.

Step#1 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...

Hi Brian,

Sorry for the delay. Find the new text of the CheckSUR.log below:



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-22 10:52


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972
(f) CSI C Mark Deployment Missing 0x00000000 c!0821253b661..112862867be_31bf3856ad364e35_6.1.7601.23037_87f371331c00d062 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da


Summary:
Seconds executed: 1263
Found 2 errors
CSI C Mark Deployment Missing Total count: 2
 
Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

BrianDrab said:
Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
Click to expand...

Hi Brian,

See below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-03-23 00:12:22.149
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Jed\Desktop\SFCScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0821253b661..112862867be_31bf3856ad364e35_6.1.7601.23037_87f371331c00d062.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0821253b661..112862867be_31bf3856ad364e35_6.1.7601.23037_87f371331c00d062.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 216 datablocks.
Finish time: 2018-03-23 00:12:22.520
Script hash: IElaenKI31ntg+ge84CiIuTMNL36Sr8iOBK1LoL5pqQ=
----------------------EOF-----------------------

Many thanks.

Jed
 
Please do the following.

Step#1 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
BrianDrab said:
Please do the following.

Step#1 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...

Heya Brian,

See the CheckSUR.log below:



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-03-23 14:55


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Catalog Missing 0x00000002 bf249c39f839f63cd103c8609edb402f32803962a1888c86630f94b8ef043238.cat 0821253b661..112862867be_31bf3856ad364e35_6.1.7601.23037_87f371331c00d062 Missing catalog or invalid CatalogThumprint
(fix) CSI Catalog Missing CSI File Replaced Deleted CatalogThumbprint
(f) CSI Catalog Thumbprint Invalid 0x00000000 bf249c39f839f63cd103c8609edb402f32803962a1888c86630f94b8ef043238 a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9
(fix) CSI Catalog Thumbprint Invalid CSI Catalog Thumbprint Deleted bf249c39f839f63cd103c8609edb402f32803962a1888c86630f94b8ef043238
(f) CSI Missing Component Key 0x00000000 x86_a467ff35f8c5c4660f699d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_none_a79ceef208c90ce9 HKLM\Components\DerivedData\Components
(fix) CSI Missing Component Key CSI Registry Item Repaired Key created. There will be more reports as values are replaced.
(f) CSI Missing C Mark 0x00000000 c!a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9 x86_a467ff35f8c5c4660f699d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_none_a79ceef208c90ce9 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!a467ff35f8c..d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_a79ceef208c90ce9 successfully added to x86_a467ff35f8c5c4660f699d25df9fa45c_31bf3856ad364e35_6.1.7601.18833_none_a79ceef208c90ce9


Summary:
Seconds executed: 1100
Found 4 errors
Fixed 4 errors
CSI Catalog Missing Total count: 1
Fixed: CSI Catalog Missing. Total count: 1
CSI Missing Component Key Total count: 1
Fixed: CSI Missing Component Key. Total count: 1
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1
CSI Catalog Thumbprint Invalid Total count: 1
Fixed: CSI Catalog Thumbprint Invalid. Total count: 1


Best,
Jed
 
Perfect. Please do the following.


SFC Scan

  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 commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
BrianDrab said:
Perfect. Please do the following.


SFC Scan

  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 commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...

Hi Brian,

The cbs.txt file is attached.

Best,
Jed
 

Attachments

BrianDrab said:
Excellent. Check for Windows Updates and let me know which KB numbers show up that need installed.
Click to expand...

Hi Brian,

I've got 4 that are important:

Windows 7
KB4055532
KB4088875 (which had downloaded but failed to install a while back)
KB2952664

Windows Defender
KB915597

And then there are 29 optional updates:

Optional Updates.JPG

Best,
Jed
 
BrianDrab said:
Go ahead and attempt to install any remaining updates. Let me know how it goes.
Click to expand...

Hi Brian,

Looks like all the updates are installing! Amazing :) One curious thing has started, though. I'm finding that the initial time I start-up windows, it hangs and lags significantly (failing to open windows, freezing, etc.) If I restart, however, the computer is happy again. This has happened enough times now for me to wonder whether it is buggy. Do you think it's related to the fix, or just settling into its new, healthy state?

Thanks hugely for all the help.

Best,
Jed
 
If this happened right after all the updates then it's likely just settling into its new healthy state. If all updates are installed and you reboot 24 hours later and still have the issue then please let us know but you shouldn't.
 
BrianDrab said:
If this happened right after all the updates then it's likely just settling into its new healthy state. If all updates are installed and you reboot 24 hours later and still have the issue then please let us know but you shouldn't.
Click to expand...

Thanks so much, Brian. Everything looks sparkly new! Let me know if there is any way to leave immensely positive feedback for you!!

Best,
Jed
 
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