Windows 10 TH2 and Intel Graphics Driver file corruptions

Discussion in 'Windows 10' started by gnugeek, Nov 19, 2015.

  1. gnugeek

    gnugeek MDL Member

    Nov 23, 2009
    171
    41
    10
    #1 gnugeek, Nov 19, 2015
    Last edited by a moderator: Apr 20, 2017
    I have Intel NUC D34010WYKH on Windows 10 PRO TH2 X64 on fresh install from a bootable USB. The ISO was downloaded from Microsoft directly.

    I ran SFC once Windows booted up after initial "Lets Start" message. No errors.

    Then Intel WHQL official Driver got installed through Windows Update. Then I run SFC, I get corruption errors. I ran command with mounted TH2 ISO and it even said that it was able to fix the errors.
    With ISO Media in CD/DVD tray: (The same media you installed image with) Type in ADMIN Cmd Prompt
    Code:
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:M:\sources\install.wim:1 /limitaccess
    Where M is the drive

    But then after a reboot, SFC /scannow still throws up some errors. They just are unfixable even if I completely uninstall the display driver and unplug LAN cable.

    Then I used Microsoft's autohide tool to hide the driver update and disabled it from "device installation settings" found by right clicking on your PC in Old Control Panel's Devices and Printers.

    So again a fresh install. But as soon as it connects to internet, it downloads and installs the Intel's display driver blatantly ignoring my settings. Again file corruption. I want to block this driver so badly. My ISO is not corrupt as my main PC with Nvidia graphics is perfectly fine.

    Am I missing anything? Why Microsoft has to be hands up our arse all the time?
     
  2. odiebugs1

    odiebugs1 MDL Expert

    Jul 30, 2015
    1,390
    458
    60
    #2 odiebugs1, Nov 19, 2015
    Last edited: Nov 19, 2015
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,991
    23,072
    340
    #3 Enthousiast, Nov 19, 2015
    Last edited by a moderator: Apr 20, 2017
    Did you check what errors sfc found? Maybe if you publish them someone could help you.

    After sfc /scannow run: "findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt" and check your desktop.


    My system runs 10240 from the pre rtm release, it's upgraded last week to 10586 via WU and i also have onboard intel graphics (i7 3770) and i've got this result:

    SFC /VERIFYONLY:
    Code:
    2015-11-19 18:16:01, Info                  CSI    00003cde [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
    2015-11-19 18:16:02, Info                  CSI    00003ce8 [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
    2015-11-19 18:16:02, Info                  CSI    00003ce9 [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"
    2015-11-19 18:16:02, Info                  CSI    00003cec [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2015-11-19 18:16:04, Info                  CSI    00003d53 [SR] Verify complete
    
     
  4. gnugeek

    gnugeek MDL Member

    Nov 23, 2009
    171
    41
    10
    #4 gnugeek, Nov 19, 2015
    Last edited: Nov 19, 2015
    (OP)
    The WU driver is older one 10.18.15.4256 and newest off Intel's site gives me version 15.40.10.4300.

    Both cause corruption.

    I ran sfc /scannow multiple times after that dism command. Still the same error.
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,991
    23,072
    340
    #5 Enthousiast, Nov 19, 2015
    Last edited: Nov 19, 2015
    Did you use the findstring ("findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt") i gave to see what exactly is corrupted?
     
  6. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,544
    5,051
    210
    You need to uninstall that driver with Minitools in my sig, then hide you when it shows up again, then run DISM repair again if needed:D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. dasag

    dasag MDL Junior Member

    Mar 9, 2014
    63
    8
    0
    I have the same problem.

    I ran the Intel(R) Driver Update Utility says version 15.40.10.4300 is the latest.

    I Installed version 15.40.10.4300 but version 10.18.15.4256 is still showing in Device Manager.

    Then I ran WU and it's wanting to update the driver. Whats going on.?
     
  8. gnugeek

    gnugeek MDL Member

    Nov 23, 2009
    171
    41
    10
    #8 gnugeek, Nov 20, 2015
    Last edited: Nov 20, 2015
    (OP)
    1. Uninstall and 4256 driver from device manager. When it asks select Delete driver files option.
    2. Update driver to 4300
    3. Run the dism command with mounted iso of same Windows 10 build
    4. Reboot
    5. In Admin Command prompt, run sfc /scannow It should find errors and fix them.
    6. Reboo
    7. Keep on repeating step 5 and 6 till your system is error free.

    Bonus tip. I created a custom WIM of 10586 build which had KB3118754 integrated as my existing pc was having the same KB installed.

    Thanks. This is now solved.

    But once Intel releases new Graphics driver on WU, it will ignore my block settings overwrite the existing driver and again cause corruption.

    These poor decisions of Microsoft is causing them to bleed customers. They are trying to emulate Apple but they are making things worse for themselves and power users.
     
  9. dsbig

    dsbig MDL Senior Member

    Aug 3, 2009
    258
    25
    10
    #9 dsbig, Nov 20, 2015
    Last edited: Nov 20, 2015
    its because it comparing your latest intel driver to the one included with windows 10. and its not matching.




    nothing is wrong with your system.

    microsoft needs to fix this. so people stop complaining about the same file.

    no offence to op.


    it shows up for intel/amd/nvidia.
     
  10. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,544
    5,051
    210
    #10 lobo11, Nov 20, 2015
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Ache

    Ache MDL Novice

    Dec 27, 2011
    21
    5
    0
    #11 Ache, Nov 22, 2015
    Last edited: Nov 22, 2015
    The correct fix will be to remove wrongly installed Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 update (RemoteFX Display driver which contains opencl.dll with reduced functionality, which overwrites correct Nvidia/Intel/ATI \SysWoW64\opencl.dll on attempt of DISM recover from install.wim) from WinSxS (which is 32bit counterpart of their amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7 64bit update, later one is inactive and does no harm). But I know no tool for correct selective remove of specific directory from WinSxS. Manual removing this directory damages internal structures, I already try that.
     
  12. wmn

    wmn MDL Novice

    Feb 24, 2010
    11
    1
    0
    #12 wmn, Dec 1, 2015
    Last edited: Dec 1, 2015
    This bug exist on all Windows 10 version since a long time (official release at least) and also on Server 2016 preview releases..

    To fix it (win x64):

    1) After installing Windows, do not allow any video drivers installation (manually or via Windows Update).

    2) Do a sfc /scannow to be shure that there is no files corruption etc.

    3) Go to security tab and take ownership of the opencl.dll in the Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.(build number)... folder. (You must be at Administrator level)

    4) Remove write permission from System, Administrators and any account that have it.

    5) Now you can install video drivers, and sfc /scannow should not report any file corruptions.


    I think that Microsoft should be blamed for this f***up.