Suprise with M$ updates

[Wandering one]

Have always had both my computer and wife's laptop set to NEVER check for updates. I usually manually check perhaps twice a month, and usual time to search was around 30 minutes. Since January times were in the hours and many times I just gave up.
Since the middle of this month I tried three times on each computer and the longest wait was SEVEN MINUTES to have the update list ready Is this a mistake or are we now allowed server access for W7 ?
Art.

 

[Callender]

Users with problems keep blaming MS Servers. Personally I find that update searches might go slightly faster if avoiding serching on Patch Tuesday but those long waits seem to be down to:

Incorrectly configured machines.
Missing updates.
Old updates (WUC) are installed that don't work too well.
Pending or failed updates that haven't been cleared.
Problems with installed versions of NET Framework.

Many users have been able to fix the slow update search problem. If it just went away on it's own with no changes to your system then who knows why?

Any time I've had problems - and I've had a few including this month - there's always been a fix.

 

[ThrashZone]

Hi,
Yea timing sounds about right
Lots of workarounds

I'm not a fan of hiding updates or switching to never check for updates yet
But hiding updates if you do I've found that really does freak out the update system lately
I surely wouldn't hide an Important update ever.

As long as you sort the updates accurately meaning in update setting excluding Recommended updates from being installed the same as Important ones
I haven't had many issues with the real Important updates
But I do have 21 or so Recommended and a few Optional updates I stay well away from

Microsoft Net framework wow that is a weird one which I've found Net 4.5.2 is the best to have around
As far as workarounds there has been one every month
Oddly the updates to install first and manually were Kernel mode drivers
These are updates that quite a few people would usually hold off on installing
But installing it brings up quickly the rest of the round of updates for that month and possibly other prior updates :/

Here's this months workaround listed where most workarounds are first posted at
Brink post these every month,
http://www.sevenforums.com/news/397321-microsoft-security-bulletin-summary-june-14th-2016-a.html

 

[Callender]

RE: Problems with NET Framework. I mean one of those problems that you'd never notice unless you tried to tried to uninstall/change or repair an existing installation then you might get informed that the program could not be uninstalled or repaired.

Some uninstallers (including the no longer supported Comodo Programs Manager) indicate problem programs or partial installs with a red X. Windows doesn't give any easy visual indication that there's a problem.

​

Well I had a red X against one of those NET Framework versions some time last year. Removing it using the cleanup tool and reinstalling it also fixed the slow WU problem that I was having at the same timhat'e.

EDIT: That's Prio fixed. (There's no longer a red X against it) - Looks like I'll need to fully remove and reinstall the other program.

​

EDIT: Off topic kind of but fixed the other program. The point is that windows does not always show any signs when there's a problem especially with NET Framework.

​