Update WUA on Windows 7 SP1 Clients to 7.6.7600.320

Hi All
We have an SCCM 2012 R2 CU 2 environment with a CAS and a Primary Server
One SUP (SUP1) is connected to the internet and is used as upstream server for another SUP Server (SUP2) , our clients connect to SUP2
Our clients are all Windows 7 SP1 , the SUP servers run “Windows Server Update Services 3.0 Service Pack 2 (SP2)”
I noticed the following article to update the WUA on my client computers to version 7.6.7600.320
http://blogs.technet.com/b/configmgrteam/archive/2014/07/14/how-to-install-the-windows-update-agent-on-client-computers.aspx
But I don’t want to update this agent with a package but I want to update this agent with the WSUS/SUP functionality of automatically update this client to the newest version
Is the following approach valid ?
Download Update for Windows Server Update Services 3.0 SP2 (KB2938066) http://www.microsoft.com/en-us/download/details.aspx?id=43633
Install this update on our SUP1 (connected to the internet)
Synchronise
Install this update on our SUP2
Synchronise
Afterwards the clients will connect to SUP2 and will install the newest WUA 7.6.7600.320 automatically
I hope someone can answer this if this approach is valid?
Thx in advance
Regards
Johan

We have an SCCM 2012 R2 CU 2 environment with a CAS and a Primary Server
But I don’t want to update this agent with a package but I want to update this agent with the WSUS/SUP functionality of automatically update this client to the newest version
Is the following approach valid ?
Download Update for Windows Server Update Services 3.0 SP2 (KB2938066) http://www.microsoft.com/en-us/download/details.aspx?id=43633
Install this update on our SUP1 (connected to the internet)
Synchronise
Install this update on our SUP2
Synchronise
Afterwards the clients will connect to SUP2 and will install the newest WUA 7.6.7600.320 automatically
This is exactly what you need to do.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

Windows 7 SP1 client shows status of "Not Applicable" for every single update

Windows 7 SP1 client
Every update, including all Critical Updates for Windows 7, show a status of "Not Applicable" when running a "Computer Detailed Status Report"
The computer is current in updating its status with the WSUS server.
I am hoping that you can suggest reasons why this would be.
Thanks!
mk

It is only the one computer that has all of its updates listed as 'Not Applicable'
Some of these are the same updates that other computers show as 'Installed'
Any other ideas?
Yep!
Every update, including all Critical Updates for Windows 7, show a status of "Not Applicable" when running a "Computer Detailed Status Report"
The computer is current in updating its status with the WSUS server.
One of those two statements is not true.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Windows 7 SP1 client file lock on network share hosted ny WIndows 2012 Server

Hello
I have one strange problem after migration from Windows 2003 Server to Windows 2012 Server R2 Standard.
All migration tasks went well but two things do not work.
In Computer Management you have The Opened Files feature and if you open any file that is located on the network share hosted by Windows 2012 R2 form Windows 7 SP1 and then close it
it remains open in the Opened Files tab (even if you wait an hour). There is no problem with Windows XP SP3. The issue exist only with Windows 7.
The session view of sessions to the file server do not work. If I try to open it I get the message that the application is not responding.
Can someone help me with that ?
About the environment:
It is one server Domain migrated form 2003 to 2012R2.
The domain and forest level was raised to 2012 R2.
I have made clean install of Windows 2012 R2 and then migrated AD.
Best Regards
Sebastian Sala

Hi Sebastian,
>>There is no problem with Windows XP SP3. The issue exist only with Windows 7.
T>>he session view of sessions to the file server do not work. If I try to open it I get the message that the application is not responding.
Based on the description, please check event logs in Event Viewer to see if there were some related events logged. Besides, does this phenomenon happen all Windows 7 clients? We can try to restart the client to see if it helps.
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Cleanup WinSxS folder of Windows 7 Sp1

Microsoft released an update to cleanup WinSxS.
Go this this KB article and install the update:
Update is available that enables you to delete outdated Windows updates by using a new option in the Disk Cleanup wizard in Windows 7 SP1
http://support.microsoft.com/kb/2852386
When you now launch the disk cleanup (as admin) you get an option "Windows Update Cleanup":
Click ok to start cleanup. now you must reboot Windows 7. After the reboot you get a screen which shows you that cleanup happens:
You can get more information here:
Breaking News! Reduce the size of the WinSxS Directory and Free up Disk Space with a New Update for Windows 7 SP1 Clients
http://blogs.technet.com/b/askpfeplat/archive/2013/10/08/breaking-news-reduce-the-size-of-the-winsxs-directory-and-free-up-disk-space-with-a-new-update-for-windows-7-sp1-clients.aspx
"A programmer is just a tool which converts caffeine into code"

Horinius - you have to reboot for the clean up to occur. WHen I did, it cleaned up the amount of disk space that the Cleanup manager said, but my winsxs folder had about 8 GB more, most of which is files and folder that at 3+ years old. My theory is that
this is garbage that my IT department left behind when they build the standard image.
Anyone know how to delete the rest of the trash in WinSxS?
Of course we have to reboot for the clean up. Did I say we didn't have to?
If you want to do the "Windows Update cleanup" (as specified in the original post), there's no need to use this "Cleanup manager". You just need to open "C:\Windows\SoftwareDistribution\Download" and delete everything inside it.
Please read carefully my posts before commenting.

Windows Management Framework 3.0 does not install on Windows 2008R2 SP1 Server

I have tried to Install the below update on my Windows 2008R2 SP1 Server and I get error as illustrated
http://www.microsoft.com/en-us/download/details.aspx?id=34595
64-bit versions: Windows6.1-KB2506143-x64.msu
Below is the Error Message I gathered from the Event Viewer
ErrorCode 2149842967
ErrorString
CommandLine "C:\Windows\system32\wusa.exe" "E:\IT\2008R2SP1\Windows6.1-KB2506143-x64.msu"
As per below screenshot, .NET V4 is already installed. Am I missing something?

Sorry I missed it.
Did you go through the 'System Requirements' in the download section ?
If Yes and if your machine has met all pre-requisites and still not able to install WMF 3.0 then you can submit your feedback here:
http://connect.microsoft.com/PowerShell
P.S. found few related questions already asked..hope you have gone through them already before asking the question here :
http://social.technet.microsoft.com/Forums/windowsserver/en-US/56c6ac4e-d7ba-4308-a4de-d4ca45325e65/windows-management-framework-30-install-showing-as-not-applicable?forum=winservermanager
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c85adc4e-d3ad-460a-8e2e-7c6b1e32e7d7/windows-management-framework-30-installation-error?forum=sharepointadmin
Knowledge is Power{Shell}
DexterPOSH
My Blog

Windows Update Error 80080005 Windows 7 Client with WSUS 3.0 SP2 server

Hello everyone, I've looked around at other threads related to my issue, and I can't seem to find a correct answer.
I have a computer lab that I've recently installed a Windows 7 Enterprise image onto 35 Dell Optiplex computers (most are 380's, a few older 360's).
I created the image using MDT2010 and used one of the 380's as a reference.
All has been well for about a month or two but recently 6 computers are giving me Windows Update errors with the error code of 80080005.
I have a WSUS 3.0 SP2 server running, and all of my other computers seem to be getting their updates just fine. WSUS has the problematic computers in it's database, but it shows that they haven't checked in for "x" days.
I have Avast 4.8 Professional installed, I have OpenDNS configured to block bad websites, ____, etc. and I also use an Untangle server to prevent access to bad websites. I've ran a Malwarebytes' Anti-Malware scan on the affected computers, as well
as Windows Defender scan, and Windows Live OneCare scans, and all have found no malicious software.
I have also tried resetting the Windows update service as described here: http://support.microsoft.com/kb/971058 as well as a script that supposedly does the same thing, but also resets all previous
update events, but I can't find the script source right now (I had ran it last week, and it didn't work).
I'm currently running a SFC /Scannow on one of the computers, and now it has finished. It gives the error: Windows Resource Protection could not start the repair service. I'll have to google that next.
The last windows update that ran on the computer that I'm working on now was installed on 11-18-2010 and was a Windows Defender Update (KB915597 Def: 1.93.1985.0)
Previous to that was 11/9/2010 2 updates: KB977165 and KB981852.
I guess I'll have to look at all of the other machines to see if they have the same updates installed.
Anyway, has anyone else had this problem? I've seen vista home editions, and RC's but no real Windows 7 Pro+ RTM versions in business environments where updates were controlled by WSUS.
Thanks for any help that you can provide!
By the way, I only work at this location once a week (tuesdays, well thursdays too, but I'm next door to this building, but I have remote access), so bare with me on trying to fix things.

Ok, for the sake of completeness, I have completed the instructions given by Miya Yao.
After stopping the Windows Update Service (from an Admin Command prompt window), renaming the SoftwareDistribution folder to SDold, then starting the update service again, I still receive the same error when checking for updates.
The windows update log shows this (starting from about 4am) and I just reset the service at about 9:10, which you can see in the log.
2010-12-21 04:19:02:342 940 f20 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 04:19:02:342 940 cd4 AU >>## RESUMED ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 04:19:02:342 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 04:19:02:342 940 cd4 AU #########
2010-12-21 04:19:02:342 940 cd4 AU ## END ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU #############
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU AU setting next detection timeout to 2010-12-21 14:19:02
2010-12-21 04:19:02:342 940 cd4 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:07:350 940 f20 Report REPORT EVENT: {A472759C-BEE7-4161-84E8-41F1C1D03AB4} 2010-12-21 04:19:02:342-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 04:19:07:350 940 f20 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 04:19:07:350 940 f20 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 04:19:07:350 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:24:22:767 940 f20 PT WARNING: Cached cookie has expired or new PID is available
2010-12-21 04:24:22:767 940 f20 PT Initializing simple targeting cookie, clientId = a6d6dc1c-d844-451c-8609-3879e6cacb33, target group = , DNS name = lab24.sja.local
2010-12-21 04:24:22:767 940 f20 PT Server URL = http://server2:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-12-21 04:24:22:814 940 f20 Report Uploading 2 events using cached cookie, reporting URL = http://server2:8530/ReportingWebService/ReportingWebService.asmx
2010-12-21 04:24:22:814 940 f20 Report Reporter successfully uploaded 2 events.
2010-12-21 06:59:23:020 940 b4c AU AU was unable to detect updates for more than 48 hours
2010-12-21 06:59:28:027 940 c78 Report REPORT EVENT: {511B1C92-939C-4E97-A51B-50E75FCB7AEF} 2010-12-21 06:59:23:020-0500 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
2010-12-21 06:59:28:027 940 c78 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:02:03:476 940 2f4 AU Triggering AU detection through DetectNow API
2010-12-21 09:02:03:476 940 2f4 AU Triggering Online detection (interactive)
2010-12-21 09:02:03:476 940 b4c AU #############
2010-12-21 09:02:03:476 940 b4c AU ## START ## AU: Search for updates
2010-12-21 09:02:03:477 940 b4c AU #########
2010-12-21 09:02:03:488 940 b4c AU <<## SUBMITTED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:03:488 940 e38 Agent *************
2010-12-21 09:02:03:488 940 e38 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:03:488 940 e38 Agent *********
2010-12-21 09:02:03:488 940 e38 Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:02:03:488 940 e38 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:02:03:488 940 e38 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:02:03:488 940 e38 Agent * Search Scope = {Machine}
2010-12-21 09:02:03:488 940 e38 Setup Checking for agent SelfUpdate
2010-12-21 09:02:03:489 940 e38 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:02:03:489 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:03:496 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:071 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:06:078 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:080 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:087 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:100 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:107 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:123 940 e38 Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:02:06:123 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2010-12-21 09:02:06:129 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:129 940 e38 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
2010-12-21 09:02:06:129 940 e38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:02:15:386 940 b4c AU AU received policy change subscription event
2010-12-21 09:02:36:165 940 e38 Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent *********
2010-12-21 09:02:36:165 940 e38 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:36:165 940 e38 Agent *************
2010-12-21 09:02:36:165 940 e38 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:02:36:165 940 e8c AU >>## RESUMED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:02:36:165 940 e8c AU #########
2010-12-21 09:02:36:165 940 e8c AU ## END ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU #############
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU AU setting next detection timeout to 2010-12-21 19:02:36
2010-12-21 09:02:36:165 940 e8c AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:41:172 940 e38 Report REPORT EVENT: {678C2913-B3B3-4F14-9310-C2E2B1F3334A} 2010-12-21 09:02:36:165-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 09:02:41:172 940 e38 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 09:02:41:172 940 e38 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 09:02:41:172 940 e38 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:07:779 940 b4c AU ########### AU: Uninitializing Automatic Updates ###########
2010-12-21 09:06:37:809 940 b4c Handler FATAL: UH: 0x80080005: StartSession failed in CCbs::IsCbsPending
2010-12-21 09:06:37:840 940 b4c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:37:872 940 b4c Service *********
2010-12-21 09:06:37:872 940 b4c Service ** END ** Service: Service exit [Exit code = 0x240001]
2010-12-21 09:06:37:872 940 b4c Service *************
2010-12-21 09:08:37:104 940 e84 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0500) ===========
2010-12-21 09:08:37:104 940 e84 Misc = Process: C:\Windows\system32\svchost.exe
2010-12-21 09:08:37:104 940 e84 Misc = Module: c:\windows\system32\wuaueng.dll
2010-12-21 09:08:37:104 940 e84 Service *************
2010-12-21 09:08:37:104 940 e84 Service ** START ** Service: Service startup
2010-12-21 09:08:37:104 940 e84 Service *********
2010-12-21 09:08:37:108 940 e84 Agent * WU client version 7.4.7600.226
2010-12-21 09:08:37:108 940 e84 Agent * Base directory: C:\Windows\SoftwareDistribution
2010-12-21 09:08:37:108 940 e84 Agent * Access type: No proxy
2010-12-21 09:08:37:108 940 e84 Agent * Network state: Connected
2010-12-21 09:08:37:453 940 e84 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2010-12-21 09:08:37:462 940 e84 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2010-12-21 09:08:37:464 940 e84 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
2010-12-21 09:08:37:464 940 e84 Agent WARNING: Invalid service in the backup data store; cleaning up
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Failed to add and register service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Default Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
2010-12-21 09:09:22:474 940 e84 Report CWERReporter::Init succeeded
2010-12-21 09:09:22:474 940 e84 Agent *********** Agent: Initializing Windows Update Agent ***********
2010-12-21 09:09:22:475 940 e84 Agent *********** Agent: Initializing global settings cache ***********
2010-12-21 09:09:22:475 940 e84 Agent * WSUS server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * WSUS status server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * Target group: (Unassigned Computers)
2010-12-21 09:09:22:475 940 e84 Agent * Windows Update access disabled: No
2010-12-21 09:09:22:475 940 e84 DnldMgr Download manager restoring 0 downloads
2010-12-21 09:09:22:476 940 e84 AU ########### AU: Initializing Automatic Updates ###########
2010-12-21 09:09:22:477 940 e84 AU # WSUS server: http://server2:8530
2010-12-21 09:09:22:477 940 e84 AU # Detection frequency: 22
2010-12-21 09:09:22:477 940 e84 AU # Approval type: Scheduled (Policy)
2010-12-21 09:09:22:477 940 e84 AU # Scheduled install day/time: Every day at 3:00
2010-12-21 09:09:22:477 940 e84 AU # Auto-install minor updates: Yes (Policy)
2010-12-21 09:09:22:478 940 e84 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:09:22:751 940 e84 Report *********** Report: Initializing static reporting data ***********
2010-12-21 09:09:22:751 940 e84 Report * OS Version = 6.1.7600.0.0.65792
2010-12-21 09:09:22:751 940 e84 Report * OS Product Type = 0x00000004
2010-12-21 09:09:22:772 940 e84 Report * Computer Brand = Dell Inc.
2010-12-21 09:09:22:772 940 e84 Report * Computer Model = OptiPlex 380
2010-12-21 09:09:22:775 940 e84 Report * Bios Revision = A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Release Date = 2010-03-11T00:00:00
2010-12-21 09:09:22:775 940 e84 Report * Locale ID = 1033
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:777 940 e84 AU Initializing featured updates
2010-12-21 09:09:22:777 940 e84 AU Found 0 cached featured updates
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU AU finished delayed initialization
2010-12-21 09:09:27:781 940 36c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:10:20:421 940 bf0 AU Triggering AU detection through DetectNow API
2010-12-21 09:10:20:422 940 bf0 AU Triggering Online detection (interactive)
2010-12-21 09:10:20:422 940 e84 AU #############
2010-12-21 09:10:20:422 940 e84 AU ## START ## AU: Search for updates
2010-12-21 09:10:20:422 940 e84 AU #########
2010-12-21 09:10:20:425 940 e84 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:20:425 940 36c Agent *************
2010-12-21 09:10:20:425 940 36c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:20:425 940 36c Agent *********
2010-12-21 09:10:20:425 940 36c Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:10:20:425 940 36c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:10:20:425 940 36c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:10:20:425 940 36c Agent * Search Scope = {Machine}
2010-12-21 09:10:20:425 940 36c Setup Checking for agent SelfUpdate
2010-12-21 09:10:20:426 940 36c Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:10:22:715 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:10:22:725 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:745 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:10:22:750 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:765 940 36c Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:10:22:765 940 36c Setup SelfUpdate handler is not found. It will be downloaded
2010-12-21 09:10:22:765 940 36c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:10:52:778 940 36c Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent *********
2010-12-21 09:10:52:779 940 36c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:52:779 940 36c Agent *************
2010-12-21 09:10:52:779 940 36c Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:10:52:779 940 ba0 AU >>## RESUMED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:10:52:780 940 ba0 AU #########
2010-12-21 09:10:52:780 940 ba0 AU ## END ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU #############
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:783 940 ba0 AU AU setting next detection timeout to 2010-12-21 19:10:52
2010-12-21 09:10:52:783 940 ba0 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:784 940 ba0 AU Successfully wrote event for AU health state:0

Windows 8.1 clients are not detecting updates deployed to them through SCCM 2012 R2

Hello,
We are using SCCM 2012 R2 to deploy software updates.
On Windows 8.1 SCCM does not show certain updates as being needed and isn't deploying them to the clients even though Windows Update will show them as high importance. These same updates are being detected and deployed to Windows 8 clients successfully.
I believe that the update catalog that WSUS uses may have some incorrect detection rules for the following updates:
2917933
2913320
2913270
2913152
2909569
2904440
2904266
2903939
2899189
2893984
2893294
2892074
2916626
2898785
My automatic deployment rules include Windows 8.1 in the product category. I have even created a standalone rule for Windows 8.1 that builds a new package and the behavior is the same.
We only have a handful of Windows 8+ clients so this hasn't been a big issue but others may want to keep an eye out.

I am also running into this issue. After "checking online for updates" on one of my machines in office I found that there were 21 important updates for my 8.1 box. When I cross reference them in SCCM under All Software Updates, it appears these
8.1 updates are not listed. They are however listed for all other OS.
10 seconds after typing this, I went in to verify my WSUS -> Products and Classifications settings and come to find 8.1 and 2012 R2 weren't selected, even though it's an option in SCCM. Go figure! This wasn't the end though. After
running a Synchronization, my issue still wasn't resolved. Went back to check my settings and they again were changed back to having these OS unchecked. Finally, a solution! I found that in SCCM, under Administration tab, Site Configuration
> Sites > ABC - Mysitename, right click and scroll down to "Configure Site Components" > Software Update Point. This setting (although the same as is in WSUS) takes precedence, thus was rolling my settings back to the original configuration
in WSUS.
So long story short, even though my automatic deployment rules stated approve all windows 7/8/8.1 criticals/importants, 8.1 was getting skipped for the most part because my WSUS server wasn't syncing with Microsoft for all of the updates I required. I
did have a couple of updates that squeezed through because they were categorized as "Security Updates for Windows 8, 8.1".
Not sure if this is the solution you were looking for, but your thread got me started in the right direction, hopefully this response helps in the same way!
Thanks!

No Sound from Old T61 Now Updated to Windows 7 SP1

I'm getting no sound (neither System Sounds nor from Windows Media Player) from either the speakers or the phone jack on this 6459-CTO. The speaker control icon in the notification area indicates sound levels on both the source and the speaker in each case. Device Manager says the device is working properly. I've tinkered with all the sound setting I can find to no avail. Can somebody give me troubleshooting instructions to test the hardware itself and, if that is working, to track down the problem?
The following are details that you may not need:
I started out with Windows XP and, at least at some point, had sound, though I usually kept it muted with the on-keyboard buttons. I just did a clean install of Windows 7 SP1 from an OEM installation disk. I know I was hearing the "Windows Startup Sound" on reboots and couldn't stand it, so I disabled it by enabling Local Group Policy Editor/Local Computer Policy/Computer Configuration/Administrative Templates/System/Logon/Turn off Windows Startup Sound. Then I ran ThinkVantage System Update, which among other things, installed Hotkey Features Integration and SoundMax Audio SoftwareSupport, including the driver ("SoundMax Integrateed Digital HD Audio" version 6.10.2.7255 by Analog Devices). I started fretting when the on-keyboard speaker-control buttons didn't work (see thread at http://forums.lenovo.com/t5/ThinkVantage-Technologies/Lenovo-Volume-Mute-Keys-Don-t-Work-after-Clean... but eventually discovered this more serious problem.
Now I've uninstalled the Lenovo-provided SoundMax driver under Programs and Features and allowed Windows to replace it with a Microsoft driver (version 6.1.7601.17514). No change. Any other suggestions?

JCW2 wrote:
...Can somebody give me troubleshooting instructions to test the hardware itself and, if that is working, to track down the problem?
P.S. -- I remembered that I have a bootable CD of Linux Mint (suggested long ago by ajkula66 to debug a networking problem), but I don't really know how to use it nor whether it would constitute a valid test of the sound hardware. Mint boots up fine, appears to find the sound hardware, and can seemingly control the volume; but I don't know how to make it create any sounds. For example, it has a built-in media player but no sample tracks on the boot CD to play on it (and of course I can't try an audio CD because the drive is in use by Mint). I also think I can see how to turn on the default "alert" sound, but I don't know what Linux would recognize as an "alert" condition in order to make the sound. Again, any help would be much appreciated. -- JCW2

Offline install of Windows 7 SP1 not recognised by Windows Update

Hi
I have asked this question over at the Windows Community forum, and someone suggested that I ask here.
This question regards Windows 7 and Service pack 1
I bought a couple of new computers, and decided to use the offline SP1 installation on each to get the computers up to date when I first configured them.
So I downloaded the offline update iso from Microsoft, created a DVD and installed SP1.
After configuring my computer, I then connected windows update to get all fixes etc since SP1.
To my dismay windows update has presented me with a list of *all* updates, including SP1.
Is there any way of getting Windows update to recognise the fact that I already have SP1 installed?
Further info:
This is the procedure I went through.
1) Built the computers
2) Installed Windows 7
3) Installed hardware device drivers
4) Installed SP1 from DVD
5) Connected to the internet
6) Activated Windows
7) Used Windows Update
8) Installed the fix/patch required for windows update to work
9) re-connected to windows update
10) Was dismayed at the list of fixes requiring download. (around 148)
After going through the process of downloading the updates, at around the time of the second re-boot, the list of updates included Service Pack 1.
AV Software was going to be the next thing to install, after the computer was *fully* patched
Further Further informatio :)
I have since gone ahead and installed Windows on my second computer.
I'm still interested in finding a solution for future reference.
After installing Windows7 and applying the offline SP1 update, I checked to see what updates were installed before
activation and connecting to windows update.
These are the updates listed.
1) Service Pack 1 for Windows 7 (KB976902)
2) Update for MS Windows (KB976902)
3) User Mode Driver framework V1.11 (KB2685813)
4) KB958488 (the list just haqd the kb number, no title)
5) Hot Fix for Windows (KB2505454)
My original question, and the answers/feedback can be viewed at the following page:
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/offline-install-of-windows-7-sp1-not-recognised-by/e8ab61d0-8669-4297-acfd-4acc0da8c1dc?rtAction=1427893878897
Cheers...
Daz

Hi Daz,
You mentioned that the SP1 prompted again in the needed updates, I suspect that that is not the full service pack, it is only some changes to existing non-security content, appropriate 10 MB size. you can check the size of the update to confirm
this.
See more information in this link
http://support.microsoft.com/en-us/kb/894199
And after you have manually installed the updates offline, have you checked whether these updates are listed in the "installed updates", or in Update history? And you can check the new detected updates, whether they have been successfully installed
in your system. Meanwhile, when you check for updates online, please check your Windows Update settings, we recommend you to check for important updates, not optional updates or hotfix. You can install the optional update or hotfix when you need it in the
future.
Regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

IE 10 Update 2977629 on Windows 7 x64 SP1 repeatedly fails to install.

IE 10 Update 2977629 on Windows 7 x64 SP1 repeatedly fails to install with error code 214794205 "Access is Denied". This update is being run using an administrator account. This is a systemic issue on all domain joined systems, desktops
not in a domain are not affected. I cannot find any guidance on how to fix this, please help!

Hi,
Based on your description, ED's suggestion is available. You could use gpresult command to export the group policy settings to check if there any group policy affect the installation.
About how to use it, please read the guide below:
How to Use the Group Policy Results (GPResult.exe) Command Line Tool
http://technet.microsoft.com/en-us/library/bb456989.aspx
If it's not helpful, please provide the Windows Update installation log in order to analyze it.
You could find it from the following path:
%windir%\Windowsupdate.log
Karen Hu
TechNet Community Support

System Update 4.0.0046 install fails on Windows 7 SP1

I just tried updating my Lenovo System Update to the latest version compatible with Windows 7 SP1 (version 4.0.0046), and it fails every time with the following error:
Windows cannot find 'C:\Users\DARREN~1.STI\AppData\Local\Temp\pftD0BB.tmp\setup\pasinst.exe' Make sure you typed the name correctly, and then try again.
I looked in the 'pftD0BB.tmp' folder and there is no 'setup' folder, so I'm guessing this is an error in the installer?
Any ideas? Definitely want to get this up and running again.
Thanks,
Darren David

It's no longer (sadly) surprising to me that this issue has not been publicly addressed and that I experienced the same issue with 4.0.100.1124 today.
Here is what worked for me. I don't have the bandwidth to test this again, nor is it likely the most direct method (I'm sure several of these steps are redundant). And I hate authoring instructions for just about anything. Just my blundering path to a non-failing installation.
1. Downloaded the systemupdate40-2011-02-18.exe from the Lenovo support site.
2. Ran systemupdate40-2011-02-18.exe and was presented with the "Windows cannot find..." love note.
3. Unpacked systemupdate40-2011-02-18.exe (I use winrar) to a folder on the desktop (e.g. \sysupdate\)
4. Ran setup.exe within that folder...same failure to find psainst.exe
5. Located and executed psaddZip.exe within same folder. This unpacks to a \setup folder with, surprise surprise, psainst.exe within.
6. Ran setup.exe again. Successful installation.
System Update 4.0.1.x.whatever ran, checked, and updated beautifully, and then BSOD'd on restart. But I'm still here.
Your mileage will most certainly vary.
wws

ConfigMgr 2012 R2 client on Windows 7 SP1 x86 causes "Program Compatibility Assistant" to appear

After I upgraded to R2 I am seeing the message below on newly installed Windows 7 SP1 x86 machines when I go to Control Panel and open the Configuration Manager Properties and then close it. This seems to only happen on 32-bit Win7 not on 64-bit.
I have created a new package for the client from definition and I also tried building new images using my Build and Capture task sequences. In this case I get the same message on the x86 Windows 7 SP1 machine if I log on after the Build & Capture is
done. My Build And Capture sequences uses the RTM-image for Windows 7 SP1 that has been patched using Offline Servicing.
Has anyone else seen this? Everything is working normally on the clients and if I click "This control panel works correctly" the message goes away. However, if I click "Open the control panel using recommended settings" that results in
admin-rights being required to open the Configuration Manager Properties under the Control Panel.
Regards,
Carl

I just pinged the product team and they are not aware of this issue at all so please someone open a support case with CSS where the issue can be worked.
Jason | http://blog.configmgrftw.com
I'll be opening a support case first thing monday :)
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa
Hi Tim
How did you go with this? We're still seeing this issue migrating Windows 7 x86 machines from the ConfigMgr 2007 SP2 R3/ConfigMgr 2012 client to the ConfigMgr 2012 R2 client in multiple environments.
Cheers
Sam
Ticket opened with Microsoft Support, still no fix but I will keep you all posted.
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Lenovo G560 cannot get Windows 7 SP1 via Windows Update

My Lenovo G560 laptop running Windows 7 Home Basic is not getting the option to download Windows 7 SP1 from Windows Update. What could be the problem? Has anyone else experienced this? What is the solution? I have had the laptop for almost two years.

hi SipoKapumba,
Do you get any error code(s) after a failed installation of Windows 7 SP1? Chances are, the prequisite to install Windows 7 SP1 are not installed.
Can you try to:
1. Follow this article from Microsoft and this guide in installing Windows 7 SP1 thru Windows Update
2. If it still fails, try to run Windows 7 SP1 Standalone Installer. (use the windows6.1-KB976932-X64.exe for 64bit machines)
Hope this helps

Boot Camp: Driver Update (Windows Vista SP1)

I'm running a dual boot MBP Unibody w/ OS X & Vista SP1 64Bit
I don't like to install Boot Camp in the Windows OS due to the fact that updating drivers can be a pain when installed via boot camp. However, since I've done so, I've lost the functionality of some of the hardware.
If anyone can point me to a place where I could find drivers for the following I would greatly appreciate it. If I dont get a response, I will attempt to manually extract the drivers from the OS X Install CD.
Drivers Needed:
Express Card 34 Slot (The Drivers needed to get the slot to work, regardless of card)
Apple I Sight Built in Camera
IR Receiver
Trackpad
System Specs:
17" MBP Unibody
Windows Vista SP1 64Bit
2.93 / 4GB / 9600M GT
Sonnet Tempo eSata Express/34 Card (Rev. A) (I have the drivers for this, but the card isnt recognized when placed in the MBP)

you must run system 1 dvd where bootcamp is, open folders and there choose driver/64bit ..
no choose witch one you like and install with right-click as problem or something like this.
you take working with vista sp1 before and so on ..
i run 64bit win7 rc1 with all drivers exept isight.
for more look here:
http://forums.macrumors.com/forumdisplay.php?f=86

Windows update requesting to install Windows Update Agent 7.6.7600.320

I received this today when trying to manually scan for available updates via the windows update in control panel. It shows message as below. Seems that it will install the latest Windows Update Agent 7.6.7600.320. Will this machine able to get any patch
deployed via SCCM if the WUA is not updated to the latest version?

I can't say I've heard of any widespread issues with this version of the WUA so YMMV as always. If you do have an issue, you should contact CSS though.
As for it being pushed automatically, that's correct and is no different than past WUA agent updates. It is considered an infrastructure update and is thus automatically installed via Windows Update or WSUS regardless of your client update settings unless
you've actually disabled the WUA via group policy (not the service though) -- this includes ConfigMgr also because ConfigMgr does not in way pre-empt WSUS and leverages WSUS behind the scenes.
Jason | http://blog.configmgrftw.com | @jasonsandys

Update WUA on Windows 7 SP1 Clients to 7.6.7600.320

Similar Messages

Maybe you are looking for