Windows 10: SFC failed to repair corrupted file

Hello,

I'm not a computer enthusiast. I periodically run sfc, dism and chkdsk to keep my operating system in working condition. Just today when I ran sfc via an elevated command prompt window it found some corrupted files but was unable to fix. I ran chkdsk and dism and everything's fine in both of them.

Using findstr command I was able to replicate the corrupted file - > C:\WINDOWS\System32\ml-in\ml-in\TransliterationComponentLayouts.dgml

I tried running sfc from safemode but still got the same issue.



Windows 10 Pro 16299.334 64 bit

Antivirus - > Bitdefender Total Security 2018 22.0.19.242 64 bit

Windows Defender for the periodic scanning

Office 365 - 1802 64 bit

Language packs installed -> English (India), English (United Kingdom), English (US), Malayalam



Any help would be appreciated

The logs will be attached to the post

Thankyou *Smile

:)

 

SFC Failed to repair corrupt files

Did you run dism to repair the problems? What was the underlying issue that prompted you to run SFC?

Please run a system file check (SFC) & DISM if you are on win 7 or higher



All instructions are in our Wiki article below...Should you have any questions please ask us.
System file check (SFC) Scan and Repair System Files & DISM to fix things
SFC cannot

 

SFC Failed to repair corrupt files

I have run a SFC scan and it found corrupt files but failed to repair files. This is the log file details are

here.

 

Hi and welcome to Tenforums.
This is the problem? The SFC log says it was repaired.
Code: C:\WINDOWS\System32\ml-in\ml-in\TransliterationComponentLayouts.dgml[/quote] (Appears to have something to do with Visual Studio)
Have you checked if the folder even exists on the computer?

Which DISM command(s) have you run?

Dism /Online /Cleanup-Image /checkhealth
Dism /Online /Cleanup-Image /scanhealth
Dism /Online /Cleanup-Image /restorehealth
then, again:
sfc /scannow

 

(Appears to have something to do with Visual Studio)
Have you checked if the folder even exists on the computer?

Which DISM command(s) have you run?

Dism /Online /Cleanup-Image /checkhealth
Dism /Online /Cleanup-Image /scanhealth
Dism /Online /Cleanup-Image /restorehealth
then, again:
sfc /scannow[/quote] Hi,

Thanks for the welcome *Smile

To answer the question, yes that's the error I got from the CBS log after running the "findstr" command. I couldn't upload the CBS log as its too big to be attached here.

I wonder if it had something to do with Office 365 updating to the new version - 1802. I tried a previous system image before the update. Ran SFC and it found no problems. Office got updated to 1802 and there it is again.I do have a Malayalam language pack for Office. Wonder if the "ml-in" refers to it.

I checked the directory and yes I do have that folder.





I ran two dism commands back to back :

Dism /Online /Cleanup-Image /checkhealth
Dism /Online /Cleanup-Image /scanhealth

Didn't bother with restoring the component store since scanning it didn't find any integrity violations. I ran another SFC command after running the DISM commands.

I'm at work now. I'll make another system image then try running the DISM command to restore the component store first thing tonight or tomorrow.

Thank you for taking the time to reply *Smile

 

Right. We don't need the whole CBS log anyway, just the text file you posted is fine.

Appears the ml-in refers to the language pack. Perhaps remove the language pack, update Office and reinstall the language pack? If you can identify the language pack as the problem, you'll want to report that in the Feedback hub.

No problem. Let us know how it goes.