[Solved] Update problem

Yes, installed the newer version of this and confirmed it this morning.

 

(Previous post deleted, new info since then) Had to do a System Restore this morning for an unrelated problem, so I lost the new version of KB3177467. Installed KB3177467-v2 from MS Update Catalog. Old version gone from list. Other updates- 4457918- "failed", error message 80070BC9, but got the familiar pop-up to restart, and then the usual messages when an update is being installed- "configuring...." But 4463376 was installed instead of the specified one. 4459922- "successful", but installed list shows 4457008 and 4457035 instead. 4457918 reappeared on the list of offered updates, this time "successful" but installed list shows 4457044 and 4457016 instead. 4054530- "successful", shows in installed list. 4462923- failed again both from the updates screen and from a download from MS Updates, error code 80073701. This continues the months-long trend for this type of "rollup" to fail the installation. BTW, previously, I never got the usual "failed" message on the "install updates" page, but they all show as failed in the installed list, dating back over a year.

Questions- What further should I do? Could there be a glitch in the updating function in this computer?

 

Slowpoke,

I left you a suggestion in your "Where to go from Window's 7" thread.

 

Many thanks for this. After I posted earlier, I found some advice re error 80073708. What do you think?
https://www.techsupportall.com/how-to-fix-windows-update-error-80073701/

 

Thanks, I'm ready to try that right now. Will report back

 

No joy- following the steps on this link brought this, after which the update still failed.

The next step resulted in an error message, can't figure out what's wrong.

I thought I typed correctly, the instruction shows the text on two lines, but the only way I know to start a new line is with the enter key, obviously no help here.

 

Searching the error code returned many hits, most apparently old, with broken links. One hit was an "associate" MS help site which jumped to chat format immediately and after a short exchange the tech said my issue could only be fixed by remote access and offered a support contract for $80 or $100 or so. This seemed fishy, especially since the response was so immediate without much detail as to what the problem is, so I ended the chat.

Edit- plodr- just tried the link you posted again, but the page would not open.

Just tried again, left one space between the two "software distribution". Message was "access denied." Also tried starting by right-clicking Command Prompt from Accessories on the All Programs menu, then clicked "run as administrator", still no good.

 

plodr- just got back to the page in your link, I remembered that I had bookmarked it. Ran through it again, and one of the previous problems is now supposedly resolved- "service registration" now says, fixed. The other error, see screenshot in above post, persists. But I still can't get the command prompt section to accept my input.

No luck with manual update either.

 

Thanks for the lead, I'll try it. So far today I ran the check disc function and troubleshooting from control panel, still no joy.

 

Again, my thanks. Earlier today I registered there with the same user name and posted what I hope is a comprehensive account of the issue, and attached the screenshot I posted here of the failed registry edit.

As far as that remote access guy, even I saw through him immediately, he needs to adopt the screen name "slick."

 

Thanks to the help received here, and the link by plodr in post #31, I'm pleased to report that my updating problem is now solved. Special mention to Tony D, allheart55, and plodr for saving my bacon once again. My grateful thanks to all!

 

Just so. Of course, in Croatia, the home of the tech who helped me, Thanksgiving is not observed- but I am immensely thankful for his help (and sent a donation). My heartfelt thanks to you for your efforts, including directing me to that site. Your insight into his situation made his effort all the more remarkable. And, at 7(?) hours ahead of me here in the eastern US, the time stamps on some of his posts indicated that he regularly toils into the wee hours!