Windows 7 update success

Topic

New Reply

This in from Jim in Yakima (which is where I went to high school!): As you and untold numbers of other frustrated users have experienced, the Windows
[See the full post at: Windows 7 update success]

Reply | Quote

Replies

Woody,

Just looked at your last post. I tried the same thing last night. It took windows Update about 20 minutes to look for updates and about 0 minutes to install. INITIAL conclusion was that everything was OK. I let computer run all night, and so far this morning everything looks OK. I’ll let you know if there are any problems later on today.

Reply | Quote

OOPS ! ! ! clumsy fingers here. It took about 30 minutes to install. Sorry.

Reply | Quote

Hmmmm!
Win7 Ult laptop with 6GB RAM – searching was at 6 hours when I went to bed Sat. Somewhere in the night it came up with the list of updates. Sun. morning, downloading ran until around noon seemingly doing nothing until the updates finally arrived.

I don’t think anything’s fixed. I think we’re just wishing.

Reply | Quote

I use Autopatcher exclusively, haven`t used WindowsUpdate for years and my systems are stable as a rock!

Reply | Quote

The latest version of Autopatcher supports Windows 7, 8.1 & 10 and also only Vista 32bit (x86). Autopatcher has never supported 64bit Vista so Vista x64 users will have to use WSUS Offline Update tool instead.

Reply | Quote

It’s kind of sad when a successful Windows Update makes news. But it is the world we live in now.

For what it’s worth, I’ve managed successful updates this month with Windows 7 and 8.1 test systems that are and have been managed manually.

They BOTH took much longer than they should have, with hard CPU loops before displaying the available updates, but were ultimately fully successful and seem to run fine after. I’ve noticed no new attempts to contact servers online.

Maybe it’s coincidence, but the Win 8.1 system gained a few percent in overall speed in a Passmark benchmark run immediately thereafter (which I do with every system I update).

-Noel

Reply | Quote

@PkCano,

I recall that you had installed this month’s KB3153199 fro another thread and that your machine was working fine. What changed, what happened?

Reply | Quote

I found WU took 92 minutes on my Laptop. I cancelled, rebooted and tried looking for the KB3153199 manually on the MS site and found nothing. Finally gave up and let WU look. After a second 60 minutes the updates were located. I unchecked all and just installed the KB3153199 and rebooted.

I went back and installed the rest but as you said the install sat on 0% for 60 minutes and then finished rapidly. I suspect the progress bar feature is not working correctly.

I too have my doubts about it being fixed. Time will tell, but I suspect this is deliberate by MS to “encourage” Win7 users to update to Win10.

Update: I found nothing because I had read a post somewhere that had the wrong number of KB3163199. Duhh!!!

Reply | Quote

The MS fix it tool (the one that replaced the good windows update fix from years back) always reports it fixed those problem. It can’t detect the problem, so if it doesn’t have anything else to do it just “fixes” it, even if that replaces good entries with identical entries, that still counts as a fix.

Reply | Quote

Fixit didn’t report either the registry or EDB file repair the first time it ran. The first run reported problems (one was “failed update”, other was failure to connect to servers, or similar, which I pretty well knew). There were a couple of items that were fixed, but didn’t seem major. The first run didn’t result in a successful update connection.

The second run and its “repairs”, followed by a restart, did result in the success I encountered.

Not suggesting that this is a salve for the ailing. It certainly didn’t harm me.

In my way of counting, if it isn’t fixed, it doesn’t count.

Counting a failed fix as good would be like Woody’s “X-ing” out of his favorite “Get Windows 10” window and finding the new MS interpretation of “close window” really means, “Yes, go for it!” The ultimate “Fixit”!

Reply | Quote

Here is another one, if your last update status was “failed to install update for reason code 0x80071234 (error message that microsoft forgot to document), update fix ran, cleared all history of failures” now it shows “fixed 0x80071234, because the last error was — no error (we just erased the record of it)”

Reply | Quote

Never10

https://www.grc.com/never10.htm

Reply | Quote