August Patch Tuesday

[kado897]

A total of 15 updates for me this month. There are two large .NET 4 updates which are initially not selected. Apply these after the main bunch they take a long time to apply. On the shutdown for restart it sat at the preparing updates screen for over 30 minutes so be patient.

 

[mikedl]

On the shutdown for restart it sat at the preparing updates screen for over 30 minutes so be patient.

Odd. I received the same updates as you did since I, also, have Office 2010 (plus two additional ones for my MS Keyboard and mouse) but the restart was maybe 5 minutes at most.

 

[kado897]

Very strange. It seems to have gone in with no reported issues.

 

[derekimo]

A total of 15 updates for me this month. There are two large .NET 4 updates which are initially not selected. Apply these after the main bunch they take a long time to apply. On the shutdown for restart it sat at the preparing updates screen for over 30 minutes so be patient.

View attachment 169402

That's what I had too, restart was only a few mins at most though.

 

[kado897]

Mmm. Maybe it's because I have the full .NET 4 rather than just the client profile. Plus I've always had issues with .NET 4. Had to re-install it twice.

 

[beauparc]

Installed fairly quickly for me without any problems, and took about ten minutes for the lot.

 

[kado897]

Mmm. Apparently there is a fixit for the problem. Which is even stranger because the update applied it.Installing updates for the Microsoft .NET Framework 4 can take longer than expected in some scenarios

 

[richnrockville]

I also did the updates today, Damn, again because I like office 2003 and have outlook 2010, the updates screwed up my outlook. But after about the 3rd or 4th time I have been thru this, I just went to control panel program and then selected outlook 2010 and change. told it to repair and all is well again.
BTW, if you use itunes and sync an iphone or ipad, don't do it until you repair your outlook..

But I am a happy camper now. And my updates only took about 10 minutes.

Rich

 

[mikedl]

Mmm. Apparently there is a fixit for the problem. Which is even stranger because the update applied it.Installing updates for the Microsoft .NET Framework 4 can take longer than expected in some scenarios

Thanks for looking that up, Kado. Probably the issue you encountered with the updates installing over a longer period of time than those of replying, so far, have experienced.
Great research!

 

[HQuest]

Both updates for .Net Framework 4 were not checked by default. Including Office 2010 x64, 15 important updates too. Will see how long it will take to install.

 

[kado897]

Mmm. Apparently there is a fixit for the problem. Which is even stranger because the update applied it.Installing updates for the Microsoft .NET Framework 4 can take longer than expected in some scenarios

Thanks for looking that up, Kado. Probably the issue you encountered with the updates installing over a longer period of time than those of replying, so far, have experienced.
Great research!

The problem is I only noticed it because It was installed twice along with each set of the updates I applied yesterday and the second set (the .NET 4 ones) still took 30 minutes preparing windows. Maybe the second install uninstalled it.:sarc:

 

[piattj]

...large update files... had this kinda thing before...

I invoked Windows Update last night & found, as we all did no doubt, a bunch of updates for Patch Tuesday.
I tried twice but on both occasions, installing the 2 big .NET 4 files failed (error 643)... but all the other patches went in fine...so I rebooted, went into WU again, this time found an additional security patch for .NET 4.

I installed this one on its own. All OK
Then the first of the 2 .NET patches that failed previously... all OK
Then the final .NET patch on its own... all OK.

This is an approach I've taken of late - not installing all at once but taking them singly. Tend to find a more reliable smooth update in that way.

Any thought / comments / observations / experiences?

 

[Hopalong X]

+1 Piattj

I install the updates one at a time. There were two about 300Kb I did them both together.

Also when you do one at a time and you are prompted to reboot do so then. You know that update is finished.

That prevents potential problems as you found out Piattj.

Just makes sense to take the extra time as you install. You only do it once a month.

Mike

 

[derekimo]

I just install everything that's already checked, reboot, install the rest, reboot.

I usually just try all at once, if some fail they usually go the second time.

 

[FredeGail]

I lagged so bad during the install. Seems to have passed now.

 

[dwarfer66]

I installed all of the updates, no problems, booted normal

 

[DBone]

I installed all the updates, including the two that were unchecked by default, with no problems and no long wait time. The .net optimization services went crazy for about 60min after reboot, but they eventually disappeared.

Question.............Why does MS not check some updates, but still marks them as recommended? Seems like most of the general population won't have these installed because most people never even look at the update screen, and they are set to auto as well. So if they are recommended then why not pre check them?

 

[kado897]

I think it is an attempt to get them installed after the others are out of the way. I suspect that if you hadn't run the unchecked ones they would have been checked the next time the check for updates was run.

 

[TVeblen]

Like piattj & Mike I do not install all updates all at once. I know I could. But I don't.

I install in groups:
All the securities at once
Then all the general Updates
Then any IE's
Then .NETs - one at a time.
Then any optionals

The one time I broke this rule the .NETs got screwed up. Turned a 5 min job into a 30 min job. Never again!

 

[FredeGail]

I installed all at once. Made me lag like creep.

Best Regards,
FredeGail