manuel_ritz
Junior Member
This is such a great help for those newbie here and don't know what to do whenever there's an update. But, if we delay the update do you think this will affect some programs?
Thats around the time MS released updates to fix slow update problems and one patch was replaced because it caused trouble.I didn't start having problems with it until july, seem's too coincidental
Win10 has problems with updates too, even if it isn't as serious. But its larger updates which are really upgrades have caused alot of trouble for many people and updates in Win10 cannot be delayed or stopped without some complicated tinkering unless you have the Enterprise edition......
But I grabbed a copy of windows 10 Pro and got everything running as smooth as butter. Now 7 just feels so dated and with the support starting fall off my days of 7 are now behind me.
It depends on the error, I recall there was a specific issue with Autocad 2015 when installing if you had something newer than 4.0.Hey is there any fix for Net Frame 4.0 update? I have to install autocad 2013 on my pc, it has windows 7 and its giving me Net frame 4.0 error. I don't know why coz I have Net Frame 4.0 installed. I have checked msscore file in my system file and read the properties too. It says I have Net Frame version 4.0 installed. Yet I face the same error, over and over again..
Help?
Did you install the latest Windows Update Agent after resetting components? Then also try installing the July 2016 rollup: https://support.microsoft.com/en-us/kb/3172605Just ran the Win7 version of the "update fixer " ( [URL said:https://support.microsoft.com/en-us/kb/971058[/URL] ) --- dont use this tool.
Don't use the automatic 'fix-it' use the standalone package above it.I'm looking at your link ... and the " download" fix-it has been disabled.
My Win Update version ( Wuaueng.dll ) is for my Win7 x64 is 7.6.7601.19046
Don't use the automatic 'fix-it' use the standalone package above it.
See Dahak's post above, this is currently the best order of things to get WU working on it's own after clean install of W7 /SP1. I've use those recommended patches in that order now about four times and it works.
There are many threads with the same problem, here is the solution that worked for me:
1. disable updates, set it to never check
2. restart
3. install this manually: https://support.microsoft.com/en-us/kb/3102810
(direct links
32Bit: http://www.microsoft.com/downloads/details.aspx?FamilyId=fcd6bf5d-f004-4ca3-aa7e-1de462b91dd0
64Bit: http://www.microsoft.com/downloads/details.aspx?FamilyId=4fe566bd-31b1-4413-8c4c-412b52533669
4. restart
5. install updates normally now, either set to automatic check or manually check ..etc.
----
the link https://support.microsoft.com/en-us/kb/3102810 says:
Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2
Issue 1
When you install updates by using System Center Configuration Manager, the installation takes a long time, and System Center Configuration Manager becomes overloaded.
Issue 2
The Svchost.exe process occupies 100 percent of CPU usage when you upgrade a Windows Update client to Windows 10.
Yeah, I wish they had just released a Service Pack 2. It would save a lot of bandwidth.Thanks that fixed my problem!
But whoa now there's 215 updates to do. lol that sounds very wrong!
Yeah, I wish they had just released a Service Pack 2. It would save a lot of bandwidth.
For Windows 7 Windows Update Issues, this is what I have been doing lately.
1- Download the following files
1a - Latest WU Client https://support.microsoft.com/en-us/kb/949104
b - KB3177467 32-bit 64-bit
c - KB3172605 32-bit 64-bit
d - KB312557 Microsoft Catalog Update Site
Once those 4 are downloaded. Disconnect from the internet, either unplug the cable or disable the network/wireless adapters
Install the patches in order and REBOOT after each. It does not seem to work properly if you do not reboot
Then it should not take very long to search for updates, ive seen it drop down to about 10-15 min, at most probably 30min but never timed it
With WU service stopped, the installer's preliminary "Searching for updates on this computer ..." phase flashed by in a second or two - no interminable hang. In the past I've let it sit up to 5 hours, hoping for completion.@FeuerFrei -- Would quote but it seems to be broken. -- I have been reading that some posts lately around the web that stopping the service seems to work now too. Usually I just set my WU to never search and that is usually enough but good to know in the future that maybe stopping the WU service would be a good idea too