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

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #11

    Here's everything but the VC++ 2005 files....


    I've uploaded a file - 828aa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\828aa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\828aa
    or
    DIR E:\828aa



    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



    XCOPY <drive>:\828aa <drive>:\windows\winsxs /y /i /s /v /h



    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply
      My Computer


  2. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #12

    I have done as you have said; logs attached.
    Both sfc/startup repair cannot fix corruption - credui.dll Attached Files
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #13

    I seem to have missed one file - apart from the manifests we know about.
    I'll deal with that one tomorrow...
    Code:
    2014-03-10 00:10:44, Info                  CSI    00000331 [SR] Repairing 6 components
    2014-03-10 00:10:44, Info                  CSI    00000332 [SR] Beginning Verify and Repair transaction
    2014-03-10 00:10:44, Info                  CSI    00000333 [SR] Cannot repair member file [l:50{25}]"Windows Critical Stop.wav" of Microsoft-Windows-Shell-Sounds, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
    2014-03-10 00:10:44, Info                  CSI    00000334 [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-10 00:10:44, Info                  CSI    00000335 [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)
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #14

    Still hunting for the VC files

    Lets get the final one of the others sorted...


    I've uploaded a file - 828ab.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\828ab
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\828ab
    or
    DIR E:\828ab



    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



    XCOPY <drive>:\828ab <drive>:\windows\winsxs /y /i /s /v /h



    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply
      My Computer


  5. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #15

    Since my last post (and reboot) I finally have access to chrome without using "old_chrome.exe", and whocrashed opens without error! You people here are brilliant, thank you so much for the help!!

    I have attached the new sfcdetails.txt, lets hope there aren't many more files to replace now.

    I am also getting a new error - "wermgr.exe Application Error" - I have googled it and people said to either disable the Windows Error Reporting service or just delete the file from system32. Should I attempt to pull a working one from an installation disc and replace it?

    A thousand thanks to you, Noel :)
    Both sfc/startup repair cannot fix corruption - credui.dll Attached Files
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #16

    Just the two VC++ files to deal with now - I have a team hunting for them :)

    We've got the source update - but it's a case of knowing the proper procedures for extraction and renaming - which I don't. If I have to, I'll create a new machine to install the update into and then pull the files from that (but that's going to mean about 5 hours work!)

    Back when I've found the files....

    Here's the summary output from your last scan..
    Code:
    2014-03-10 17:25:11, Info                  CSI    00000326 [SR] Repairing 3 components
    2014-03-10 17:25:11, Info                  CSI    00000327 [SR] Beginning Verify and Repair transaction
    2014-03-10 17:25:11, Info                  CSI    00000328 [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-10 17:25:11, Info                  CSI    00000329 [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-10 17:25:11, Info                  CSI    0000032a [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\Media"\[l:50{25}]"Windows Critical Stop.wav" from store
    2014-03-10 17:25:11, Info                  CSI    0000032c [SR] Repair complete
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #17

    With luck this will work :)


    I've uploaded a file - 828ac.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 828ac 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

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

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


  8. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #18

    Here you go, Noel.
    Both sfc/startup repair cannot fix corruption - credui.dll Attached Files
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #19

    OUCH!
    looks like I may have goofed with those two files

    They seem either to be wrong, or to have highlighted other problems...

    Here's the edited highlights of the CheckSUR log

    Code:
    Checking Component Store
    (f) CSI Manifest Missing 0x00000002 x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_cbeeb6564710a1d1.manifest x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_cbeeb6564710a1d1 
    (w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_cbeeb6564710a1d1.manifest x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_cbeeb6564710a1d1 
    (f) CSI Manifest Missing 0x00000002 x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_03c6f934205fcb15.manifest x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_03c6f934205fcb15 
    (w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_03c6f934205fcb15.manifest x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_03c6f934205fcb15 
    (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 
     
    Unavailable repair files:
     winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_cbeeb6564710a1d1.manifest
     winsxs\manifests\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4027_none_03c6f934205fcb15.manifest
    This means that either I got the files wrong, or you have other problems as well.
    In view of the difficulties with VC files in general, I think that the problem lies with me.

    I'll have to review and come back to you.
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #20

    I *think* I may have the source of the problem - an excess line-feed!

    I'll upload new copies of the files in a few minutes
      My Computer


 
Page 2 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:00.
Find Us