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

[symosk]

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

 

[symosk]

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.

 

[symosk]

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

 

[GokAy]

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?

 

[symosk]

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.

 

[GokAy]

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 - http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

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

 

[symosk]

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..............

 

[symosk]

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.

 

[GokAy]

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.

 

[symosk]

Here you go

 

[GokAy]

PM sent, expect a reply from NoelDP. He is usually very busy, so it may take a day or two.

 

[NoelDP]

Hah! ye of little faith
Here's the CheckSUR error...

Unavailable repair files:
	servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat

...and here's the SFC errors...

	Line 3683: 2015-09-19 07:52:26, Info                  CSI    00000368 [SR] Beginning Verify and Repair transaction
	Line 3688: 2015-09-19 07:52:26, Info                  CSI    0000036b [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)
	Line 3691: 2015-09-19 07:52:27, Info                  CSI    0000036d [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

It's unusual for a Manifest file to show an error in SFC without it appearing in CheckSUR also - but I see this CheckSUR is a couple of days old, so may be a little out of date.
I'll post a fix for the CheckSUR problems first, as they may have a bearing on the SFC.

Back soon.

 

[NoelDP]

I've uploaded a file - smkaa.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 smkaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

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

And 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.

 

[symosk]

Noel......Many Thanks.
I followed your instructions and just finished running the SURT, again (hotfix).
I'm attaching the CheckSur and the CheckSur Persist files.

Sy

 

[NoelDP]

Good - that fixed the mum/cat file error (although there's still no mention of the problem Manifest file )

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

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

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

 

[symosk]

I just ran a new SFC /scannow.......sorry to report the exact same errors and results.

Sy

 

[NoelDP]

Yeh - that's to be expected as the CheckSUR can't do normal file replacements, unfortunately.
See my last post for the fix for the driver file - and once that's out of the way I'll see about the problem with the manifest file.

 

[symosk]

Noel.......I encountered a problem. I got as far as storing all the unzipped files
in a folder named smkab in C dir C:\smkab

Unfortunately, I'm unable to do a "Repair My Computer", since I don't have (or unable to find)
Windows 7 Pro disk that it requires. Trying to remember if computer came with (1) when I bought
in 2011 I thought it came with 7 Home, and I updated to Professional so that I install my old XP in
"virtual mode", which I did, and ironically I've never used

Noel, I tried to do an XCOPY in safe mode......didn't work

XCOPY C:\smkab C:\Windows\Winsxs /y /i /s /v /h <access denied>


Noel, I really do appreciate all the time, hard work, and effort you've spent in trying to solve this
problem of mine. Fortunately, everything seems to work just fine, even with those manifest and package
errors. Windows Update, The printer, video, audio, graphics, system restore....everything seems to work
just fine.......perhaps, I should just leave "well enough" alone, unless you can think of another way for me
to copy those files over into C:\Windows\Winsxs with the correct attributes.

I 'ghosted' an external USB drive sometime in July......There's no quarantee that those errors were not present, even back then......I have restore points going back pretty far, so I wonder if I should just do a system restore to check for those errors......of course, if actual manifest files were missing, the restore would probably not help, so back to "square one"........What are your thoughts?

Thank you very much....you've been a wonderful help about this
Sy

The thing I would love to know is exactly what computer function those errors point to..........

 

[NoelDP]

You don't normally need the disk for that, unless your system has no System Reserved partition?
YOu can create a Repair disk, anyhow... http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

 

[symosk]

Noel.........For some reason, I'm having trouble with the XCOPY syntax ?


DIR C:\smkab <OK>

then

XCOPY C:\smkab C:\Windows\winsxs /h /i /s /v /h <access denied>


keeps giving me that it can't create directory windows\winsxs
I'm not trying to create C:\Windows\winsxs directory, but copy to it from from C:\smkab

There appears to be nothing wrong with the attributes, just the C:\Windows\winsxs syntax????????