Replies

Give it up to two hours, even if it looks like nothing is happening.  Based on info I found Googling that’s what I did with one of my similarly “stuck” Windows 7 updates a couple months ago.  The same update had installed promptly on my other two Win 7 computers.  Just as I was preparing to abort at the one-hour point — especially given no evidence of disk activity — it suddenly “came to life” and finished the installation.  After the reboot it confirmed a successful installation.

Glad it worked out!  But had you just waited longer the first time — up to two, or even three hours — it’s likely your “stuck” installation would have eventually completed.

A couple months ago, after the updates had gone smoothly on two of my Windows 7 computers, I ended up at an apparently “stuck” “configuring” screen on the third computer.  But I read about how it can sometimes take up to hours to finish.  After nearly an hour I was ready to force-close anyway, when — sure enough — it finally started counting percentage completion, quickly finished and rebooted, with all updates successful.

1 user thanked author for this post.

jburk07

Yeah, I’ve sometimes wondered what proportion of Windows 7 and earlier-version users are aware of that integration.  In fact, I’ve sometimes forgotten about it myself until I see files opened locally in my Computer lumped into IE history…or remember that Start/Run Autocomplete is toggled on/off via an IE setting.

On a related note, what happens if you “turn off” IE in “Turn Windows features on and off?”  Will you still get offered the security update?  Again, confusion.  Also, is Edge an integral part of Windows 10?  Or is that OS finally, fully browser-divorced?

What exactly do you mean by “just stalled?” If it’s that the the machine just seemed stuck on some sort of Configuring Windows message, you really should have waited — a long time.  See my post linked to below, about a situation where an update that installed quickly on two of my Win 7 computers required 55 minutes to finish on my third Win 7 computer (with a Configuring Windows screen staring at me almost the whole time):

https://www.askwoody.com/forums/topic/ms-defcon-4-with-the-win7-monthly-rollup-now-working-its-time-to-get-everything-updated/#post-230337

As for a remedy for your current situation, if geekdom’s suggestion doesn’t work you could try a system restore back to before the update process was started, and try again.

 

1 user thanked author for this post.

frankus333

I have a number of WMP non-default settings and filetype associations, and the *only* one that is ever changed by a WU-induced configure request is — ta-da — how often to check for WMP updates.  It takes under 2 minutes getting back to where I was before the WU, with most of that time being in recreating my WMP shortcut for the QuickLaunch.

2 users thanked author for this post.

SueW, DrBonzo

A few years back this would happen pretty frequently.  But this time is only two months since the last.  That’s annoying.  Fortunately, as I mentioned then, almost all of the old settings seem to be preserved. so it’s a quick fix.

https://www.askwoody.com/forums/topic/ms-defcon-4-with-the-win7-monthly-rollup-now-working-its-time-to-get-everything-updated/#post-229820

1 user thanked author for this post.

SueW

Fyi:  I am in Group A, and a few weeks ago I took a chance and decided to install the .NET Security-Quality Update & the MSRT on all 3 of my Win 7 machines.

On the first two machines everything proceeded briskly and completed.

But on the third machine, as it was powering down to reboot, the screen seemed stuck at “Preparing to Configure Windows (Update), Do Not Turn Off Your Computer.”  (No countdown percentage shown.)  After a half hour I was tempted to conclude it would never finish, and was ready to to force-close.  But I read some things saying that force-closing can cause problems, and to give it a good 2-3 hours before concluding it wouldn’t eventually complete on its own.

I was skeptical, and at about the 55 minute mark was getting ready to force close it.  But before I could, sure enough it finally shut down by itself, reboot normally, and quickly finished setting up the updates.  Yesterday I installed the October Rollup on the same machine without issue.

1 user thanked author for this post.

bassmanzam

The need to re-do Windows Media Player setup after a WU is something that I *thought* had  finally gone away.  I used to have to go through that task after 2-3 WU’s a year, but it seems like it had been perhaps two years since the last time.

The good thing is that — as before — it’s only the few setup screens where options need to be re-selected.  (Over three years ago I created a document to remind me what settings I had chosen.)  Once WMP is back up, I find all my other WMP options — including my selected media file associations — remain in place…with ONE exception.  The one exception is update-check frequency, which always changes from once a month to once a week (not that there’s ever an update anymore anyway….).

3 users thanked author for this post.

SueW, jburk07, HiFlyer

Ever consider sub-Defcons? At least for 10 vs 7/8/Sever 2008?  As wonderfully helpful as the posts are, sometimes it seems like the single Defcon rating is mixing apples and oranges.

1 user thanked author for this post.

Charlie

Group A, Win 7 64.  Just as a data point,  I have only the “old” version of KB3177467 that I installed two years ago, but I was able to install the latest MSRT plus one Office 2010 update today.  (I haven’t installed anything else offered in October.)

I guess I’ll just kick back and wait for the November Rollup and Defcon 3.  Assuming I even get *offered* the November rollup that is…or we ever again attain Defcon 3…  Win 7 Pro 64. KB3177467 installed October 2016 through WU, haven’t seen the October rollup since it was withdrawn (and that applies even on another Win 7 64 machine where KB3177467 was offered and added a few days ago).

I just checked for updates and the October rollup went away for me too (Win 7), and  likewise the 2018-09 Rollup Preview reappeared on the Optional tab (KB4457139).

3 users thanked author for this post.

dgreen, columbia2011, DrBonzo

Fyi, from my notes on 10-11-16 (Win 7):

First, I noted that dreaded and long-avoided telemetry update KB2952664 had refreshingly *not* made its usual re-appearance.

After other updates I begrudgingly installed KB3177467, which was on the Important tab and ticked.  The instant it finished — without even rebooting —  I got a “new updates are available” alert, and when I opened WU there was (unticked) attention-hog KB2952664 staring at me for the umpteenth time. And I hid it for the umpteenth time.

I’m concerned about people who don’t vote because they have been successfully discouraged or even prevented from doing so (in various ways) by others who feel they would vote “the wrong way.”

LOL, before seeing this I’d already followed the suggestion in your August 23 ComputerWorld article: “I suggest you wait another day or two before installing the August patches.”

I installed everything in the Important tab that was pre-checked: the Rollups for Windows 7 (64-bit) and .Net, plus an Office 2010 Security Update, and the MSRT.  I didn’t install .NET 4.7.2, especially since it wasn’t pre-checked.  So far no issues that I can tell.

1 user thanked author for this post.

jburk07