Both sfc/startup repair cannot fix corruption - credui.dll

[NoelDP]

I've uploaded a file - 828ad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder 828ad in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests
(overwrite if necessary)

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[Matrix828]

Thank you for your help in this matter.
Attached.

 

[NoelDP]

You have problems
There are now more errors appearing.
If I remove the ones that we already knew about, here's what we get...

Checking Component Store
(f) CSI Payload File Missing 0x00000000 DWrite.dll.mui amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_it-it_6d6b27713a307bae 
(f) CSI Payload File Missing 0x00000000 DWrite.dll.mui x86_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_it-it_114c8bed81d30a78 
(f) CSI Payload File Missing 0x00000000 FntCache.dll.mui amd64_microsoft-windows-d..fontcache.resources_31bf3856ad364e35_7.1.7601.16492_it-it_acc694affd2f0026 
(f) CSI Manifest Missing 0x00000002 amd64_wiabr004.inf_31bf3856ad364e35_6.1.7600.16385_none_07dc391f98b960bb.manifest amd64_wiabr004.inf_31bf3856ad364e35_6.1.7600.16385_none_07dc391f98b960bb 
(fix) CSI Manifest Missing CSI File Replaced File: amd64_wiabr004.inf_31bf3856ad364e35_6.1.7600.16385_none_07dc391f98b960bb.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-rtm-client-neutral-amd64.cab
(f) CSI Manifest Missing 0x00000002 winsxs\Manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16476_none_cd31ac6ff1344730.manifest x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16476_none_cd31ac6ff1344730 
(fix) CSI Manifest Missing CSI File Replaced File: x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16476_none_cd31ac6ff1344730.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-ie9gdr-servicing-x64-20aug13.cab
(f) CSI Payload File Missing 0x00000000 FntCache.dll.mui amd64_microsoft-windows-d..fontcache.resources_31bf3856ad364e35_7.1.7601.16492_fr-fr_c29e9e6925fd1aa8 
(f) CSI Payload File Missing 0x00000000 DWrite.dll.mui amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_fr-fr_8343312a62fe9630 
(f) CSI Payload File Missing 0x00000000 DWrite.dll.mui x86_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_fr-fr_272495a6aaa124fa 
(f) CSI Manifest Missing 0x00000002 amd64_wiabr004.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b7f73fef29875704.manifest amd64_wiabr004.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b7f73fef29875704 
(fix) CSI Manifest Missing CSI File Replaced File: amd64_wiabr004.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b7f73fef29875704.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest Missing 0x00000002 amd64_wiabr004.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4fdc831e7ae5b86d.manifest amd64_wiabr004.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4fdc831e7ae5b86d 
(fix) CSI Manifest Missing CSI File Replaced File: amd64_wiabr004.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4fdc831e7ae5b86d.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Manifest Missing 0x00000002 amd64_wiabr005.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b94b7905f521b95b.manifest amd64_wiabr005.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b94b7905f521b95b 
(fix) CSI Manifest Missing CSI File Replaced File: amd64_wiabr005.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b94b7905f521b95b.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab
(f) CSI Payload File Missing 0x00000000 DWrite.dll.mui amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_ru-ru_29e175fbc10a89d0 
(fix) CSI Payload File Missing CSI File Replaced File: DWrite.dll.mui From: C:\Windows\winsxs\x86_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.1.7601.16492_ru-ru_cdc2da7808ad189a\DWrite.dll.mui
(f) CSI Payload File Missing 0x00000000 mshtmler.dll amd64_microsoft-windows-ie-htmleditingsupport_31bf3856ad364e35_8.0.7600.16385_none_6a1cbf5f4ad99b65 
(f) CSI Payload File Missing 0x00000000 VGX.dll x86_microsoft-windows-ie-vgx_31bf3856ad364e35_9.4.8112.20593_none_05f6a2141c55df06

This tends to imply that you have either got malware problems, or disk problems...


Please run a full CHKDSK scan....
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.

You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, and then reboot.
The chkdsk will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

Look for the results in the Event Viewer's Windows Logs - Application events, under the Source 'Wininit' They should be there - copy and paste the results to your reply.

 

[Matrix828]

I will have to get those results back to you tomorrow.

I am pretty certain there's some bad sectors on my drive but I am planning on getting an SSD in the not-so-distant future (week or so, depending on how much space I can free up so it'll fit and how long that will take).
I'm probably just going to clone the entire drive over, so should we wait until that has happened and then continue trying to fix those problems?

 

[NoelDP]

Your first priority must be to back up your data to external media - your drive may be on a slippery slope with a cliff it'll go over tomorrow!
Once that's done we can worry about the OS and other stuff.

 

[Matrix828]

I'm already in the process of creating a system image on an external drive, using Acronis.. Lets hope the bad sectors wont mess anything up.

 

[NoelDP]

<crosses fingers>

 

[Matrix828]

I hope I have posted what you are asking for.
It seems to be cut off unexpectedly, but I found another chkdsk report from 14/3/14 that seemed a lot more complete ("Old Report.txt") so have attached them both below.

 

[NoelDP]

Your hard drive is DEFINITELY failing, back up your data to external media NOW - before it dies completely (If you haven't already).

 

[Matrix828]

I have made a full backup using Macrium Reflect due to Acronis freezing every time I start it up.
I have also ordered a SSD so that should be here in a few days. Could you recommend a good drive cloning program so I can just transfer everything in one go?

 

[NoelDP]

Last time I cloned my drive, I used a straight filecopy - XCOPY with appropriate switches.
It took ages, but I ended up with a perfect copy.

Your problem though, is that you have severe disk problems, and that's likely to mean headaches in any serious copy process.

I really would recommend a clean install - you're very likely to need to do a repair install immediately afterwards anyhow.

 

[Matrix828]

Damn, I was really hoping I wouldn't have to resort to that
I have had a look at the tutorials available on this site for repair installs, and either I didn't read it properly or it didn't state it, but is there a way to do it and also keep things like installed programs and user accounts intact, so its like almost new, but with all my stuff on it?

 

[Britton30]

Repair install, Image, or Clone will keep everything you now have, including possibly corrupt system files.

 

[Matrix828]

I have spent the best part of today isntalling the new SSD due to hiccups constantly appearing during cloning the old hdd over.
I managed to do it and i am using the cloned system now (blazingly fast, may I add).
Attached is a new sfcdetails, a quick look showed only a couple of corrupt files. (if I'm reading it right)

 

[NoelDP]

I'd *much* rather see the full CBS.log file - the extracted SFC log gives very limited detail

Here's the first few lines of the summary from the SFC log...

2014-03-23 21:11:03, Info                  CSI    00000345 [SR] Repairing 9 components
2014-03-23 21:11:03, Info                  CSI    00000346 [SR] Beginning Verify and Repair transaction
2014-03-23 21:11:03, Info                  CSI    00000347 [SR] Cannot repair member file [l:32{16}]"FntCache.dll.mui" of Microsoft-Windows-DirectWrite-FontCache.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"it-IT", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    00000348 [SR] Cannot repair member file [l:32{16}]"FntCache.dll.mui" of Microsoft-Windows-DirectWrite-FontCache.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"fr-FR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    00000349 [SR] Cannot repair member file [l:28{14}]"DWrite.dll.mui" of Microsoft-Windows-DirectWrite.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"it-IT", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    0000034a [SR] Cannot repair member file [l:28{14}]"DWrite.dll.mui" of Microsoft-Windows-DirectWrite.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"fr-FR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    0000034b [SR] Cannot repair member file [l:28{14}]"DWrite.dll.mui" of Microsoft-Windows-DirectWrite.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"it-IT", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    0000034c [SR] Cannot repair member file [l:28{14}]"DWrite.dll.mui" of Microsoft-Windows-DirectWrite.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"fr-FR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-03-23 21:11:03, Info                  CSI    0000034d [SR] Cannot verify component files for Microsoft.VC80.MFCLOC, Version = 8.0.50727.4027, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2014-03-23 21:11:03, Info                  CSI    0000034e [SR] Cannot verify component files for Microsoft.VC80.MFC, Version = 8.0.50727.4027, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2014-03-23 21:11:03, Info                  CSI    0000034f [SR] Cannot repair member file [l:32{16}]"FntCache.dll.mui" of Microsoft-Windows-DirectWrite-FontCache.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"fr-FR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

Please note that however much I want to try and fix this, my chances of a full fix are limited by the system history, and as a consequence, you may be better off doing at least a repair install.

I'll post a fix protocol later.