Windows 10: Need Help With Corrupt File (sfc /scannow)

Hello All,
My system was acting a little funny so I ran an sfc /scannow of the system from my command prompt. It came back with the message

Windows resource protection found corrupt files and was unable to fix them. The details are in the CBS log.Note that logging is currently not supported in offline servicing scenarios. Well I worked for a couple of hours to fix this error by restoring my computer then resetting my computer all to no avail, the error was still there. I finally re-formaated the drive and installed Windows 10 from scratch and there were no errors. Great. I did several things and updates and all kinds of things and still no error. Great. As soon as I installed my Microsoft 365 and ran the sfc /scannow the error reappeared. Of course I am not 100% sure that the two are connected but I think that that are.

Again I tried for hours to correct the error and I can not fix it with my limited knowledge and ability. In my CBS log I see that the error might be:

2016-06-02 18:58:43, Info CSI 00003e0a [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-02 18:58:43, Info CSI 00003e14 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-02 18:58:43, Info CSI 00003e15 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-06-02 18:58:43, Info CSI 00003e18 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-06-02 18:58:45, Info CSI 00003e7f [SR] Verify complete

I do know if that is the source of corrupt file, but I think it is and I can not figure out how to fix it. I also ran the command

DISM /Online /Cleanup-Image /RestoreHealth

several times and I was unable to fix the error. I get error: 0x800f081f, the source file could not be found, use the source option to specify the location of the files that are required to restore this feature.

I am running Windows 10 Pro but I not sure how to use Group Policy Editor to allow my system to fix this problem.

I need help. Any help would be appreciated.

Bennett

:)

 

sfc/scannow corrupt file

This is because the system has corrupt files and is partially able to repair some of them. Here is a snip from the log:

0000608e [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\IMJPPRED.DLL from store

2017-12-02 16:54:25, Info CSI 00006090 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMETC\IMTCTIP.dll from store

2017-12-02 16:54:25, Info CSI 00006092 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\IMJPSET.EXE from store

2017-12-02 16:54:26, Info CSI 00006094 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEKR\imkrapi.dll from store

2017-12-02 16:54:26, Info CSI 00006096 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\IMJPLMP.DLL from store

2017-12-02 16:54:26, Info CSI 00006098 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\imjpuexc.exe from store

2017-12-02 16:54:26, Info CSI 0000609a [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\IMJPTIP.DLL from store

2017-12-02 16:54:26, Info CSI 0000609c [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\APPLETS\IMJPSKF.DLL from store

2017-12-02 16:54:26, Info CSI 0000609e [SR] Repairing corrupted file \??\C:\WINDOWS\IME\IMEJP\DICTS\IMJPZP.DIC from store

2017-12-02 16:54:26, Info CSI 000060a0 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\imjputyc.dll from store

2017-12-02 16:54:26, Info CSI 000060a2 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEKR\APPLETS\imkrcac.dll from store

2017-12-02 16:54:26, Info CSI 000060a4 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEKR\DICTS\imkrhjd.dll from store

2017-12-02 16:54:26, Info CSI 000060a5 [SR] Could not reproject corrupted file...

I suggest doing a repair install, as some system files are missing:

http://www.yourwindowsguide.com/2016/06/how-to-...

http://www.tenforums.com/tutorials/16397-repair...

 

sfc/scannow corrupt file

https://1drv.ms/u/s!ApJz2K2MUntDhjqDF49EhWYTUO50

 

Did I respond to you on the same problem before ? Just wonder.

RE : DISM /Online /Cleanup-Image /RestoreHealh.................. I get error: 0x800f081f, the source file could not be found

Use the Tech Bench link below to download YOUR version of Windows 10 iso file.
http://www.microsoft.com/en-us/softw...load/techbench

Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.

Then open the elevated command prompt and copy and paste this................

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

When it is completed, you should get the report that the operation is successful.
Now run the sfc /scannow again. It should be ok this time.

 

Thanks. No, I have never had this problem before so I have never had to try to fix this kind of problem before.

I currently have a Windows 10 ISO on my computer dated from May 9th, will that work?

 

My method requires an iso from Tech Bench because I need Install.wim .
If your iso file was taken from Media Creation Tool ( MCT ), or taken from Sources folder from your installed Windows 10, then it will have Install.esd which will not work in my method.

It is best if you take the time to download from Tech Bench just to be sure.

 

Thanks. I am downloading it now. I am on slow internet, 5 mbps, but I will report back when I am done.

Thanks again.

 

WOW! WOW! WOW! Thank you very much. I performed the operations exactly as you described them and it fixed my issue. I will try to copy and paste that post into a word document file for my future reference because it was,

A. Quick
B. Easy
3. and it fixed my issues.

Thanks again.

Bennett

 

While you're waiting for the TB ISO, you might want to try

Download and run the Windows Update Troubleshooter

 

The process should work with install.esd as well.
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:H:\sources\install.esd:1 /limitaccess

Some members claim that using install. esd is not as successful as using install.wim - I've never experienced any issues using install.esd as the source

Moot at this point, but for your reference
I guess you can forget the Windows Update Troubleshooter too *Wink

 

You are welcome.
Now that problem is resolved, please mark the thread as Solved.
Thank you.