Microsoft intentionally sabotaging Windows 7, by making Windows Update unbearable??

[escrow4]

The very first updates to a new system take longer than normal.

But dude. I do, do this all day long. I work on 10-40 PCs a day, not all of them need an update and not all are even win 7. But I have wide ranging experience seeing windows updates occurring. I watch windows 7 update no less than lets say..3 times a day. No less. And this is usually AFTER the person has called for some kind of problem possibly malware, and I have cleaned the pc and now am updating java and flash and reader etc. Then I check for updates. And these are old people who dont do their updates. So there are a few. And Im connected to them remotely. Online. If Im connected for a TOTAL of more than 2 hours my employer doesnt like that. So I can malware clean and windows update most PCs in less than 2 hours TOTAL.

if not...there is some kind of problem I cannot address.

But what is more likely?
That microsoft is engaged in what would be a scandalous conspiracy to make win updates for win 7 slow.

Or that the problem is somehow local to you?

Especially considering that people with lots of experience with windows 7 updates are not also having the problem you are.

Im not some windows lover. I dont really like win 10. The PC im on now is win 7 and I prefer android mostly lol.
<snip>

That is the problem. Java, flash and reader are trash. The first 2 shouldn't be installed on a modern system anymore and the third can be replaced free with PDF X-Change Viewer.

 

[thewhat]

Updates in 7 have been broken for about a year or so. Broken meaning that checking for updates uses a lot of CPU and RAM and takes longer than it should.
It's probably not broken on every system, which is why LPCTech hasn't seen it, but it's there. Check this thread, for example.

It has been acknowledged by Microsoft and they released some fixes, but apparently they didn't fix it completely or for all users.

I've seen this issue on a few PCs myself and I recommend to disable automatic updates check on weak PCs, because it can be quite annoying and render a PC barely usable for 10 minutes every day. The updates are issued only once a month for the most part, so it shouldn't be a big deal.

Is this intentional or simply incompetence? I'm leaning towards the latter, but we can only speculate. With Microsoft being as desperate as they are, you never know.

 

[LPCTech]

That is the problem. Java, flash and reader are trash. The first 2 shouldn't be installed on a modern system anymore and the third can be replaced free with PDF X-Change Viewer.

im working on another persons pc i have to do what they want. and other than java, i agree.

 

[johnno]

It's a pain. We have four machines in the house. My win7 desktop that updates like it always has. Win 10 lappy with no issues. My old Vista desktop that will not receive any updates any more, was fine a few months ago. A new install also makes no difference and it is just endlessly searching for updates. And finally a crappy netbook with win 7 starter that also stopped receiving updates since November, again just endlessly searching.

 

[LPCTech]

just a tip: if you are having update issues, I have found that at least on win 10(I havent tried this with win 7 but Im betting it works the same) if you go to the folder:

"C: \Windows\SoftwareDistribution\Download" and delete everything in it (dont delete the folder just whats in it)

then reboot and run win update again. Sometimes that can help.

If it helps it means that somehow whatever was in there was corrupted in some way and this makes windows download it again.

Again, I have never tried this with win 7, only win 10 where it works great every time. Couldn't hurt to try.

 

[tcsenter]

That's simply not true. Windows update, on fully-functional modern hardware (Haswell Celeron with 16GB RAM), with an internet connection of at least 50Mbit/sec, using a DVD burned and verified OK, from an ISO of Win7 HP 64-bit SP1-U, downloaded from Digital River (before they were pulled), still takes OVER TWO HOURS, during the first Windows Update session, before it presents the list of updates available. This is fact.

KB3102810: Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2

Restart then try again. Works for me. Then use Edit Group Policy to set/enable "Turn Off The Upgrade to the Latest Version of Windows Through Windows Update". It won't stop the GWX icon or control panel from loading (which you can hide in notification) but it will NOT download the install bits for W10, and won't pop-up on you, anymore.

Also don't forget System Update Readiness Tool if you still have problems.

 

[postmortemIA]

KB3102810: Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2

Restart then try again. Works for me. Then use Edit Group Policy to set/enable "Turn Off The Upgrade to the Latest Version of Windows Through Windows Update". It won't stop the GWX icon or control panel from loading (which you can hide in notification) but it will NOT download the install bits for W10, and won't pop-up on you, anymore.

Also don't forget System Update Readiness Tool if you still have problems.

I have that update installed for over 2 months, and problem didn't go away. It wouldn't be first time that MS (or any other company for that matter) admits to an issue, then publish the fix that does not completely fix the issue.

 

[tcsenter]

I have that update installed for over 2 months, and problem didn't go away. It wouldn't be first time that MS (or any other company for that matter) admits to an issue, then publish the fix that does not completely fix the issue.

Which one, the Windows Update Client update or System Update Readiness Tool? This appears to be the latest client update, replacing the prior one I linked: https://support.microsoft.com/en-us/kb/3112343

 

[MongGrel]

About guinea pig time for me again.

Another new version of Win 10 dropping.

Announcing Windows 10 Insider Preview Build 11082

http://www.neowin.net/news/microsof...review-build-11082-its-first-redstone-release

http://www.neowin.net/news/edge-alr...ns-support-in-windows-10-redstone-build-11082

I'm up to insider build 14257 in Windows 10 now.

Has taken a bit of fighting here and there, to get a few things to play nice, but its stable on the main rig, atm.

Not sure why some people fight progress I guess.

There is such a thing as being overly paranoid.

 

[MongGrel]

14271 time, youks and away.

*edit* working fine at the moment, maybe I should start an insider thread.

Every time I do that I almost expect the computer to come up singing "Bicycle built for Two"

Almost has a few times in the past.

 

[MongGrel]

Have Windows 10 insider build 14291 running now, it has actually fixed a few minor problems I was having with 14271.

Overall, it seems a very nice improvement.

It seems some programs I run in the background do not crash the system over hours like it used to now and then, it's getting more stable.

Even file transfers have went back being more stable and faster than they have been in the past.

 

[postmortemIA]

Every Tuesday Patch, WU takes one core away... this time it has been stuck for days, unable to find updates but still utilizing one core 100%.

 

[fr]

Did a clean install yesterday and pulled my hair out for hours wondering why I couldn't get any updates installed. Couldn't install .NET Framework 4.0 either to get an app I needed running. Had to install missing drivers the old fashioned way. Ugh. I installed KB 3083710, 3102810, and 3138612 but it changed nothing.

 

[ratjacket]

the best workaround I have found is once you hit the wall with manual updates.

Is set it to automatic (download but manually install) and leave it to run overnight this seems to get the last lot of updates through.

it only makes it take a day longer than it should :'(

 

[nerp]

Yeah, turn on automatic updates and stop trying. They'll trickle in eventually. Best approach is no approach.

One trick is to nuke any system restore points. That should speed things up.

 

[postmortemIA]

Looking at most helpful reply on a topic at answers.microsoft.com
it seems that as you install more updates, it will cause next update cycle to be slower. In other words, as we approach last years of Windows 7 support, this is going to be even bigger problem.

 

[TeknoBug]

Still got Win 7 Pro on one of my laptops, I've had 0% progress sitting there for hours a few times but yeah updates are sloooooowwwww.

 

[Mem]

Still got Win 7 Pro on one of my laptops, I've had 0% progress sitting there for hours a few times but yeah updates are sloooooowwwww.

My Win7 PCs got upgraded many years ago, even my old XP PC got upgraded to Linux decades ago, one thing about Linux I like is how fast updates are.

To be honest I never had to wait for any Linux updates to the OS over the years compared to Windows.

I guess that is due to Windows being more popular, even with all those servers Microsoft have.

 

[VirtualLarry]

I had need to refurb a Q9300 rig (that's a 2.5Ghz Core2Quad, for those that don't know). With a 50GB Vertex2 SSD, and a fresh install of Win7 64-bit SP1.

I got the various drivers installed, then I went to do Windows Update. It was set to "do not do anything - manual mode". So the first time I clicked check for updates, it had to update WU itself, which happened fairly quickly. Then it came back, and said "Searching for updates", and I let it run while I slept, finally, when I woke up, it had a list of 177 updates. I have a specific order I do them in, so I did the .Net framework updates first, then I rebooted, then I started the WU "Searching" grind again. It's been searching since 4:30PM EST-ish, and it's 7:30PM EST. Still searching. Sigh.

One core of my Q9300 has been pegged the whole time.

Edit: It finished searching five minutes after posting that, so I did the security updates, and then rebooted, and then searched again. That time, it didn't spend more than five minutes again searching for the non-security, non-net-framework updates. I did those updates, including whatever the revised SP1 update was, and the IE11 update.

So I did those updates, and now I'm searching for more post-IE11 updates. (Sometimes there are a few.) But this time, it's taking a bit of a longer time again. (More than five minutes.)

Edit: More like 30 minutes to search for post-IE11 updates. Found 8 security updates, and of course, the MSRT. What a joke that is.

 

[Ketchup]

I had need to refurb a Q9300 rig (that's a 2.5Ghz Core2Quad, for those that don't know). With a 50GB Vertex2 SSD, and a fresh install of Win7 64-bit SP1.

I got the various drivers installed, then I went to do Windows Update. It was set to "do not do anything - manual mode". So the first time I clicked check for updates, it had to update WU itself, which happened fairly quickly. Then it came back, and said "Searching for updates", and I let it run while I slept, finally, when I woke up, it had a list of 177 updates. I have a specific order I do them in, so I did the .Net framework updates first, then I rebooted, then I started the WU "Searching" grind again. It's been searching since 4:30PM EST-ish, and it's 7:30PM EST. Still searching. Sigh.

One core of my Q9300 has been pegged the whole time.

Yeah. Let the first update run 'till its done. You don't want to sit through that wait any more times than necessary.

 

[VirtualLarry]

Yeah. Let the first update run 'till its done. You don't want to sit through that wait any more times than necessary.

I do it in multi-parts, because I've run into issues with RAM limits doing all of the updates at once, and I've read comments from others on here that they had issues with updates failing and reverting (wasting more time), if they tried to do all of them in one shot. My method seems to work for me. (No failed updates.) It just requires waiting through the searching process several times. Sigh.

 

[Ketchup]

I do it in multi-parts, because I've run into issues with RAM limits doing all of the updates at once, and I've read comments from others on here that they had issues with updates failing and reverting (wasting more time), if they tried to do all of them in one shot. My method seems to work for me. (No failed updates.) It just requires waiting through the searching process several times. Sigh.

I was going to say, the initial wait is the worst part. I have done at least a dozen fresh installs since this thing started, and letting it all go at once is the best way to go. Because every search thereafter will only be a matter of minutes (vs. hours). A couple updates failing on the first run (it's either 2 or 3 on the first run) is not the worst thing in the world.

 

[escrow4]

I do it in multi-parts, because I've run into issues with RAM limits doing all of the updates at once, and I've read comments from others on here that they had issues with updates failing and reverting (wasting more time), if they tried to do all of them in one shot. My method seems to work for me. (No failed updates.) It just requires waiting through the searching process several times. Sigh.

Should have installed 10. You can install the 1511 build to a 8GB USB and use that to reinstall at will. Creaky 7 now in 2016 with all those updates bleh.

 

[VirtualLarry]

Should have installed 10. You can install the 1511 build to a 8GB USB and use that to reinstall at will. Creaky 7 now in 2016 with all those updates bleh.

Maybe... but what if I want 7? Or eventually, a licensed copy of 10? Gotta install 7 first. (*)

(*) Because this is a Windows 7 Family Pack, I am unsure what will happen to the license key, if it is "used up" by installing Win10 1511 using that key directly. If I install Win7 first, then I can install and activate THREE machines, as per the license agreement, and then upgrade ALL of them to Win10.

 

[BarkingGhostar]

I do not have updates turned on to automatic, nor to notify me. I'm a big boy.

Anyway, when I do check, which was two days ago, I noticed a bunch. I think I selected 'n-1' of them, the '1' being a phishing scam to W10, and when I selected Install the update program just sat there. Nothing happened.

I went to breakfast (restaurant) and came back and still nothing. I cancelled, rebooted and selected one friggen item. Just one. And it sat there. I walked away and only after another hour did it actually install that one item. Of the remaining items, again I selected 'n-1' and within seconds the Update ran like an f-ing cheetah and did its job.

Craziness is not acknowledging that this isn't necessary, but that M$ is trying to punish us W7 users.