How to understand this SFCdetails.txt

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #11

    Hi NoelDP,

    Don't worry. just FYI

    I double check the packages you sent me and for instances for this:

    Code:
     servicing\packages\Package_32_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
    you gave me these files below:

    Code:
    package_32_for_kb3011780_bf~31bf3856ad364e35~x86~~6.1.1.5
    package_for_kb3011780_sp1~31bf3856ad364e35~x86~~6.1.1.5
    package_for_kb3011780~31bf3856ad364e35~x86~~6.1.1.5
    I'm not an expert in this matter, but I'll take a guess that the names are mismatching (e.g - the first one has an extra _bf).

    And for this one:

    Code:
    servicing\packages\Package_74_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.mum
    There is no file on the .zip you sent me.

    Again don't worry, I'll wait for you fix, and thank you once more for your time. :)
      My Computer


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

    I've uploaded a file - dpsab.zip - to my OneDrive at https://onedrive.live.com/?cid=93673...FCEB92F%211007
    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 dpsab in the same place.
    Open this folder - there should be one folders inside it (Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages


    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


  3. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #13

    Hi NoelDP,

    thanks for sending me the fix so quickly, I did again the steps above, but still 2 packages to fix.

    because you gave me AMD packages. I've attached the CheckSUR logs

    Thanks, once more for your patient :)
    How to understand this  SFCdetails.txt Attached Files
      My Computer


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

    Not enough caffeine!
    Code:
    Unavailable repair files:
    	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
    	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.mum
    	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
    	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.cat

    new file - dpsac.zip - same procedure.
      My Computer


  5. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #15

    Hi NoelDP,

    as usual here I've attached the checkSUR logs (this time no errors :) )

    so I decided to run the
    Code:
     SFC /scannow
    but still giving me errors, so I've attached the SFCdetails.txt

    hope you can help me pn this one too :)
    How to understand this  SFCdetails.txt Attached Files
      My Computer


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

    OK - here's the error-list
    Code:
    	Line 292: 2015-07-19 16:38:18, Info                  CSI    000001ee [SR] Repairing 4 components
    	Line 293: 2015-07-19 16:38:18, Info                  CSI    000001ef [SR] Beginning Verify and Repair transaction
    	Line 294: 2015-07-19 16:38:18, Info                  CSI    000001f1 [SR] Cannot repair member file [l:32{16}]"IEExecRemote.dll" of IEExecRemote, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    	Line 295: 2015-07-19 16:38:18, Info                  CSI    000001f3 [SR] Cannot repair member file [l:54{27}]"OxpsConverter.Resources.dll" of OxpsConverter.Resources, Version = 6.1.7601.17932, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    	Line 296: 2015-07-19 16:38:18, Info                  CSI    000001f5 [SR] Cannot repair member file [l:24{12}]"WUDFHost.exe" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    	Line 297: 2015-07-19 16:38:18, Info                  CSI    000001f7 [SR] Cannot repair member file [l:56{28}]"Windows Navigation Start.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.17377, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    I'll post a fix protocol for those when I can!
      My Computer


  7. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #17

    Thank you NoelDP, I'll wait :)
      My Computer


  8. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #18

    bump this :)
      My Computer


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

    Sorry about that - 12-hour days and a cold don't lead to much coherent thought!

    I've still not been able to find the last file, but I think I have a workaround for that

    Let's fix the others in the meantime...

    I've uploaded a file - dpsad.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:\dpsad
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\dpsad
    or
    DIR E:\dpsad

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

    XCOPY <drive>:\dpsad <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


  10. Posts : 12
    Windows 7 Pro x64 SP1
    Thread Starter
       #20

    HI NoelDP,

    just followed every step, here is my CBS.log and just in case sfcdetails.txt

    I'm not quiet sure if it registered something to checksur logs this time and my sfcdetails looks the same as my previous that I posted here.
    How to understand this  SFCdetails.txt Attached Files
      My Computer


 
Page 2 of 3 FirstFirst 123 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:54.
Find Us