Main Forum > General Computer Support
Missing Windows Servicing Packages files & update problems
Shane:
Wow! 9 pages so far in this thread, I was just speed reading through and noticed you are waiting for some advice from me, I am also answering all the other posts right now as well.
If you dont mind what posts in this thread should I go and read carefully to answer your questions? I also noticed you said you did find some bad sectors, the moment you find even one bad sector it is normally a good idea to replace the drive because it is only going to get worse.
All hard drives have a small batch of sectors set aside so when a bad sector is found then it is remapped to a good sector from one of the spares, by the time Windows finds bad sectors that means that all the spares have been used up and there is no more spares to remap to. So this also shows that the bad sectors are growing and will only get worse with time. :wink:
Shane
Boggin:
Yes, that was it Tony.
I would normally copy & paste the Notepad text but I was looking for how to just add the link.
Unfortunately, I'm getting the error that it cannot find findstr so the Notepad file that opens is empty.
Tone111:
Ah I see, can't believe you haven't attached a file to any of your 1100+ posts before though! :omg:
If the CBS.log (I presume?) doesn't contain the string typed inside the findstr [] then it won't pass anything to the file created - I've had this before. Either that or the syntax of the dos command isn't quite correct so it's not running as expected and then not returning anything even though it's there - what's the exact syntax of the command you're using?
Tone111:
Hi Shane. yeah, sorry it's been such a looooong process and long-winded thread! :rolleyes: but it's been worth the drag and I'm very grateful to yourself and Boggin for all the help and advice offered :artist:
There were a couple of outstanding questions though - to cut a long story short, as I know you're a busy guy with a lot on your plate right now, following an (eventually!) successful repair install the system is now fully updated and your pre-scan has come back clear for the first time ever. SFC is also clear (after a late fix for some new errors using a different program). To save rephrasing what I asked Boggin, which he said to wait for your advice for, I've copied the following couple of paras from my earlier posts, so if you get a minute I'd be interested in what you think the problem and solution might be, cheers :smiley:
"Every time I've managed to get any updates on, without fail, the machine would configure and restart ok (apart from once where it said Reverting changes), then upon rechecking it would throw up error 80080005 and not be able to check due to updates pending; also there would be a pending.xml present and SFC scan would not start due to reboot/repair pending, so I've had to go into Repair mode every time and manually rename pending.xml (can't do it within Windows! :angry:), then SFC scan would work, then I could reboot back into Windows and re-check successfully for updates, where it would always find more! I now have 4 or 5 renamed pending.xml files - do I need to keep them all? There's also a reboot.xml as well, what about this one?
My only question now relates to all the renamed pending.xml files - do I need to keep them? And the reboot.xml in the winsxs folder as well? And I'm a bit wary that every time the monthly updates come around that I'll be in the same boat having to rename the pending.xml and do a double (or more!) reboot and recheck every time - any idea what's causing it to do this or how I can stop it?"
Boggin:
It's not often I need to ask for help as I can usually find a fix and I would have just normally copy & pasted the file.
The command I used was findstr /c:"[SR]" Cannot %windir%\logs\cbs\cbs.log > 0 & notepad 0
I'll have to check the sevenforums tutorial for sfc /scannow.
The reason I ran the sfc was because of what KB3022345 was doing http://www.infoworld.com/article/2922324/microsoft-windows/windows-usage-tracker-patch-kb-3022345-triggers-sys-file-corruption-which-sfc-is-unable-to-fix.html so while I had uninstalled the KB because I kept getting errors that the Diagnostic Tracking Service had stopped, I decided to reinstall it and run a sfc /scannow and got an identical report to the one you had posted.
That would tend to suggest your errors were a direct result of installing KB3022345.
Anyway, I ran the SFCFix.exe and that sorted mine out as well.
I've been thinking about restoring back to before I reinstalled the WU but have checked Reliability history and there's no repetition of the Diagnostic Tracking Service error so perhaps it was the file corruption it had caused which was also responsible for the error - I'll check Reliability history again tomorrow before I make my final decision.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version