Windows 10: WIndows resource protection has found some corrupt files... No Fix Solved

Page 1 of 2 12 LastLast
  1.    15 Apr 2016 #1

    WIndows resource protection has found some corrupt files... No Fix


    Hello,

    I have tried to run sfc/ scannow and it gives me the notification that: WIndows resource protection has found some corrupt files but is unable to fix some of them. Details are included in the CBS.log.

    Is it ok to post the log here so someone can have a look at it?

    Thank you!
      My ComputerSystem Spec

  2.    15 Apr 2016 #2

    Hi, can you look thru it and check this..
    If the only failure report is about opencl.dll, this is about your Nvidia driver and can be ignored.

    However I believe that discrepancy was resolved after an update a little while back.

    See post #2 here
    sfc /scannow failed to repair certain files - Windows 10 Forums

    and #3 following.

    If that fails, then you can do an in-place upgrade repair install.
    An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.

    For this you need an installation medium with the same base build as you have installed.

    Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

    This will refresh Windows, after the manner of a Windows installation.
    - all/most associations will be unchanged
    - all your programs will be left installed
    - you will lose any custom fonts
    - you will lose any customised system icons
    - you may need to re-establish your Wi-Fi connection
    - you will need to redo Windows updates subsequent to the build you have used for the repair install
    - Windows.old will be created
    - system restore will be turned off- you should turn it on again and I recommend you manually schedule a daily restore point.
    - you will need to redo any language downloads including the display language if you changed that)

    This is one of the better features of Win10: as each major build comes out, that's your updated reference build, and as updates are mostly cumulative, there will be few to do.

    Recommendation:
    Before you perform this major repair procedure, do create a disk image.

    Please consider using disk imaging regularly. It's a brilliant way to
    - preserve your system (and your sanity)
    - back up your data
    - restore your system to a previously working state in a relatively short time

    Recommended: Macrium Reflect or Aomei Backupper (free) + their boot disk/device + large enough external storage medium.
      My ComputerSystem Spec

  3.    15 Apr 2016 #3

    Thank you i will try it out!
      My ComputerSystem Spec

  4.    24 Apr 2016 #4

    I have found 31 corrupt entry's through dism/scanhealth, now when i want to restore health it says that it can't find the source file location. I have tried entering gpedit.msc but apparently Win10 Home edition doesnt include this future.

    Would it be wise to add this future or do i better do a 'repair install'?
      My ComputerSystem Spec


  5. Posts : 1,875
    Windows 3.1 to Windows 10
       24 Apr 2016 #5

    download > image health - repair corrupt file < link in sig below...

    run option 1 and follow how to
      My ComputerSystem Spec

  6.    25 Apr 2016 #6

    Ok, I have made disk image yesterday and this morning I ran the program...

    after i did the scanhealth, it said the problem was repairable so I mounted the image of the recommended iso 64bit and started option 2, it gave me the notion it couldnt find the source files so i ran option 3, operation succesfull (mounting i suppose) and then it gave the notion source files could not be located and operation succefull (unmounting i suppose)

    So what do i do now, sfc scan? I just searched for the text file but couldnt find it on desktop so i went to windows/logs/dism and checked the file for Total Detected Corruption.

    Checking System Update Readiness.


    (p) CSI Payload Corrupt amd64_microsoft-windows-servicessnapin_31bf3856ad364e35_10.0.10586.0_none_5be97afcf0121814\services.lnk
    (p) CSI Payload Corrupt amd64_eventviewersettings_31bf3856ad364e35_10.0.10586.0_none_817d705fae0a5733\Event Viewer.lnk
    (p) CSI Payload Corrupt amd64_taskschedulersettings_31bf3856ad364e35_10.0.10586.0_none_d7709c22aeb417b7\Task Scheduler.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-c..termanagementsnapin_31bf3856ad364e35_10.0.10586.0_none_d79bb88420ae2d66\Computer Management.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-speech-userexperience_31bf3856ad364e35_10.0.10586.0_none_a88f8863f623d2ed\Speech Recognition.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-m..-odbc-administrator_31bf3856ad364e35_10.0.10586.0_none_d0d57fb6e80e3f5e\ODBC Data Sources (64-bit).lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-t..etpc-mathinputpanel_31bf3856ad364e35_10.0.10586.0_none_57271b70fb42a4a1\Math Input Panel.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-mspaint_31bf3856ad364e35_10.0.10586.0_none_1aa31efd98e8ec4b\Paint.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-charmap_31bf3856ad364e35_10.0.10586.0_none_7edf55b74eb25a19\Character Map.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-wordpad_31bf3856ad364e35_10.0.10586.0_none_ba40118c173cb7f2\Wordpad.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-sud-link_31bf3856ad364e35_10.0.10586.0_none_5bb3b3b77727a42e\Default Programs.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_10.0.10586.0_none_f9c9ceba07e30464\Disk Cleanup.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-f..client-applications_31bf3856ad364e35_10.0.10586.0_none_057f44bfd2bd9812\Windows Fax and Scan.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-iscsi_initiator_ui_31bf3856ad364e35_10.0.10586.0_none_6470c30a06691255\iSCSI Initiator.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-c..s-admin-compsvclink_31bf3856ad364e35_10.0.10586.0_none_5f17ea2284d04ef8\Component Services.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-xpsreachviewer_31bf3856ad364e35_10.0.10586.0_none_a1a0ebd8f88eb4bf\XPS Viewer.lnk
    (p) CSI Payload Corrupt wow64_microsoft-windows-m..-odbc-administrator_31bf3856ad364e35_10.0.10586.0_none_db2a2a091c6f0159\ODBC Data Sources (32-bit).lnk
    (p) CSI Payload Corrupt amd64_networking-mpssvc-shortcut_31bf3856ad364e35_10.0.10586.0_none_11dc8d62b71c6074\Windows Firewall with Advanced Security.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_10.0.10586.0_none_da61e5edcb6ec32f\Remote Desktop Connection.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-defrag-adminui_31bf3856ad364e35_10.0.10586.0_none_259ba7173a9c269a\dfrgui.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-m..diagnostic-schedule_31bf3856ad364e35_10.0.10586.0_none_205c3495240eb77a\Memory Diagnostics Tool.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.10586.0_none_66ffd6dc481743c2\System Configuration.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-advancedtaskmanager_31bf3856ad364e35_10.0.10586.0_none_3b6c733895d68477\Task Manager.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10586.0_none_288f56844b4b2341\Resource Monitor.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10586.0_none_288f56844b4b2341\Performance Monitor.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-a..roblemstepsrecorder_31bf3856ad364e35_10.0.10586.0_none_67772984f550f61f\Steps Recorder.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-msinfo32-exe_31bf3856ad364e35_10.0.10586.0_none_3861ff2fa4057c69\System Information.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.10586.0_none_3b570a9cf80c90b7\Windows Media Player.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-snippingtool-app_31bf3856ad364e35_10.0.10586.0_none_26499a8833fa2713\Snipping Tool.lnk
    (p) CSI Payload Corrupt amd64_microsoft-windows-stickynotes-app_31bf3856ad364e35_10.0.10586.0_none_79cc4f5663a2c321\Sticky Notes.lnk
    (p) CSI Payload Corrupt amd64_windows-defender-ui_31bf3856ad364e35_10.0.10586.0_none_a28eb67a8a54ab2a\Windows Defender.lnk


    Summary:
    Operation: Detect only
    Operation result: 0x0
    Last Successful Step: CSI store detection completes.
    Total Detected Corruption: 31
    CBS Manifest Corruption: 0
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 31
    Total Repaired Corruption: 0
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 0
    CSI Store Metadata refreshed: True

    This what is there so it seems to me nothing is repaired
      My ComputerSystem Spec


  7. Posts : 1,875
    Windows 3.1 to Windows 10
       25 Apr 2016 #7

    reboot and choose option 1 again...
    then Option 0 to create the details.txt

    All your corruption is shortcut lnk(s)
      My ComputerSystem Spec

  8.    25 Apr 2016 #8

    Yes it worked after i scannedhealth and created the text file it reports there is now only one left. I tried to repair it option two folllowing option three, again i got the message source files could not be located.

    (p) CSI Payload Corrupt amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.10586.0_none_3b570a9cf80c90b7\Windows Media Player.lnk

    Any insights on this?

    Thanks for explaining what it actually means btw, i was looking for that. And thanks for all your help!
      My ComputerSystem Spec

  9.    26 Apr 2016 #9

    Click image for larger version. 

Name:	2016_04_26_06_22_221.png 
Views:	13 
Size:	18.4 KB 
ID:	76757
      My ComputerSystem Spec


  10. Posts : 1,875
    Windows 3.1 to Windows 10
       26 Apr 2016 #10

    You are getting that error, because the Source (install.wim) does not contain the file needed..
    Most likely because the file can through a windows update...
    Try Option 2

    But do not run yourself ragged over 1 corrupt shortcut .lnk
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Build 14291 Ran sfc and received the error message as posted in the title. Ran this net start trustedinstaller in elevated command prompt. No help. However, dism /online /cleanup-image /restorehealth completed successfully. So, how to...
Is there any way to fix this? This is weird. I have tried a number of commands and started all of my services.
Found corrupt files (SFC scan) in Performance & Maintenance
Was on Win 8.1 and found nothing of the sort "windows did not find any integrity violations". Upgraded to windows 10 and boom "Windows Resource Protection found corrupt files but was unable to fix some of them." Full DISM log:...
Hi, just wanted to know what should one do if one gets the error and how does one troubleshoot it properly? I looked up the log on my system but it's just a really big lump of text.

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:21.
Find Us