Use DISM to Repair Windows 10 Image  

Page 18 of 84 FirstFirst ... 816171819202868 ... LastLast

  1. Posts : 1,116
    win 10 pro x64 os build 20H2
       #170

    yes i did that and all is well now it says it fixed something hope that fixes it :)
      My Computer


  2. Posts : 68,543
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #171

    Great news. I hope so as well. :)
      My Computers


  3. Posts : 118
    Windows 10 Pro
       #172

    Hi,
    Just updated nVidia driver to release 361.75 & am still getting the hash mismatch for opencl.dll. DISM tells me the store is repairable, so guess I really do have some corruption. RestoreHealth operation failed for version: 10.0.10586.0 = Either the repair source was not found or the component store cannot be repaired.

    Sorry if this is a silly question:
    So I do not have C:\$Windows.~BT but do have C:\ESD\Windows\sources\install.esd. Is there any reason I cannot use this? If not will proceed with the TechBench Windows ISO.

    thanks
      My Computers


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

    dogpark said:
    Hi,
    Just updated nVidia driver to release 361.75 & am still getting the hash mismatch for opencl.dll. DISM tells me the store is repairable, so guess I really do have some corruption. RestoreHealth operation failed for version: 10.0.10586.0 = Either the repair source was not found or the component store cannot be repaired.

    Sorry if this is a silly question:
    So I do not have C:\$Windows.~BT but do have C:\ESD\Windows\sources\install.esd. Is there any reason I cannot use this? If not will proceed with the TechBench Windows ISO.

    thanks
    If your only problem is Opencl.dll than you are all set, as this is a problem between Windows 10 and Nvidia.....more on the MS side thou. Anyone who has a Nvidia card from like the 700 series and up has this problem. SFC /Scannow will repair it by deleting one of them and replacing 2 others with MS ones......their is no real solution until MS decides to address this issue.
      My Computers


  5. Posts : 118
    Windows 10 Pro
       #174

    Hi OldMike65,

    I do have a GTX 760.
    At first figured there was no problem since the hash mismatch is exactly as posted on page 1 of SFC command tutorial, but after running the DISM CheckHealth command & getting The component store is repairable I was afraid there may actually be some corruption.

    I am building a new PC (my first) & will be moving the GTX 760 to the new build & reinstalling the old AMD GPU in the current desktop in a couple weeks. Guess I can wait to see what happens after with another sfc /scannow.
    Are you saying the DISM commands will come back as Healthy after removing the nVidia card/drivers?

    thanks
      My Computers


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

    dogpark said:
    Hi OldMike65,

    I do have a GTX 760.
    At first figured there was no problem since the hash mismatch is exactly as posted on page 1 of SFC command tutorial, but after running the DISM CheckHealth command & getting The component store is repairable I was afraid there may actually be some corruption.

    I am building a new PC (my first) & will be moving the GTX 760 to the new build & reinstalling the old AMD GPU in the current desktop in a couple weeks. Guess I can wait to see what happens after with another sfc /scannow.
    Are you saying the DISM commands will come back as Healthy after removing the nVidia card/drivers?

    thanks
    Yes if your only error is Opencl.dll BUT running SFC /scannow should repair the error with Opencl NOW. Unless you have another problem. I have the 750TI card myself. Same problem for last 6 months. It does not affect anything.
      My Computers


  7. Posts : 118
    Windows 10 Pro
       #176

    OldMike65 said:
    Yes if your only error is Opencl.dll BUT running SFC /scannow should repair the error with Opencl NOW. Unless you have another problem. I have the 750TI card myself. Same problem for last 6 months. It does not affect anything.
    Guess I think do have another problem. Yesterday ran sfc/ scannow three times with restart in between each per Brink's suggestion but each time I get: (& note it indicates Repairs Complete?)
    Code:
    2016-02-06 17:10:42, Info                  CSI    000050dc [SR] Beginning Verify and Repair transaction2016-02-06 17:10:44, Info                  CSI    0000512c [SR] Verify complete
    2016-02-06 17:10:44, Info                  CSI    0000512d [SR] Repairing 1 components
    2016-02-06 17:10:44, Info                  CSI    0000512e [SR] Beginning Verify and Repair transaction
    2016-02-06 17:10:44, Info                  CSI    00005130 [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-02-06 17:10:44, Info                  CSI    00005133 [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-02-06 17:10:44, Info                  CSI    00005134 [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-02-06 17:10:44, Info                  CSI    00005137 [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-02-06 17:10:44, Info                  CSI    00005139 [SR] Repair complete
    2016-02-06 17:10:44, Info                  CSI    0000513a [SR] Committing transaction
    2016-02-06 17:10:44, Info                  CSI    0000513f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    Since it does not appear to be causing a problem guess I'll wait until old AMD card is in & check all again. Would still like to know if the above referenced file C:\ESD\Windows\sources\install.esd can be used to run the DISM / restorehealth / source:esd command.

    thanks OldMike
      My Computers


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

    dogpark said:
    Guess I think do have another problem. Yesterday ran sfc/ scannow three times with restart in between each per Brink's suggestion but each time I get: (& note it indicates Repairs Complete?)
    Code:
    2016-02-06 17:10:42, Info                  CSI    000050dc [SR] Beginning Verify and Repair transaction2016-02-06 17:10:44, Info                  CSI    0000512c [SR] Verify complete
    2016-02-06 17:10:44, Info                  CSI    0000512d [SR] Repairing 1 components
    2016-02-06 17:10:44, Info                  CSI    0000512e [SR] Beginning Verify and Repair transaction
    2016-02-06 17:10:44, Info                  CSI    00005130 [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-02-06 17:10:44, Info                  CSI    00005133 [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-02-06 17:10:44, Info                  CSI    00005134 [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-02-06 17:10:44, Info                  CSI    00005137 [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-02-06 17:10:44, Info                  CSI    00005139 [SR] Repair complete
    2016-02-06 17:10:44, Info                  CSI    0000513a [SR] Committing transaction
    2016-02-06 17:10:44, Info                  CSI    0000513f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    Since it does not appear to be causing a problem guess I'll wait until old AMD card is in & check all again. Would still like to know if the above referenced file C:\ESD\Windows\sources\install.esd can be used to run the DISM / restorehealth / source:esd command.

    thanks OldMike
    The Tech Bench iso works a lot better Most use that iso.....their is a way to make yours work.....I'll have to look it up thou.
      My Computers


  9. Posts : 118
    Windows 10 Pro
       #178

    OldMike65 said:
    The Tech Bench iso works a lot better Most use that iso.....their is a way to make yours work.....I'll have to look it up thou.
    I have been brushing up on the TechBench ISO, reading both what you & Brink have posted. Was about to download the ISO when came across the C:\ESD file.
    :)
      My Computers


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

    dogpark said:
    I have been brushing up on the TechBench ISO, reading both what you & Brink have posted. Was about to download the ISO when came across the C:\ESD file.
    :)
    Much easier to do if you download the right ISO for your windows 10 from Tech Bench. The big difference is in the Install.wim file.....
      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 23:46.
Find Us




Windows 10 Forums