Replies

Apparently the edit window has passed.  But I meant to point out that the first stuck-at-58%-configuring message I refer to was *after* the first reboot and welcome screen, i.e. things seemed to be going normally before the first reboot.  Same goes for all the other stuck-at-58% and “reverting” screens, although it all became kind of a blur…

Kind of similar situation on one of the three Win 7 pc’s where I attempted to use Windows Update to install KB4512506 Quality Rollup, KB4474419 Security Update and MSRT all at once.  While everything went fine on two of the computers, the third was stuck for ~15 minutes at 58% of “Configuing Windows.”  I had had a couple of past instances where I would have to wait as long as an hour for one of my computers to complete “configuring,” so I just let it continue chugging.

But instead of eventually progressing past 58%, it  gave the “Failure Configuring Windows Updates – Reverting Changes message” and rebooted.  Then the exact same thing happened all over again — stuck  at 58%.  Then it happened yet again.  But the fourth time, instead of a configuring countdown it gave me the “reverting” message immediately upon reboot.  Then THAT behavior repeated again.  But after the second no-configure-attempt reboot and immediate “reverting message”, on the next reboot my desktop came up, with a system tray balloon message that some updates had installed, but some had failed.  Turns out only the MSRT had installed, while KB4512506 and KB4474419 had both failed.

I haven’t yet made any further attempts on the affected computer, but I’m glad I just patiently “let it run its course”, and was happy it gave me the “privilege” of seeing my desktop again, without having to deal with any possible forced-shutdown/safe mode machinations (not that having done so would have necessarily been a problem…and besides, who knows what the next attempt will bring…).  I’m leaning against doing a System Restore before the next attempt.  But regardless, I will do (“try”?) one update at a time the next time.

Maybe this is all related to incompatibility with some program or driver that is on the third computer, that isn’t on the other two??

1 user thanked author for this post.

jburk07

KB4512506 Quality Rollup and KB4474419 Security Update are both dated August 13 for me as well.  I wonder if the Computerworld article reference to August 17 for one of them was an error?  Or does it somehow vary among Win 7 users?

1 user thanked author for this post.

jburk07

Group A.  3 Win 7 machines, two with 64-bit Pro and 1 with 64-bit Home Premium.  Installed the Monthly Rollup and MSRT on all three, plus Microsoft Filter Pack 2.0 update (KB 3114879) on the applicable Pro machine.

Everything seems fine, although — unlike Blizzard — I did have to reconfigure Windows Media Player on all three machines.  This seems to be required more often than not these days.

1 user thanked author for this post.

Myst

Windows 7 64-bit, Group A.  Updated and all seems OK (so far…)  But — as now seems to happen more months than not — Windows Media Player has to be re-configured.  An annoyance, but a minor one since all options/settings are retained except for how often to check for updates.

2 users thanked author for this post.

jburk07, dgreen

Same here on *one* of my three similarly-configured Win 7 pc’s with Firefox 60.6.1 esr.

But on pc #2, the same add-ons were left enabled and in the “main” add-on page, but with a caution message added, e.g., “Adblock Plus – free ad blocker could not be verified for use with Firefox.  Proceed with caution.”

On pc #3, everything is working normally with 60.6.1 esr and (mostly) the same add-ons .  There aren’t even any messages of any kind.  (Maybe it will just take awhile for symptoms to show, since this is the first time I’ve fired up #3 in 2 or 3 weeks?)

Weird that the situation would be different between the three pc’s.  This is all without any kind of action of my part.

Same situation here with 60.6.1 esr when I first opened it a few minutes ago.

EDIT:  Just found that on my second Win7 pc, also with Firefox 60.6.1 esr, those same add-ons have been moved to the Legacy section and disabled.  Then on a third (which hasn’t been used in at least two or three weeks), everything looks and works completely normal (at least so far…).  Odd how the situation would vary between three similarly-configured pc’s.

Group A Win7 x-64.  Installed all three Important-tab updates I was offered (4489878, 4474419 and  890830), all of which were pre-ticked.  When finished, 4490628 (servicing stack) popped up and I installed it.  I was never offered 4493132 in either Important or Optional…not that I want it.  As mentioned in prior post, I had to take a minute to configure WMP again…mainly just clicking OK to retained settings.

1 user thanked author for this post.

jburk07

Group A, Win7 64-bit.  As is frequently the case lately, Windows Media Player had to be reconfigured after the updates.  Annoying, but it only takes a minute to address because it essentially saves my old configuration.  Specifics:

Open wmplayer (which for me points to C:\Program Files (x86)\Windows Media Player\wmplayer.exe).  It will open to the first Configure screen.  Choose Custom Settings and click Next. Next tab should have preserved all your old choices, so just click Next again.  Choose “Choose the file types Windows Media Player will play” and click Next (unless you use WMP as your default video and audio player, in which case you should choose the “Make default” option).  The displayed associations list should be unchanged from what you had before, but you might want to skim through to be sure.  If OK as expected, just click cancel.  On the final configuration screen refuse the Bing online store unless you use it.

After that simple process, I always find that the ONLY setting that has changed in the player itself is that “Check for Updates” in Options went from once a month to once a week, so I just change it back to monthly (not that it ever checks anymore, anyway…)

 

Group A, Win7 64-bit.  Still haven’t been offered the KB 4493132 “Win 7 ending” nag update.   I wonder why it is offered to some, but not others (as confirmed in numerous posts a few weeks ago).

“This specific security breach wasn’t directly responsible for the ShadowHammer infiltration, but it demonstrates an incredible lack of concern over simple security procedures.”

Three months ago I bought an Asus router (RT-AC68U), but hesitated due to the company’s history of a lax attitude toward router security issues, including failing to keep customers apprised of threats (see link). Asus had even received warnings from the FTC regarding this.   While the router has performed beautifully thus far, it appears that attitude persists — across products —  and I’m now wondering if getting the Asus router was a mistake.

Computerworld – Asus router warnings on privacy and security

Group A.  Just checked for updates — 11:30pm 3-20 — and I’m not being offered KB4493132 in either the Important or Optional tabs.  So I’m also wondering if it might have been pulled.

Or, while I suppose this is unlikely, I was wondering if my machine is being excluded because its Win7 Pro 64-bit was a manufacturer-installed downgrade from Win 8.

Group A here. For reasons I won’t go into (embarrassment may be one :)) I took the rare step of running WU on my three Win 7 machines yesterday, while we’re still at MS-Defcon 2.

No problems on two  of the machines, but on the third Word 2016 was molasses-slow when I tried to save a document.  Then a couple hours later I was trying to save another document, and had to give up and force close.  Explorer seemed unable to refresh.  Then Norton gave me an error message and clicking “fix here” accomplished nothing…then the Norton UI locked up.  There’s more that was messed up…I won’t go into it all, but the kicker was that — for the first time I can recall — I got a notification above the system tray that my copy of Windows was not genuine.

Rebooted (I had to force-close one program..I forget which), but problems remained.  Rebooted again, this time into recovery mode.  Ran System Restore from there to try to undo the WU.  Fortunately the Restore seems to have been flawless, no remaining issues that I can find.  Will definitely wait for Defcon 3 before trying again…or maybe I’ll just wait until next month.

BTW, I don’t know for sure whether it was actually necessary to run the the Restore from recovery instead just trying a full reboot first…but it just seemed like a “cleaner” way to proceed.  And I also have to wonder whether this was actually a problem with the updates themselves, or possibly just, e.g., some sort of unlucky application conflict that occurred while I was trying to update that machine.

“That’s precisely what the title of the entry was supposed to do — make you think about it.”

And indeed it did.  My initial reaction was “What??”  Followed by, “Interesting food for thought,  but I’ll likely still be with Win 7 at least somewhat after EOL.”  Followed by “People who felt offended by the title need to lighten up a little” (which does *not* mean they have to agree with Susan, at all).

Susan, what do you think of Matthew’s (and others’) suggestion as an alternative, namely “moving up to Win-8.1 for those of us who bought PCs with a Win-8.1 license but Win-7 preinstalled?”  Thus obtaining extended support for 3 more years after 7’s extended support ends?  Thanks, Rick.