jnelsoninjax Posted May 9, 2017 Share Posted May 9, 2017 From the log: 2017-05-06 20:15:25, Info CSI 00005481 [SR] Repairing 2 components 2017-05-06 20:15:25, Info CSI 00005482 [SR] Beginning Verify and Repair transaction 2017-05-06 20:15:26, Info CSI 00005484 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\imageres.dll from store 2017-05-06 20:15:26, Info CSI 00005488 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\imageres.dll from store 2017-05-06 20:15:27, Info CSI 0000548b [SR] Repair complete 2017-05-06 20:15:27, Info CSI 0000548c [SR] Committing transaction 2017-05-06 20:15:27, Info CSI 00005490 [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation. 2017-05-06 20:15:27, Info CSI 00005491 [SR] Repairing 2 components 2017-05-06 20:15:27, Info CSI 00005492 [SR] Beginning Verify and Repair transaction 2017-05-06 20:15:27, Info CSI 00005494 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\imageres.dll from store 2017-05-06 20:15:28, Info CSI 00005498 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\imageres.dll from store 2017-05-06 20:15:28, Info CSI 0000549b [SR] Repair complete I have run SFC 3 times now and these 2 files keep showing up. Should I be concerned about them? i have rebooted between scans.s Link to comment Share on other sites More sharing options...
JustGeorge Posted May 9, 2017 Share Posted May 9, 2017 (edited) Try running DISM, then SFC: Dism /Online /Cleanup-Image /RestoreHealth Link to comment Share on other sites More sharing options...
jnelsoninjax Posted May 9, 2017 Author Share Posted May 9, 2017 45 minutes ago, slamfire92 said: Try running DISM, then SFC: Dism /Online /Cleanup-Image /RestoreHealth Did that as well... Link to comment Share on other sites More sharing options...
xendrome Posted May 9, 2017 Share Posted May 9, 2017 I believe there is an issue with DISM and SFC in the creators update. Something to do with the repair database entries. I did some googling on this a few days ago and it hasn't been fixed/addressed yet by MS, so this may be something that is throwing a false flag. Link to comment Share on other sites More sharing options...
+Warwagon MVC Posted May 9, 2017 MVC Share Posted May 9, 2017 What is the SHA1 hash of your imageres.dll file Mine is C054D6F5B250E3287D31AE7367067073798BD976 Link to comment Share on other sites More sharing options...
jnelsoninjax Posted May 9, 2017 Author Share Posted May 9, 2017 1 hour ago, warwagon said: What is the SHA1 hash of your imageres.dll file Mine is C054D6F5B250E3287D31AE7367067073798BD976 OK, the SHA1 for the file in syswow64 matches with yours, so I guess that it's not corrupt? Link to comment Share on other sites More sharing options...
Appzalien Posted May 10, 2017 Share Posted May 10, 2017 Have you tried running sfc from Safe mode with command prompt? Sometimes things cannot be repaired if they are busied by the system. It couldn't hurt. Also when I run sfc scannow I always choose run as administrator when I right click on the command prompt link. I suppose your doing that as well. Link to comment Share on other sites More sharing options...
+Warwagon MVC Posted May 10, 2017 MVC Share Posted May 10, 2017 10 hours ago, jnelsoninjax said: OK, the SHA1 for the file in syswow64 matches with yours, so I guess that it's not corrupt? Well, I guess in that sense it doesn't appear to be.. Link to comment Share on other sites More sharing options...
Shiranui Posted May 10, 2017 Share Posted May 10, 2017 11 hours ago, xendrome said: I believe there is an issue with DISM and SFC in the creators update. Something to do with the repair database entries. I did some googling on this a few days ago and it hasn't been fixed/addressed yet by MS, so this may be something that is throwing a false flag. Yes. Only DISM fails around 98%. Link to comment Share on other sites More sharing options...
Mando Posted May 13, 2017 Share Posted May 13, 2017 On 5/9/2017 at 1:25 PM, jnelsoninjax said: From the log: 2017-05-06 20:15:25, Info CSI 00005481 [SR] Repairing 2 components 2017-05-06 20:15:25, Info CSI 00005482 [SR] Beginning Verify and Repair transaction 2017-05-06 20:15:26, Info CSI 00005484 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\imageres.dll from store 2017-05-06 20:15:26, Info CSI 00005488 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\imageres.dll from store 2017-05-06 20:15:27, Info CSI 0000548b [SR] Repair complete 2017-05-06 20:15:27, Info CSI 0000548c [SR] Committing transaction 2017-05-06 20:15:27, Info CSI 00005490 [SR] Unable to complete Verify and Repair transaction because some of the files that need to be repaired are in use. A reboot is required to complete this operation. 2017-05-06 20:15:27, Info CSI 00005491 [SR] Repairing 2 components 2017-05-06 20:15:27, Info CSI 00005492 [SR] Beginning Verify and Repair transaction 2017-05-06 20:15:27, Info CSI 00005494 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\imageres.dll from store 2017-05-06 20:15:28, Info CSI 00005498 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\imageres.dll from store 2017-05-06 20:15:28, Info CSI 0000549b [SR] Repair complete I have run SFC 3 times now and these 2 files keep showing up. Should I be concerned about them? i have rebooted between scans.s Nothing at all to worry about, MS have scored an Own goal yet again. its a false positive issue. Link to comment Share on other sites More sharing options...
Recommended Posts