[SOLVED] [7SP1Pro x64] CSI P.File Missing: F12Resources.dll, msfeeds.dll, System.Web.Mobile.

Click on Start - All Programs - Accessories.
Right-click on Command-prompt and select Run as administrator.
When command prompt opens, copy and paste the following commands into it, press enter afterwards.

Code: 
ren %systemroot%\System32\Spupdsvc.exe Spupdsvc.old
Wait for this to finish before you continue
Code: 
exit
Check Windows Update again and report the result.
 
Follow the instructions here to download and run the Windows Update Troubleshooter for Windows 7.
Did that resolve the issue ?
 
Hi PeterJ

This is the status:

Checking System Update Readiness
No errors detected

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

sfc /scannow
Windows Resource Protection found corrupt files but was unable to fix some of them
Attached CBS.log
Download CBS.log from Sendspace.com - send big files the easy way

Windows Update Troubleshooter
Windows Update error 0x80070490 Not Fixed

Think I managed to solve the continually reported SFC error:
Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:20{10}]"msisip.dll" from store

How:
1/ Windows Update> Change settings> Uncheck Microsoft Update > OK
2/ Reboot
3/ Windows Update click on “Get updates for other Microsoft products”
4/ Microsoft sadly blocks it's own site! :shame2: so to ensure you get more than the useless “Use your Start menu to check for updates.”
add Microsoft.com to Compatibility view settings
add https://*.microsoft.com to Trusted sites
5/ Click Install
6/ Reboot
 
Think I managed to solve the continually reported SFC error:
Click to expand...
Great, thanks for your feedback.
Are there any remaining issues ?
 
Hi PeterJ

Even though everything seems to be working the SFC is still reporting:

Windows Resource Protection found corrupt files but was unable to fix some of them
 Attached CBS.log
Download CBS.log from Sendspace.com - send big files the easy way

I did the:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Took a look at the sfcdetails.txt file and there is no CSI "Repairing corrupted file" line only a CSI "Repairing 0 components" with a "Repair complete"

I don't know how to decipher the CBS.log, if you could take a look and see what it's complaining about and give me heads up that would be appreciated. Thanks.
 
Hi PeterJ

1/ Booted computer into a Clean Boot state
2/ Checked to make sure only Microsoft Processes and Services were running using SysInternal's Process Monitor, Task manager and Services.
3/ Ran Sfc /sannow
4/ Same Result: Windows Resource Protection found corrupt files but was unable to fix some of them
 Attached the latest CBS.log
https://www.sendspace.com/file/vcqoor
 
Hey PeterJ

Just thought I'd add... a thought occurred to me why not try the old DISM that is in Windows 7, although it's limited in functionality....

1/ Ran:
DISM /Online /Cleanup-Image /Scanhealth

2/ It produced the following CheckSur.log which may tell us a bit more about what's wrong:
https://www.sendspace.com/file/o6285o
 
System Update Readiness Tool for Windows 7

CheckSUR.log:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-01-26 10:07
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 Not Marked 0x00000000 c!policy.14.0..g.vc140.mfc_f92d94485545da78_14.0.25325.0_882c42cee4e7ea43 amd64_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.25325.0_none_882c42cee4e7ea43
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..g.vc140.crt_f92d94485545da78_14.0.25325.0_d7585f6ff4959666 x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.25325.0_none_d7585f6ff4959666
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..g.vc140.crt_f92d94485545da78_14.0.25325.0_8fab2898e0196d60 amd64_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.25325.0_none_8fab2898e0196d60
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.mfc_f92d94485545da78_14.0.25325.0_643e18eddbf60d95 amd64_avg.vc140.mfc_f92d94485545da78_14.0.25325.0_none_643e18eddbf60d95
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.mfc_f92d94485545da78_14.0.25325.0_abeb4fc4f072369b x86_avg.vc140.mfc_f92d94485545da78_14.0.25325.0_none_abeb4fc4f072369b
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..g.vc140.mfc_f92d94485545da78_14.0.25325.0_cfd979a5f9641349 x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.25325.0_none_cfd979a5f9641349
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.crt_f92d94485545da78_14.0.25325.0_b36a358eeba3b9b8 x86_avg.vc140.crt_f92d94485545da78_14.0.25325.0_none_b36a358eeba3b9b8
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.crt_f92d94485545da78_14.0.25325.0_6bbcfeb7d72790b2 amd64_avg.vc140.crt_f92d94485545da78_14.0.25325.0_none_6bbcfeb7d72790b2
Summary:
Seconds executed: 6502
Found 8 errors
CSI C Mark Deployment Not Marked Total count: 8
 
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. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
64-bit: Downloading Farbar Recovery Scan Tool

2. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
4. Press the Scan button.
5. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
6. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
ChkDsk Scan

  • Click on Start - All programs - Accessories.
  • Rightclick on Command-prompt and select Run as administrator.
  • When command prompt opens, typ chkdsk into it, then press enter.
  • Wait for this to complete.
  • Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
  • Rightclick
    58a60a47ed1bd-ListChkdskResult.PNG
    ListChkdskResult.exe and select Run as administrator. Notepad will open the file ListChkdskResult.txt on completion. (The file ListChkdskResult.txt can be found on your desktop.)
  • Copy and paste this in your next reply.
 
Chkdsk did some cleanup.
Follow the instructions below.

Step 1:
Click on Start - All Programs - Accessories.
Right-click on Command-prompt and select Run as administrator.
When command prompt opens, copy and paste the following command into it, press enter afterwards.

Code: 
chkdsk c: /f /r
At the question "Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)", press Y.
Restart the system.

Do not press any key during the restart. This will allow CHKDSK to start.
Wait for this to complete. Please note that this may take several hours. Let it run even if it looks like the process has stopped!
On completion, the system will restart automatically.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 
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. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

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