Bork Tuesday, Any Problems Yet?

A possible problem with Win10 x64. I had already successfully installed today's updates and restarted. I've just restarted again and my machine is sitting at the "Preparing to configure Windows... " and it doesn't look like anything is happening except the dots are still spinning. 5 minutes or so at this point.

It says not to turn off my machine but if nothing happens how long should I wait?

 

If you computer has a hard drive light, if you see it is blinking from time to time, it means that the the updates will still be installing. If it never comes on, it will be safe to force the computer to power off.

 

Thanks Roger! No light activity, so I forced a shut down. All seems OK, but I running sfc /scannow just to check.

My first Win10 update problem in nearly 12 months of using Win10.

 

http://www.ghacks.net/2016/06/14/mi...16/?utm_source=twitterfeed&utm_medium=twitter

 

http://www.sevenforums.com/news/397321-microsoft-security-bulletin-summary-june-14th-2016-a.html

 

Just updated my Win 8 without any problems...

 

Windows 10 x64: Updates.

 

I just updated Microsoft Office on my OS X El Capitan. Everything went smooth working great.
As for Windows 7, holding off until after the Microsoft Free period. I have all my secure files transferred to OS X because I don't know what the heck Microsoft is doing anymore, I don't think Microsoft knows either.

 

Is anyone else having issues with WIN 7 updates?

I noticed a couple of days ago that that PC fans were running more than usual. Sure enough, the win update .dll in svchost.exe -netsvc was using 17% CPU capacity for my 6 core CPU. Also when I try a manual Win Update, it just hangs at the downloading step and never finishes.

Tried the MS Fix-Its to no avail. Presently have all auto Win Update options disabled which fixed the CPU pegging issue.

 

"The Windows Update search/scan "forever" problem has once again resurfaced for Win7 SP1 as of June 14 (June Patch Tuesday). The KB3153199 Win7 updates are no longer doing the job. And once again a new win32k.sys security update (KB3161664) has been released (MS16-073), which supersedes/replaces KB3153199. Win7 SP1 users should now install KB 3161664 manually, to speed up Windows Update scans". http://www.infoworld.com/article/30...nd-windows-10-advances-to-build-10586420.html

 

That doesn't look like an update to the Windows client, or am I missing something ?
This month I had to resort to manual downloads of the updates on Windows 7. That old issue is back.

 

That did the trick as far as excessive CPU usage due to trying to connect and getting nowhere. However, I still see svchost.exe -netsvcs memory peaking at over 1 GB which is ridiculous.

BTW - to install KB 3161664 you will have to stop and disable the Win Update service. Otherwise, you will be stuck with it trying to dial out to Win Update server and the KB install stuck at that point.

 

Every month now, someone comes up with a "fix" for the slow updating issue, which seems to work temporarily for the current month, but then once again, the next month sees the same old issue return again. I've been watching this for months now, and to this date so far, there really is no permanent "fix" for the issue. It always returns the following month. It's the plague of Win 7...

 

After downloading and installing all updates including 1664, i restarted and then did a manual check for updates with 1664 now installed to help out. The manual check only took about 30 seconds to complete saying i had no updates....because i just installed all of them.

 

Yeah, I started the search for updates 2 hours ago on Win 7. It's still searching as I post. I believe it does have the plague!

 

You are perfectly right Kerodo, and that happens with Vista as well (Win 7 and Vista are similar), last month after installing a fix, it took 'only' 15 minutes for my Vista machine to update. Yesterday I left it on for 3 hours to no avail. Very disappointing indeed...

 

3.5 hours just to search for updates.

 

Yes, 3.5 hours seems to be the magic number - on all 3 Win 7 machines here.
Is it worth it - or even safe - to install KB3161664 after the fact?

 

One Win 7 machine needed 1.5 hours to search for updates, the other about 2 hours.
I started search for updates only a few minutes after the Patch Tuesday updates were issued.

Why would you want that?
After installing updates, search for updates should be back to normal.
And installing KB3161664 probably won't change anything for next month, as all previous supposed 'fixes' have shown.

 

Here on Windows 10 Pro x64, all of this months cumulative updates and other Windows updates :

- search for updates ~ 30 seconds.
- download updates ~ 1 minute and 30 seconds.
- prepare updates, reboot and install updates ~ 3 minutes.

That's a total of five minutes before I was back to being productive again.

I must say, I simply love how smooth this OS is.

 

On my Win 7 build, the primary issue wasn't the extended updating searching. It was what the Win update .dll was doing to my CPU activity. Athough overall, process monitor was indicating 17% constant CPU usage, it was using all of my 6 CPU cores and spiking all of them at frequent intervals. That has stopped now that KB3161664 was installed.

My take on this issue is it is being done by Microsoft by design to irritate and force people into upgrading to Win 10 by the end of next month. If this type activity appears again on my PC, I will just disable the Win update service as a few others have done.

 

I ran Windows update on Monday to install May's updates of which I had not installed any. For the first time after many months, WU was quick to display the updates. It took less than 10 minutes. I thought it was going to take a long time but it didn't. I didn't install anything before running WU, the only thing different that I did was change the activation of the screen saver from 3 minutes to 300 minutes. I ran WU right before the beginning of the third quarter of the NBA's Finals game, and at about half of the quarter, the window with the updates was showing up in the screen.

Bo

 

This has become absolutely ridiculous!

With my almost 5 year old W7 laptop the CPU consumption of svchost.exe, when the services that run the process just seemingly check few hours of updates and do nothing else, is almost constant of nearly 25%.

When you same time run some video feed etc. the CPU gets heated.

 

Installed KB3161664 on Vista x86 yesterday but CPU still stays at 100% while WU checks for updates. Honestly, I'm looking forward to when M$ ends support for Vista.