Main Forum > General Computer Support

Missing Windows Servicing Packages files & update problems

<< < (29/33) > >>

Tone111:
Ah yes, I remember you posting that earlier in my thread - take out the "Cannot" and it will work fine!  :artist: not sure where it's come from but it shouldn't be there and gives an error which goes when you take it out. If the notepad file generated is still blank then whatever is inside the [] ("SR" or anything else) hasn't been found

I've noticed KB3022345 on my installed updates list, but it did fail initially and reverted changes on one occasion before it installed, for whatever reason - looks like it might be one of MS's notorious dodgy updates if it's done the same on yours. Glad the SFCFix could be of help anyway - nice to be able to repay all the help in some small way  :smiley:

Boggin:
Did you run another sfc /scannow after the SFCFix.exe to see if it was clear of corruption ?

Removing cannot didn't produce anything in Notepad either.

Tone111:
Yep, ran SFC again yesterday and it was still clear  :artist: although as no more 'proper' Windows Updates have been installed since I ran the SFCFix (just a couple of IE security updates and a Windows Defender definition) then this is hardly surprising - the acid test will be next month when the new patches are all released!  :undecided:

Is yours still clear after the fix?

If taking the "Cannot" out hasn't returned anything then the "SR" isn't present in the file you're searching (CBS.log etc) - I ran it on mine and it opened a blank Notepad file (but without the DOS error that the "Cannot" produced), but then my CBS.log is tiny now after the repair and a manual search for "SR" didn't find anything either! I think that's the 'issue' as such - just the fact that it isn't there to be found  :thinking:

Boggin:
Restoring to just prior the WUs still produced files it couldn't fix and got the same with an offboot sfc.

Had to restore back to about a week before WUs before sfc /scannow was able to repair found corrupt files.

I've reinstalled the WUs less KB3022345 and thought all was well until I noticed my sound wasn't working.

No alerts or red crosses on the icon and the Realtek says it's working properly, but still getting Failed to sound test tone.

I'm not sure when this started so I can only assume one of the WUs is responsible - time will tell, but I'm not going to fight with it until tomorrow.

Shane:

--- Quote ---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?"
--- End quote ---

You can remove these, in fact my repair windows updates does the same thing and more, the more I have dug into Windows updates and how they work the more I realize how big of a mess it is. You can tell hundreds of people at MS have had their hands in it and so it is a big mess.

After all it was reported MS had a 110 programmers just for the start menu and taskbar alone for Windows 7. Now imagine how many they had for the updates. I read one time where Windows had something like over 10,000 programmers to make it. Not sure how accurate that is but it does explain why things break as easy as they do in Windows. EVERYTHING in Windows depends on something else, so when one thing breaks it creates a domino effect and then the horrible type of error messages give the user or tech no clue on where down the chain the problem is.

To many damn fingers in the pie!

Shane

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version