Help With About (4) SFC /Scannow Errors Windows 7 Pro 64-bit SP1

Page 1 of 4 123 ... LastLast

  1. Posts : 18
    Window 7 Professional 64-Bit
       #1

    Help With About (4) SFC /Scannow Errors Windows 7 Pro 64-bit SP1


    This is my 1st post on this forum, so I'll try to be concise, and not break any forum rules (unintentionally).
    I'm having some trouble in obtaining a "clean" SFC that will complete 100% with no errors. I recently had the somewhat common "telemetry" error files. Fortunately, I was able to fix those, but not by the recommended fix of uninstalling KB3022345 and KB3068708. These did not solve that problem. I ran across the (2) SFCFix Files by Niemiro (1) SFCFix.exe and (1) SFCFix9winzip.txt that I downloaded and posted to my desktop. I dragged the Winzip file on top of the SFCFix.exe, and a new SFCFix.txt file was created with text results of the fix (successful). I ran SFC /scannow, again, and sure enough, the "telemetry error files" were all gone.

    Now, I'm still left my problem of about (2) or (3) repeated errors that seem to be non-critical...they don't seem to have any adverse effects, whatsoever that I've been able to detect, but I would still like to fix these without making it too big a deal, if possible (like replacing Windows Manifest or Package files, etc. from another source, although I do have a couple of earlier USB backup images of my harddrive). Since these errors are minimal, I thought I'd just post them here, without the entire CBS log file, for the time being...see if someone can help me solve this.

    (1) CSI 00000059 [SR] Cannot verify component files for eda0994a5dcb3a3451128b283ebaf43d, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)


    (2) CSI 0000036b [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch


    These same 2 errors are repeated at the bottom of the CBS log, but are the same errors. I've done the usual stuff (chkdsk /F /R) etc., and I've tried to find out exactly "what" these errors refer to? All I can think of was a sudden power "shutdown" about 3 weeks, ago (most likely due to a overheating problem at bottom of the notebook....HP notebooks are notorious for this....very reason I had bought a cooler pad for mine (which, unfortunately, I had not been using at the time). Anyway, if someone has some definite fixes and idea for these (2) errors, I would be grateful.......I've seen these errors referred to in several other posts, but I've yet to read a solution......thanks, Sy
      My Computer


  2. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #2

    Oops......The 2nd File error "unified-Telemetry-Client" has been fixed! I posted the wrong 2nd file.
    Sorry.....Sy, I will check my latest log file, and repost.
      My Computer


  3. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #3

    Here is the SFC 2nd error file that I spoke of in my original post, above:


    (2) CSI 00000208 [SR] Cannot repair member file [l:36{18}]"Amd64\HPZSCWN7.DTD" of prnhp002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
      My Computer


  4. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #4

    According to some searching - C:\Windows\inf\prnhp002.inf. The specific entry is: "HP LaserJet 4200/4300 PCL6"

    Do you have an issue with the printer? What led you to a sfc scan in the first place?
      My Computer


  5. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #5

    NO....I don't have any printer problems at all. I use a wireless setup to a Brothers printer that works great.
    I do such things as a SFC scan periodically, just as a part of routine maintenance. As I said in my original post, the notebook works just fine, and I have not experienced any problems in any area, although those errors showed up in the SFC......I'm just curious as to precisely what program they point to plus I'd like to have a 100% "clean" scan, again....I've never installed a HP printer, so that's very interesting. Any further ideas about how to determine what the errors point to, and simple way to resolve?

    The only reason that I'm a little reluctant to do a "system restore" back about a month, ORto do a complete image restore from an external USB hard drive NTI backup that I did about a month, ago is because I've made a bunch of small changes, since then...things like adding Cyberlink PowerDVD 15, a very customized Opera browser, many many megabytes of Windows updates, etc...I still have those options, if I can't find a ready solution....Interesting that I've seen those (2) exact SFC errors mentioned in several forums, yet no one seems to really have a clue as to where they point......simply replies for requests to post the CBS log file.

    Thanks for taking the time to reply...I do appreciate.
      My Computer


  6. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #6

    Yes, I will ask you to post the CBS.log file as well So, I can in turn ask our SFC/CBS analysis expert to check it out.
    Step 4 of - Windows Update Posting Instructions

    If CBS.zip file is larger than 8MB, you can delete the older CBS persist files from the zip.
      My Computer


  7. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #7

    I'm running a 'new' scan right now. I forgot to mention that I also ran SURT twice....once as the "stand slone version" which I had downloaded, and also ran the online version....no effect on the errors.

    I use this little program in my command prompt, when I run a SFC. It renders a very nice. easy to read text file, immediately upon completion of the scan:

    @echo off
    rem delete old files
    del /q %windir%\logs\cbs\cbs.log
    del /q c:\sfcdetails.txt
    rem run sfc
    sfc /scannow
    rem filter out non essential junk from the cbs.log
    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt
    rem open details in notepad
    notepad c:\sfcdetails.txt
    rem optional command to shut down & restart pc after running. this may be needed if
    rem sfc replaces some critical files. uncomment (remove the 'rem') to activate.
    rem shutdown -r
    exit

    I like because it posts the results in very easy to read text, immediately on the desktop.
    I will send you the latest result upon completion of the scan..............
      My Computer


  8. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #8

    Here is the nice text version of the latest scan that I just ran and completed.
    I think you are right.....(1) of the errors has something to do with a printer
    (or driver update)....Interestingly, my Brother printer still works just fine.
      My Computer


  9. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #9

    This doesn't show us anything we don't know yet. I would have asked for this file otherwise :)

    Please attach the file requested. There are more detail in the CBS logs that we can't see here.
      My Computer


  10. Posts : 18
    Window 7 Professional 64-Bit
    Thread Starter
       #10

    Here you go
    Help With About (4) SFC /Scannow Errors  Windows 7 Pro 64-bit SP1 Attached Files
      My Computer


 
Page 1 of 4 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 08:21.
Find Us