[SOLVED] Expert help needed with CBS corruption that was not fixed on reboot-

[Harddrive52]

HP Pavilion a6510p-(dsktp)
Windows7x64sp1
RAM: 4GB RAM
HDD: 750GB
I'm working on this computer for a friend who is a photographer.
(I'm the computer guy in our neighborhood)

Initial complaint was that his printer would not respond to any commands 'to print' and also Windows Updates were in a fail-install-fail-install loop. He just never dealt with the problem and now it is rearing it's ugly head.

He moved his printer from Windows XP to Windows7x64 and was using the old install CD for drivers which were outdated and incompatible with the newer system. He also has a large-format scanner which is in the same shape...I believe he migrated old Windows ME files and he uses whatever he thinks is working...UGH! Yes, we have had a talk.

Sorry, back to the task at hand...
I attempted to do some repair by running System Update Readiness Tool and it found multiple problems, only 2 of which it fixed. The remainder were 'Unavailable missing ??? and it could not fix them.

I copied the files from my working Win7x64sp1 machine to a flash drive and then to the c:/windows/temp/Checksur/servicing/Packages folder on his machine...it fixed 1 or 2 other files, but then on rerun of SURT and reboot, it seems more problems were revealed.

I have done some repairs on 'store files' in the past by using elevated Command Prompt and typing out the whole command for taking ownership, copying to, etc, etc. But, this is not my area of expertise and it gets so mind boggling if you aren't focused intently...:banghead:

At this point, I ran an 'in-place upgrade' install over-the-top which was very successful and re-installed all Windows Updates until it had no more.

Now, SFC /scannow and S.U.Readiness Tool are showing no errors. But, the CBS.persist.log still has the same errors as before the 'in-place install'- showing as 'unavailable missing'?
Before the 'in-place upgrade', I did create a 'DiscWizard Backup Image' of this drive and saved it to external drive, so, nothing to worry about on that front.

Sorry for the long winded intro., I hope it makes some sense.

Thanks,
Mike

 

[Go The Power]

Hello and welcome to the forum.

I am not seeing any errors in the new CBS log that are of a concern. If the errors where showing in the old Persist logs the likely hood is they would have been fixed during the in place upgrade :)

Was the a particular part of the log you were looking at?

 

[Harddrive52]

View attachment CheckSUR.persist.log
Go the Power-

Thank you for looking at this!

I kept thinking the same thing about maybe those errors (about missing manifest, mum, cat files), seen before the 'in-place install', should have gotten replaced/repaired afterwards.

What was concerning me was, after running a new SURT and SFC /scannow; when I would reboot and check the CBS.persist.log I would see the same list of files missing as previously reported. NOW, I realize that the persist log shows a running list of errors and repairs, one after the other.

My fault for not scrolling down the list to check it out more closely. I can see at the bottom of the new list it shows no errors!

If you don't mind, I will attach a copy of my CBS.persist.log and maybe you can verify that what I'm seeing is indeed an 'after inplace upgrade', self-corrected CBS.persist log- showing 'no-errors' at the bottom...:r1:

Thank you so much for your help and clarification on this matter. :thumbsup2:

 

[Go The Power]

The most recent CheckSur scan looks like it went well, no more issue are being detected :)

 

[Harddrive52]

The most recent CheckSur scan looks like it went well, no more issue are being detected :)

Thanks so much for the expert help.

:dance: ~Donation gladly made~ :dance:

 

[Go The Power]

Thank you very much for the donation :)

Alex