SFC and DISM not working at all

2016-04-18
Hi, glad to be again intouch with you.
My laptop is one HPEnvy 17t-jooo – CTO Quad Edition, the previous OS was Windows 8.1 Pro 64bit andI upgraded it to 10 Pro 64bit the same day after receiving the Microsoftinvitation. On January 2016, I performed a clean installation due to difficultieswith the November 1511 upgrade. The issue was fixed and the current version is 10.586build 218 (wim version).
I’m the only user andI can boot as Administrator (built-in) or via my local account.

The rip worked like acharm up to recently, I just verified that in both accounts that sfc /scannow anddism /online /cleanup-image /restorehealth commands start to run but notachieving their goals.
Results:
In my own localaccount using yours IMAGE HEALTH v16.02.19 file, the messages are:
Press 1: Error 5,Access is denied.
Press 2: ditto.
Press 3, option 1:ditto.
Press 3, option 2(recommended): The request is not supported. Error 50.
Press 7: Please see fileattached.
Note: I mounted today thelast ISO file downloaded from TechBench.

Similarly, in myAdministrator account.

Besides, I tried totake ownership of the WinSxS folder but it wasn’t possible.

I will appreciate youradvice for solving these problems.
Best regards, Petrus07.

Kyhi said:

your log shows an OPENCL.dll error.. Known Issue...

what you are posting for results - I am un clear of the reasons...

What is the issue with the PC ????

Many thanks, Kyhi, for your comments.
My laptop works fine, the only problemes are SFC and DISM.
I posted such results as a mere information of the obtained results for each option.
Could you provide me guidance in order to fix the OPENCL.dll error?
Kind regards.

dalchina said:

Hi, if you have not yet started to use disk images, hope this will persuade you to... it's a great way to save yourself time and frustration.

Here's a very useful repair technique which should restore your installation, unless you have severe disk problems.
Precede it with this in case sthg has happened to your file system:

Windows key + X, click command prompt (admin)
chkdsk C: /F
Make sure the result is clear or fixed.

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.

Thank you, Dalchina, for your comments.
I use Acronis True Image 2016 regularly making full C disc images on an external disc (creating also WinPE recovery discs, just in case).
Performing the In-place upgrade repair install would not be a problem to me, but as mentioned by Kyhu will it also fix the OPENCL.dll error?
I will appreciate your opinion.
With best regards.

dalchina said:

Hi, the opencl.dll report in your sfc scan is a very well-known long-standing error, which i thought I had read had been solved- maybe a month or so ago. But it may depend on what version of the Nvidia driver you have.

That report alone does not indicate any problem with your PC.

Read all abart it! Read all abart it!
- Here's an indication of what you may find if you do a simple search of this forum for opencl.dll:

Many thanks, Dalchina, for the attached search on the OpenCL.dll issue.
I will read all them with great interest.
The video card is nVidia GeForce GT740M and its current driver is 10.18.13.5937 (automativally installed by Microsoft).
The second one is Intel, driver 10.18.15.4248 (also installed by Microsoft).
Thank you again and best regards!

Hi, dalchina
After reading the articles you addressed me and, particularly, that of the Microsoft Community, my conclusion, using common sense, is to wait the forthcoming Win10 upgrade. Therefore I thank you and Khyo as well for your willingness (and patience).
Please note that I just marked my issue as solved.
Have a nice weekend.

dalchina said:

I should have included this one specifically:
Microsoft Fixing opencl.dll issue in SFC /SCANNOW soon - Windows 10 Forums