Wednesday, October 17, 2018

windows - DrUpdate.dll error in sfc /scannow



I have an issue with sfc /scannow. It finishes the verification process and informs me of errors there were unable to be fixed. I looked into CBS.log file and I found four entries related to drupdate.dll. As I understand, this is related with driver updates over windows update?
I'm running
Win 10 Pro x64.



AMD A6 5200




4GB DDR3 RAM



SATA 500GB HDD



This is a snippet of that error



2016-03-11 18:44:18, Info                  CSI    00003cfe@2016/3/11:17:44:18.431 Primitive installers committed for repair
2016-03-11 18:44:18, Info CSI 00003cff [SR] Verify complete
2016-03-11 18:44:18, Info CSI 00003d00 [SR] Verifying 100 (0x0000000000000064) components

2016-03-11 18:44:18, Info CSI 00003d01 [SR] Beginning Verify and Repair transaction
2016-03-11 18:44:23, Info CSI 00003d02 [SR] Cannot repair member file [l:12]"DrUpdate.dll" of Microsoft-Windows-ServicingStack, version 10.0.10586.113, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2016-03-11 18:44:24, Info CSI 00003d03@2016/3/11:17:44:24.310 Primitive installers committed for repair


I tried using dism /checkhealth (not the precise command, I don't know it from my head). What else can I do?



I tried asking MS support but they give me useless advice. The reason I used sfc /scannow is because KB3140768 Cumulative update fails to install. Also I tried manually replacing the drupdate.dlls that I have found and they were 1kb in size. I replaced them with the ones from the ISO image of Win 10 and still the same error occurs in sfc.


Answer



Download the Update KB3139907, use 7zip to extract the MSU. Now use expand.exe to extract the KB3139907.CAB:




expand -F:* C:\Windows10.0-KB3139907-x64.cab C:\Windows10.0-KB3139907-x64


Now run Dism /Online /Cleanup-Image /RestoreHealth /Source:C:\Windows10.0-KB3139907-x64 /LimitAccess to restore the Dll.


No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...