Tripredacus Posted June 21, 2016 Posted June 21, 2016 This is also a problem on WES7e/p (Windows Embedded Standard) builds. Typically, clients wanting a custom Embedded image do not want updates to be installed, or for Windows Update to be disabled. The past week I've been working on two new WES7 builds to include updates and they both took on average 3-4 hours to complete the check. I had set WU to disabled and then just did Check for Updates, because there is no point in having it do the download since the updates are not added directly to the client.
erpdude8 Posted June 22, 2016 Posted June 22, 2016 (edited) On 5/15/2016 at 1:19 PM, dencorso said: @Yzöwl: Are you sure you've got the latest WindowsUpdateAgent? You might as well update it, if in doubt. It's harmless, if not needed, you know. That WUA app is v7.6.7600.320 for Win7 SP1, dencorso - that same package also includes v7.6.7600.256 for WinXP SP3, Vista SP2 & Win7 RTM/SP0 as I checked myself. That did nothing to solve the WU problem and is kinda outdated; but this newly released KB3161608 Update Rollup of June 2016 is what actually fixed the problem - KB3161608 updates the Windows Update Agent app to v7.6.7601.23453 and is now the latest version for Win7 SP1 Quote from Microsoft support KB article 3161647 - the KB3161647 fix is included in KB3161608: Quote This update contains some improvements to Windows Update Client in Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1. This includes the following: An optimization that addresses long scan time for updates that's reported on some computers. Fix for a Windows Update error 0x8007000E on some computers while they are updating. Some reliability improvements. . Took Microsoft several months to finally figure out and resolve the WU problem on Win7. Edited June 22, 2016 by erpdude8
dencorso Posted June 22, 2016 Posted June 22, 2016 Hi, erpdude8, long time no see! Glad to see you around! Thanks for the info: Quote KB3161608 updates the Windows Update Agent app to v7.6.7601.23453 and is now the latest version for Win7 SP1 That one's an important update, for sure!
bphlpt Posted June 22, 2016 Posted June 22, 2016 Are there any things in KB3161608 that those of us who are choosing to hide updates might not want? ie, is it "safe" tp install KB3161608 as is, or do we need to extract only the Windows Update Agent pieces of it? Cheers and Regards
dencorso Posted June 23, 2016 Posted June 23, 2016 I'll look into it further quite soon, and report... Later edit: Here's a list ow what's inside KB3161608... I'd sure be more confortable to recommend a standalone WUA...This rollup sure modifies a lot of low-level components, so a leap-of-faith (or good testing) is required. Quote codeintegrity_6.1.7601.23455 csrsrv_6.1.7601.23455 installer-executable_6.1.7601.23446 installer-engine_6.1.7601.23446 ncrypt-dll_6.1.7601.23455 installer-handler_6.1.7601.23446 lsa_6.1.7601.23455 lua_6.1.7601.23446 msauditevtlog_6.1.7601.23455 ntdll_6.1.7601.23455 ole-automation-legacy_6.1.7601.23452 os-kernel_6.1.7601.23455 rpc-http_6.1.7601.23455 ole-automation_6.1.7601.23452 rpc-local_6.1.7601.23455 smbminirdr_6.1.7601.23455 windowsupdateclient-activex_7.6.7601.23453 security-credssp_6.1.7601.23455 security-digest_6.1.7601.23455 security-kerberos_6.1.7601.23455 security-ntlm_6.1.7601.23455 security-schannel_6.1.7601.23455 smb10-minirdr_6.1.7601.23455 smb20-minirdr_6.1.7601.23455 windowsupdateclient-aux_7.6.7601.23453 smss_6.1.7601.23455 smss_7.1.7601.23455 systemrestore-main_6.1.7601.23455 windowsupdateclient-core_7.6.7601.23453 windowsupdateclient-ui_7.6.7601.23453 winsetupui_6.1.7601.23453 windowsupdateclient-internalupgrade_7.6.7601.23453 windowsupdate-adm_7.6.7601.23453 ole-automation-asyncfilters_6.1.7601.23452 advapi32_6.1.7601.23455 authentication-authui_6.1.7601.23446 boot-environment-windows_6.1.7601.23455 bcrypt-primitives-dll_6.1.7601.23455 cryptbase_6.1.7601.23455 boot-environment-os-loader_6.1.7601.23455 emb-boot-environment-windows_6.1.7601.23455 emb-boot-environment-os-loader_6.1.7601.23455 appid_6.1.7601.23455 1
PROBLEMCHYLD Posted June 24, 2016 Posted June 24, 2016 Thanks guys, I just created an Win 7 SP2 DVD using the Convenience Rollup and KB3161608. Windows Updates works with no problem now. This was a PITA and has been going on for a while. Thank God it's finally fixed.
jaclaz Posted June 24, 2016 Posted June 24, 2016 1 hour ago, PROBLEMCHYLD said: Thanks guys, I just created an Win 7 SP2 DVD using the Convenience Rollup and KB3161608. Windows Updates works with no problem now. This was a PITA and has been going on for a while. Thank God it's finally fixed. To be picky that is NOT a SP2 DVD (MS terms are already confusing enough, let us not add to the mess, if possible). A Windows 7 SP2 will only exist when (IF) the MS guys will release a Service Pack 2, what you made is still a SP1 fully updated to June 2016. jaclaz
PROBLEMCHYLD Posted June 24, 2016 Posted June 24, 2016 What if Microsoft is using the term Convenience Rollup to replace Service Pack????? IDK, just happy I don't have to download tons of updates.
jaclaz Posted June 24, 2016 Posted June 24, 2016 The Convenience Rollup is very different from a Service Pack: 1) it is NOT cumulative 2) it needs - besides "itself" AND the previous SP1 - a specific update as a prerequisite 3) it is not "all inclusive", what is inside it is a subset (the most relevant) of updates issued after SP1 Calling it SP2 is - besides inaccurate - giving it a "dignity" that it completely lacks. But if you are happy calling things NOT with their names, you are very welcome to do so, of course :). jaclaz
coucou Posted August 3, 2016 Posted August 3, 2016 Windows 7 SP1 Windows Update stuck checking for updates Tested on 2 computers... solved all the updates problems
NoelC Posted August 3, 2016 Posted August 3, 2016 Not to be picky, but there are multiple solutions proposed over there... Which one did you find effective? The highest upvoted one? -Noel
coucou Posted August 3, 2016 Posted August 3, 2016 (edited) The effective one is in my post Edited August 3, 2016 by coucou
NoelC Posted August 3, 2016 Posted August 3, 2016 Perhaps we have a language barrier problem... Your post points to a SuperUser forum thread with several proposed solutions. They are not all the same. For what it's worth I no longer have the slow updates problem, and I'm not looking at installing a fresh Win 7 any time soon, so I don't really care personally about the answer. I was just trying to ask the question that might be in others' minds when they read your post. -Noel
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now