I'll use this version and trying to use WU when I finished installing the updates for get the december updates. Thanks
After use that program I can say that: All updates were installed successfully but Wu doesn't work again! I'll wait until the computer do something but I want WU working too because I need fetch the Office updates! Why MS do this to W7...
Every time I revisit this subject, it's a different result. Computer is Dell M4700 laptop. I don't recall where the source ISO is from. It contains all five versions of Windows 7 SP1 x64 - Home Basic, Home Premium, Professional, Ultimate and Enterprise. I always install Professional - that's what came on the machine and I activate with Daz as it installs the factory original activation, not the COA key. Test 1: Used Linux Mint 'Vitual Machine Manager". Spent 3 1/2 hours searching for updates, then I gave up. Test 2: Similar to above, but used the QEMU-KVM64 command line to install. Spent over 4 hour hours and got nothing. Test 3: Blew away all the partitions on my drive and did a fresh install of real, not virtual machine. In 23 minutes it detected and down loaded 51 updates. After installing and rebooting it detected and installed 5 more updates. I can not get it to detect any more updates, yet I know from previous fresh installs there were on the order of 200+ updates. So now I am more perplexed than ever. Why were the virtual machines ignored? Can the update servers differentiate between the two? Why does my real machine not detect any more updates? I know they exist.
"It's a big stinking pile of poo" Finally, a proven and technical explanation I can sink my teeth into!
Now WU works for me. I run the december pack of simplix and I installed the December updates with WU.
percutientem quendam de equo mortuo A few days ago I had a Win7 virtual machine running in Linux Mint. Went to update. Then I minimized it and forgot I left it running. 12 hours later I finally remembered it was running. When I restored it, there were the updates - piece of cake. Today, another Mint with Win7 virtual. Started the update scan at 5am. 5 hours, 45 minutes later, a massive 21 updates have been detected. (And the English translation of the Latin title of this post is what I am doing - "Beating a dead horse".
Hi Atari800X I have experienced the same problem. After the upgrade to windows 10, I've performed a clean install of win 7 professional sp1 (media refresh). Then I've installed KB3102810 and then I've run windows udpate (manual start). After ten minutes it has found about 158 udpates. I've do them, but when I come to update for framework 4 update remain stuck on "checking for update" forever. On another PC I've the same windows 7 installed from any months... and I've never do the upgrade to windows 10. In this PC windows 7 continue to find new updates and everythink seem to work in the right way. I have 2 conclusion: 1) there is a bug in windows udpate for the clean install 2) After the upgrade to windows 10, MS keep a code about your machine and do not allow you to do any update for win 7 (in this 2nd view MS want to kill win 7 or to not allow us to return to win 7 after the upgrade of the machine, neither through a clean install of the system). What do you think about my toughts? Thank you for your help.
i had lately lots of issues with broken .net 4.0 in 7 lately. i think ms fked up a .net patching. try disable built in .net then run the net cleanup tool (try safemode first then reboot and rerun regular mode) then re enable the built in .net then install 4.0 on top.. then try win updates or also install 4.5.1.. i think the .2 is the culprit with updates scanning for it and priors. but im sure other updates are broken since summer and telemetry cr4p
I have done another fresh install of windows 7 and I experience the same update problem. Do you have any news about?
Are you saying that MS has introduced a bad update (KB3006137) that create all these problems? In another forum I've read that MS has reduced the win7 server's load in order to improve the server with win10. Someone suggests me to keep the pc on "checking for update" and after 1 or 2 days stucked on it, the pc finally will find the updates. In conclusion it is only a problem connected with the update server ofr win 7. See this: /answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-7-64-bit-updates-broken/97a84935-bbf1-4b52-8e03-e1b670bfeec9?auth=1
Windows Update/Microsoft Update is a single web service for pretty much everything. Any version of Windows, servers, Office, Windows Phone, HoloLens, whatever. There is no such thing as a "Windows 7 update server". Only the app store has its own update service. Any slowness is going to be caused by a client-side issue.
Why the same fresh install on the same machine some months ago workerd well but now the same win7 install it is stucked on "checking for update"?? I've tried to do the same on three different PC and the results were the same. The ISO is correct, check it with SHA1. There will be a solution
Thank you very much for your help, as I suspected under these "update problems" there is the will of MS to overcome on windows 7 with the new windows 10. In this way I agree with you when you say that you're not very confident for a solution.
I don't know; in any case, I'd start with installing the latest WU client update (KB3112343). Contrary to popular belief it's not an evil update that gives you cancer or forces Windows 10 on you, but it may actually fix issues. I'd be interested in that as well, and I might do that when I have some time.
Sometime Security issues under internet options in Trust sites.. Make sure all Internet, Local intranet, Trust Sites, and Restricted Sites set to all defaults.. Sometime issues with WU and Internet Explorer 10 and 11.. Also 3rd party like Security Anti-Virus, maybe cause problems..
I too can confirm problems since last July...oh, that was Windows 10 release month... With Microsoft's deliberate, invasive and aggressive push (for months) against Windows 7 and 8.1 forcing the 10 upgrade... Windows 7 being the best operating system ever released, and running great with just a few hiccups for almost a 5 year period to last July...now this updates issue crap for 7 months, and MS hasn't even addressed it... There is no such thing as multiple coincidences, 'mistakes', or oops just another 'accident'- oh sorry 'bout that...not with problems that affect millions and are never (1)acknowledged, (2)addressed and worked on, (3) or resolved... Not in law enforcement, not in governments, and certainly not in multi-billion $ worldwide corporations! This IS Microsoft's doing. Controlled on the server end, and it's deliberate... If it walks like a duck...
In conclusion we have 2 main solutions: 1) to use Simplix update after a fresh install of win7 or integrating it into the ISO 2) to use WSUS offline launching all the updates after a fresh install of win7. I think that MS win7 is destined to disappear under the will of MS Win10!-.-