Use DISM to Repair Windows 10 Image  

Page 20 of 84 FirstFirst ... 1018192021223070 ... LastLast

  1. Posts : 4,124
    Windows 3.1 to Windows 11
       #190

    So the 103KB Opencl.dll are being reported as corrupt by SFC ???

    Because it is funny that MS does not put the Opencl.dll into SysWow64 Folder
    But is present in Winsxs

    From Windows 10.0.10586 x64 OS
    Attachment 63355
      My Computer


  2. Posts : 134,174
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #191

    Kyhi said:
    So the 103KB Opencl.dll are being reported as corrupt by SFC ???

    Because it is funny that MS does not put the Opencl.dll into SysWow64 Folder
    But is present in Winsxs
    Yes Kyhi but only since we went to Windows 1511 This did not happen with the older release of Windows 10. Its been reported on NVidia's web site in their user forum for months. So Nvidia is well aware of this, also been reported to MS months ago, even by some insiders. This IS a Microsoft issue thou, not much Nvidia can do to fix it.

    If you upgrade your Nvidia drivers and Don't run sfc /scannow then the Nvidia drivers will not be removed, and the other 2 will not be replaced. We discussed this about 2 or 3 months ago for weeks if I remember right here in one of the forums. We just finally gave up trying to figure out how to fix this issue.
      My Computers


  3. Posts : 4,124
    Windows 3.1 to Windows 11
       #192

    Oh I know we did... But now I see pictures...

    Purple Arrows are WinSXS component store MS Files, due to size

    Red arrows Match AMD's file Size, but are also in driver store..

    your NVidia are not in your driver store, and Both x86 and x64 opencl.dll are the same file size..

    Note. it is very rare to find x86 and x64 files the same size..

    So it is a Nvidia Issue.. For which MS SFC is trying to Fix..
      My Computer


  4. Posts : 134,174
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #193

    Kyhi said:
    Oh I know we did... But now I see pictures...

    Purple Arrows are WinSXS component store MS File, due to size

    Red arrows Match AMD file Size, but are also in driver store..

    your NVidia are not in your driver store, and Both x86 and x64 opencl.dll are the same file size..

    Note. it is very rare to find x86 and x64 files the same size..
    Haha Kyhi I've posted these pics.....maybe not these exact same ones 2 or 3 times in the past. These are actually old ones, but the results are always the same, difference being my nvidia drivers would show a much newer file date. :)
      My Computers


  5. Posts : 4,124
    Windows 3.1 to Windows 11
       #194

    But now I see pictures...
    I guess I was late to that party before..

    Or OldTimers set in, in that moment..
      My Computer


  6. Posts : 17
    Windows 10 Pro x64
       #195

    lx07 said:
    Don't overstate it.

    Even if you do a clean install without Nvidea you'll still have the same issue (I have a 2 MacBook Pro, one with AMD, one with built in Intel and a Lenovo X201 with only Intel Graphics)

    All had the same issue.

    For me I don't care and I can easly fix it. For others who do have NVidea (like @OldMike65) you have to copy back the larger .dll

    It isn't tricky but I didn't give the answer (thanks all the same) - only if you didn't use that type of GPU.
    I don't know how to take this response?... I have other computers running the exact same Windows 10 build, NO sfc /scannow issues.

    The computer I am currently on, is the only one with an NVIDIA gpu. I also have a problem where it wakes from sleep, and the computer temps almost fry itself (I installed all new hardware)

    Even in the beginning of the SFC Command guide, it states.
    If you have the NVIDIA 359.06 graphics driver installed, you will get a hash mismatch for the opencl.dll file like below. You can safely ignore this.
    Yes, it does say
    You can safely ignore this.
    Yet it is still a problem for advanced users that use sfc /scannow when there is a problem.

    No one here is a Microsoft tech that can fix the issue. I was just stating my issue and the help that temporarily fixes it.
      My Computer


  7. Posts : 22
    Windows 10 Pro
       #196

    DISM - does it work?


    Does this Dism function ever work? I've tried this dozens of times using the examples shown here and elsewhere and ALWAYS get the 'source' not found. In this case, I'm trying to sort a Windows 10 installation - new and clean - which fails with corrupted files message from the scannow function.
      My Computer


  8. Posts : 17
    Windows 10 Pro x64
       #197

    seoras said:
    Does this Dism function ever work? I've tried this dozens of times using the examples shown here and elsewhere and ALWAYS get the 'source' not found. In this case, I'm trying to sort a Windows 10 installation - new and clean - which fails with corrupted files message from the scannow function.
    That is the problem a lot of us here are experiencing... I'm guessing it's those with certain hardware (Or everyone) Hopefully this can be fixed... I don't see how it has not been already, as I've had this problem for quite awhile now.
      My Computer


  9. Posts : 22
    Windows 10 Pro
       #198

    Thanks - relieved it's not just me but disappointed that there seems no way to fix the installation. It just refuses to update 2 updates. It beats me why they put out stuff like this that does the opposite of help.
      My Computer


  10. Posts : 118
    Windows 10 Pro
       #199

    seoras said:
    Does this Dism function ever work? I've tried this dozens of times using the examples shown here and elsewhere and ALWAYS get the 'source' not found. In this case, I'm trying to sort a Windows 10 installation - new and clean - which fails with corrupted files message from the scannow function.
    Make sure you're pointing to the right path, for instance once the ISO is mounted it will be a different drive number than where the install.wim resides. See my post #183 from page 19 on this Tutorial:

    One note: Altho I downloaded the TechBench ISO to drive letter J: when mounted it showed on drive letter K:? I went to install.wim on the J: drive & using a trick I learned from Edwin = to fetch the 'path' yourself the easiest way is: navigate to the item, Shift/Right Click/Copy as Path and Paste into the dialog but remove the quotation marks.
    The path it copied was in fact K:\sources\install.wim. I was a little confused as to what the full path name to install.wim might be but the Shift/Right Click/Copy as Path and Paste removed all doubt.
    richie
      My Computers


 

Tutorial Categories

Use DISM to Repair Windows 10 Image Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
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 01:44.
Find Us




Windows 10 Forums