Quantcast
Channel: WSUS forum
Viewing all 12874 articles
Browse latest View live

Windows Server 2012 fails to report status to WSUS

$
0
0

Our WSUS install runs on Windows server 2012, reported WSUS version is 6.2.9200.16384.  We have two virtual hosts, both running Windows Server 2012 with the Hyper-V role enabled, Windows Update Version 7.8.9200.17185. 

For some reason, both of these machines fail to report to WSUS.  All other servers (all 2012) and all Windows 7 clients report correctly.

I have tried most of the basic troubleshooting steps, including verifying that the WSUS Server address is correct and that the machines in question can communicate to WSUS.  Updates are being downloaded and installed, only the status reporting is failing.

Upon inspection of the Windows Update Agent log, I found the following warnings:

2015-08-17    23:56:53:687     992    1064    Report    WARNING: Failed converting event batch to web service event: 0x8007000d
2015-08-17    23:56:53:687     992    1064    Report    WARNING: Reporter failed to upload events with hr = 8007000d.

I'm guessing these are the problem, but have no idea how to fix them.  I can post the full log if needed.  Any suggestions?


Update stuck in WSUS

$
0
0

Hi!

There is some threads on this forum about my problem, however i found some new aspects of it :)

The problem is that clients Windows 7 x64 SP1 Pro do not see and do not download SOME updates.

And there is a following string in WsusUpdate.log:

2013-10-10 15:41:37:369  352 578 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

I searched all over the net for solution and found on this forum that it means that update with id189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB is stuck somehow and should be declined/deleted/etc from server.

My next step was connecting to wsus database using named pipes and searching for this update id with a simple query:

use susdb

go

select * from tbprecomputedlocalizedproperty where updateid = '189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB' and shortlanguage ='en'

go

The result is:

438931 en Irish Language Pack NULL NULL 189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB 101 185397

Irish Language Pack!!! I don't need it, i want it to go away and let my clients to download updates!

But i can't because there is no such update in my wsus console - not in approved, not in declined, not in unapproved state. I tried deleting this update by id via powershell but no luck - it says that update can not be deleted.

So my question is - can i dispose of this Irish Language Pack somehow?



A few clients are not reporting to Wsus

$
0
0

Hi there,

On our network, a few clients are not reporting to the Wsus. other machines, on the same group are reporting normally;

Here is the Windows Update log of one of the affected machines:

2017-01-1707:47:40:2371180ddcService*************
2017-01-1707:47:40:2681180ddcService** START **  Service: Service startup
2017-01-1707:47:40:2681180ddcService*********
2017-01-1707:47:40:2681180ddcAgent * WU client version 7.6.7601.23435
2017-01-1707:47:40:2681180ddcAgent * Base directory: C:\Windows\SoftwareDistribution
2017-01-1707:47:40:2681180ddcAgent * Access type: No proxy
2017-01-1707:47:40:2681180ddcAgent * Network state: Connected
2017-01-1707:48:25:6251180ddcReportCWERReporter::Init succeeded
2017-01-1707:48:25:6251180ddcAgent***********  Agent: Initializing Windows Update Agent  ***********
2017-01-1707:48:25:6251180ddcAgent * Prerequisite roots succeeded.
2017-01-1707:48:25:6251180ddcAgent***********  Agent: Initializing global settings cache  ***********
2017-01-1707:48:25:6251180ddcAgent * WSUS server: http://wsussever.localdomain
2017-01-1707:48:25:6251180ddcAgent * WSUS status server: http://wsussever.localdomain
2017-01-1707:48:25:6251180ddcAgent * Target group: Local
2017-01-1707:48:25:6251180ddcAgent * Windows Update access disabled: No
2017-01-1707:48:25:6411180ddcDnldMgrDownload manager restoring 0 downloads
2017-01-1707:48:25:6561180ddcAU###########  AU: Initializing Automatic Updates  ###########
2017-01-1707:48:25:6721180ddcAUAU setting next detection timeout to 2017-01-17 09:48:25
2017-01-1707:48:25:6721180ddcAU # WSUS server: http://wsussever.localdomain
2017-01-1707:48:25:6721180ddcAU # Detection frequency: 22
2017-01-1707:48:25:6721180ddcAU # Target group: Local
2017-01-1707:48:25:6721180ddcAU # Approval type: Scheduled (Policy)
2017-01-1707:48:25:6721180ddcAU # Scheduled install day/time: Every day at 12:00
2017-01-1707:48:25:6721180ddcAU # Auto-install minor updates: Yes (Policy)
2017-01-1707:48:25:6721180ddcAUSetting AU scheduled install time to 2017-01-17 14:00:00
2017-01-1707:48:25:8281180ddcReport***********  Report: Initializing static reporting data  ***********
2017-01-1707:48:25:8281180ddcReport * OS Version = 6.1.7601.1.0.65792
2017-01-1707:48:25:8281180ddcReport * OS Product Type = 0x00000030
2017-01-1707:48:25:8281180ddcReport * Computer Brand = Hewlett-Packard
2017-01-1707:48:25:8281180ddcReport * Computer Model = HP EliteDesk 705 G1 DM
2017-01-1707:48:25:8281180ddcReport * Bios Revision = L06 v02.22
2017-01-1707:48:25:8281180ddcReport * Bios Name = Default System BIOS
2017-01-1707:48:25:8281180ddcReport * Bios Release Date = 2015-07-13T00:00:00
2017-01-1707:48:25:8281180ddcReport * Locale ID = 1046
2017-01-1707:48:27:4971180ddcAUSuccessfully wrote event for AU health state:1
2017-01-1707:48:27:5131180ddcAUInitializing featured updates
2017-01-1707:48:27:5131180ddcAUFound 0 cached featured updates
2017-01-1707:48:27:5131180ddcAUSuccessfully wrote event for AU health state:1
2017-01-1707:48:27:5131180ddcAUSuccessfully wrote event for AU health state:1
2017-01-1707:48:27:5131180ddcAUAU finished delayed initialization
2017-01-1707:48:27:5131180ddcAU#############
2017-01-1707:48:27:5131180ddcAU## START ##  AU: Search for updates
2017-01-1707:48:27:5131180ddcAU#########
2017-01-1707:48:27:5911180ddcAU<<## SUBMITTED ## AU: Search for updates [CallId = {1505F8FE-71C6-4B3E-8ABE-A3AAB8D1FF35}]
2017-01-1707:48:27:8091180f8cPTWARNING: Cached cookie has expired or new PID is available
2017-01-1707:48:27:8091180f8cPTInitializing simple targeting cookie, clientId = c8f1acd5-cd8c-4b18-929f-2d69008782d7, target group = Local, DNS name = localcomputer.localdomain
2017-01-1707:48:27:8091180f8cPT Server URL = http://wsusserver/SimpleAuthWebService/SimpleAuth.asmx
2017-01-1707:48:28:0751180f8cPTWARNING: GetAuthorizationCookie failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
2017-01-1707:48:28:0751180f8cPTWARNING: Failed to initialize Simple Targeting Cookie: 0x8024400a
2017-01-1707:48:28:0751180f8cPTWARNING: PopulateAuthCookies failed: 0x8024400a
2017-01-1707:48:28:0751180f8cPTWARNING: RefreshCookie failed: 0x8024400a
2017-01-1707:48:28:0751180f8cPTWARNING: RefreshPTState failed: 0x8024400a
2017-01-1707:48:28:0751180f8cPTWARNING: PTError: 0x8024400a
2017-01-1707:48:28:0751180f8cReportWARNING: Reporter failed to upload events with hr = 8024400a.
2017-01-1707:48:28:0751180f8cPTWARNING: Cached cookie has expired or new PID is available
2017-01-1707:48:28:0751180f8cPTInitializing simple targeting cookie, clientId = c8f1acd5-cd8c-4b18-929f-2d69008782d7, target group = Local, DNS name = localcomputer
2017-01-1707:48:28:0751180f8cPT Server URL = http://pms-wsu01.prefeitura.local/SimpleAuthWebService/SimpleAuth.asmx
2017-01-1707:48:28:1841180f8cPTWARNING: GetAuthorizationCookie failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
2017-01-1707:48:28:1841180f8cPTWARNING: Failed to initialize Simple Targeting Cookie: 0x8024400a
2017-01-1707:48:28:1841180f8cPTWARNING: PopulateAuthCookies failed: 0x8024400a
2017-01-1707:48:28:1841180f8cPTWARNING: RefreshCookie failed: 0x8024400a
2017-01-1707:48:28:1841180f8cPTWARNING: RefreshPTState failed: 0x8024400a
2017-01-1707:48:28:1841180f8cPTWARNING: PTError: 0x8024400a
2017-01-1707:48:28:1841180f8cReportWARNING: Reporter failed to upload events with hr = 8024400a.
2017-01-1707:48:28:1841180f8cAgent*************
2017-01-1707:48:28:1841180f8cAgent** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2017-01-1707:48:28:1841180f8cAgent*********
2017-01-1707:48:28:1841180f8cAgent * Online = No; Ignore download priority = No
2017-01-1707:48:28:1841180f8cAgent * 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"
2017-01-1707:48:28:1841180f8cAgent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2017-01-1707:48:28:1841180f8cAgent * Search Scope = {Machine}
2017-01-1707:48:42:6791180f8cAgentUpdate {704A0A4A-518F-4D69-9E03-10BA44198BD5}.112 has no local extended metadata. Not returning it.
2017-01-1707:52:47:0531180ddcAUAU setting next sqm report timeout to 2017-01-18 09:52:47

Any help would be appreciated.


Rodrigo Rocha

WSUS does not download updates and bits keeps crashing

$
0
0

Hello;

I've got wsus on server 2016 inside a vm, and WSUS doesn't download updates and bits keeps crashing.

In event viewer, I don't have a specific error coded. I just got "bits start downloading folder 08 inside WsusContent directory.

Thanks

WARNING: Failed to delete service from the backup store, error = 0x80070002

$
0
0

Long story short, we have been running an old Windows 2003 server with WSUS and I just fired up a fresh 2012 install. After getting everything set up, I changed my GPO to point clients to the new server. Within minutes, clients started showing up and everything looked groovy. Fast forward a week or two and I noticed that many clients have stopped reporting to the server. In fact, hundreds out of my 3000+ machines are now showing the following errors in the WindowsUpdate.log:

2017-01-1007:40:46:815472102cAgentWARNING: could not delete Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\34b39346-130b-4ae2-8bea-830c8e6c58fb service registry key 0x80070002
2017-01-1007:40:46:815472102cAgentWARNING: Failed to delete service from the backup store, error = 0x80070002

I have been able to get a handful of clients to work again by using a combination of resetting Windows Update on the client and installing certain patches manually, i.e. the July 2016 roll-up patch which supposedly speeds up the search for updates. But I have not been able to figure out a real fix for all of my broken clients.

Does anyone have any idea what could have happened or what might be going on here?

WSUS Breaks after KB3159706, released 5/5/2016

$
0
0

Hey all, just installed KB3159706 on my WS 2012 R2 WSUS Server at 2PM on 5/5/2016.  This was supposed to fix/issues when KB3148812 was released a few weeks ago.  Don't install KB3159706, it breaks WSUS.

C'mon Microsoft, get your stuff together.  I'm tired of this amateur hour BS.



Base image

$
0
0
If I am creating a  base  image  for a  specific  model  machine  do I need  to collect the  image  of that machine  or can   I  build a Windows 7  VM and  use  this  VM as the  base  image  ? 

New information, changes your outlook ....

Windows 2012 r2 Updates stuck

$
0
0

On my 2012 r2 server, updates is stuck on "Checking for updates" and never finishes.

I've attempted numerous things including:

- WindowsUpdateDiagnostic.diagcab

- latestwu.diagcab

- KB971058

- KB949104

- KB2937636

- KB2919355

I am not on a domain.


NOT a new install.

Update 3212646 failing with error 8024200D

$
0
0

Server 2008 R2 SP1 Enterprise

All other updates installed. I have went through the normal steps:

1. Reboot
2. Verified date/time are correct
3. Renamed software distribution folder
4. Ran the readiness tool - no issues found
5. Ran SFC - no issues found

Manual deployment of Office 2010 SP2

$
0
0

Our WSUS server is completely outdated, but I have an urgent need to deploy Office 2010 SP2 to a bunch of clients.

Can I superseed the hundreds of other approved updates and push this ASAP?

I have already set the SP2 as an approved update.

Updates not Visible in Update Views, only by Searching

$
0
0

Hi all,

Have a strange issue where various updates are not visible in any of the WSUS update views - both the default ones like "All Updates" and ones we specially create targeting the relevant update classification and product. The filters are set correctly (Approval = "Any Except Declined"; Status = "Any").

If I search for the updates by KB number, they are found with approval = unapproved, and I can approve them (meaning they have not been superseded I believe). Any ideas on how to make these updates appear in the update views?

Some of the affected updates:

  • KB3055030 - Security Update for Microsoft Word 2013
  • KB3054929 - Security Update for Microsoft Visio 2013
  • KB3055029 - Security Update for Microsoft PowerPoint 2013
  • KB3054991 - Security Update for Microsoft Excel 2013

All of these are unapproved, have classification = "Security Updates" and Products = "Office 2013", which we are synchronizing directly from MS. I assume that if they weren't included in what we sync they wouldn't appear in the WSUS search results at all.

WSUS on Server 2012 R2.

Thanks.

Lukas

Windows 10 Anniversary Update (1607)

$
0
0

Anyone can explain why Windows 10 1607 client can't download WSUS updates ?

WSUS is install on Windows Server 2012 R2 Server.

When a Windows 10 client detect a Windows 10 (1607 only) update on WSUS, client can't download every update ( Windows or other)

If there are only Office update everything works good.

Not needed updates

$
0
0

I built a new WSUS server on Windows Server 2012 R2, configured it for Windows 7 and Office 2013. I imported the 2 following updates for Win7SP1, KB3020369 - April 2015 servicing stack, and KB3125574 - Convenience Rollup. I configured an automatic approval rule, and ran that without problems. After the updates install on the Win7 client, I see the following messages:

Succeeded: 164 updates

Not needed: 13 updates

Does anyone know how I can identify the "Not needed: 13 updates" so I can decline them? Can they be found in the WindowsUpdate.log, or in the WSUS console?

Thanks.

Error ID 12022 The Client Web Service is not working

$
0
0

I have recently reinstalled WSUS 6.3 onto Windows Server 2012 R2. Wsus has connected to the network machines via GPO and lists the PC/Severs on my network, but i am getting the error ID 12022 The Client Web Service is not working.

In the WSUS Console the error. This computer has not reported status yet is displaying.

I have found information regarding KB3159706 and the post install manual steps, which have not worked.

Any suggestions would be helpful

Thanks 


Single Client Cannot Conact WSUS with 0x80072f8f

$
0
0

I have a single Server 2008 R2 server that cannot contact WSUS.

2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: Send failed with hr = 80072f8f.
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://WSUS-SERVER:8531/selfupdate/wuident.cab>. error 0x80072f8f
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072f8f
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072f8f
2017-01-13    12:12:29:871     980    3df0    Misc    WARNING: Library download error. Error 0x80072f8f. Will retry. RetryCounter:0
2017-01-13    12:12:29:902     980    3df0    Misc    WARNING: Send failed with hr = 80072f8f.

The clocks are synced correctly, device has the same group policy for Windows Updates as the other 700 workstations on the network. but it cannot connect to my SSL secured WSUS server. Connecting directly to the SelfUpdate URL via IE11 gives:

This page can’t be displayed

Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting tohttps://WSUS-SERVER:8531 again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4(link for the details), which is not considered secure. Please contact your site administrator.

There are no proxies configured:

Current WinHTTP proxy settings:

    Direct access (no proxy server).

I also cannot access the SelfUpdate URL via Firefox:
Secure Connection Failed

The connection to the server was reset while the page was loading.

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

Or Chrome:

This site can’t be reached

The web page at https://WSUS-SERVER/SelfUpdate might be temporarily down or it may have moved permanently to a new web address.

ERR_CONNECTION_ABORTED



no Server 2012 updates from last Tu

$
0
0

The question:

why I don't see any for Server 2012 (that usually are there, sure I have bunch of 2012).

Sorry the image taken is too small  (sometimes it happens on forum site).

Please zoom to see

Thx.


--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis




Windows 2012 R2 WSUS, set do download to local disk, download from MS, can't select language, are greyed out

$
0
0

We have an Windows 2003 with WSUS, I have copied the content and db to a new Windows 2012 R2 server in DMZ.

If i choose not to store localy, instead download direct from MS , I can't change language, English is marked but greyed out , and it download many languages.

This seems like a bug.

Any more with this strange thing?

Roaming profile not syncing

$
0
0

Roaming profile suddenly not sync and load tem profile /Readonly , anything users done it reset after restart

any suggestions

 

Client not detecting needed updates from WSUS server or directly from Microsoft update

$
0
0

I am stumped on this, I have been working at it for three days and not found a solution. Background: I have a large domain and updates are working properly across most PCs and Servers. Over the past week we added six new 2012 R2 servers to the network. Each of those servers were able to detect and install updates, and reboot. After rebooting they each have failed to receive more updates since then. The initial update I did on the servers was done from my WSUS server. When I attempt to update from Microsoft directly, the update client still fails to detect the missing patches. 

Here is a log entry of an attempt to update from microsoft directly:

2016-12-2909:04:08:6867641b24IdleTmrIncremented idle timer priority operation counter to 1
2016-12-2909:04:08:686426479cMisc===========  Logging initialized (build: 7.9.9600.16441, tz: -0500)  ===========
2016-12-2909:04:08:686426479cMisc = Process: C:\Windows\Explorer.EXE
2016-12-2909:04:08:686426479cMisc = Module: C:\Windows\system32\wucltux.dll
2016-12-2909:04:08:686426479cCltUIFATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2016-12-2909:04:08:686426479cCltUIWARNING: RegisterNetworkCostChangeNotification: Error 80004002
2016-12-2909:04:11:1557641b24AUTriggering AU detection through DetectNow API
2016-12-2909:04:11:1557641b24AUTriggering Online detection (interactive) non-default
2016-12-2909:04:11:155764353cAU#############
2016-12-2909:04:11:155764353cAU## START ##  AU: Search for updates
2016-12-2909:04:11:155764353cAU#########
2016-12-2909:04:11:155764353cIdleTmrWU operation (CSearchCall::Init ID 1) started; operation # 10; does use network; is not at background priority
2016-12-2909:04:11:155764353cIdleTmrIncremented PDC RefCount for Network to 1
2016-12-2909:04:11:155764353cIdleTmrIncremented idle timer priority operation counter to 2
2016-12-2909:04:11:249764353cReport***********  Report: Initializing static reporting data  ***********
2016-12-2909:04:11:249764353cReport * OS Version = 6.3.9600.0.0.197008
2016-12-2909:04:11:249764353cReport * OS Product Type = 0x00000008
2016-12-2909:04:11:264764353cReport * Computer Brand = VMware, Inc.
2016-12-2909:04:11:264764353cReport * Computer Model = VMware Virtual Platform
2016-12-2909:04:11:264764353cReport * Platform Role = 1
2016-12-2909:04:11:264764353cReport * AlwaysOn/AlwaysConnected (AOAC) = 0
2016-12-2909:04:11:264764353cReport * Bios Revision = 6.00
2016-12-2909:04:11:264764353cReport * Bios Name = PhoenixBIOS 4.0 Release 6.0     
2016-12-2909:04:11:264764353cReport * Bios Release Date = 2014-04-14T00:00:00
2016-12-2909:04:11:264764353cReport * Bios Sku Number unavailable.
2016-12-2909:04:11:264764353cReport * Bios Vendor = Phoenix Technologies LTD
2016-12-2909:04:11:264764353cReport * Bios Family unavailable.
2016-12-2909:04:11:264764353cReport * Bios Major Release = 4
2016-12-2909:04:11:264764353cReport * Bios Minor Release = 6
2016-12-2909:04:11:264764353cReport * Locale ID = 1033
2016-12-2909:04:11:264764353cAgent*** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-12-2909:04:11:264764353cAU<<## SUBMITTED ## AU: Search for updates  [CallId = {11098957-A024-4EBD-8656-041770CE9014} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
2016-12-2909:04:11:264764244cAgent***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-12-2909:04:11:264764244cAgent*************
2016-12-2909:04:11:264764244cAgent** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-12-2909:04:11:264764244cAgent*********
2016-12-2909:04:11:264764244cAgent * Online = Yes; Ignore download priority = No
2016-12-2909:04:11:264764244cAgent * 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"
2016-12-2909:04:11:264764244cAgent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2016-12-2909:04:11:264764244cAgent * Search Scope = {Machine & All Users}
2016-12-2909:04:11:264764244cAgent * Caller SID for Applicability: S-1-5-21-373770480-2062961480-879972363-13372
2016-12-2909:04:11:264764244cEPGot 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "7971f918-a847-4430-9279-4a52d1efe18d"
2016-12-2909:04:11:280764244cSLSRetrieving SLS response from server...
2016-12-2909:04:11:280764244cSLSMaking request with URL HTTPS://sls.update.microsoft.com/SLS/{7971F918-A847-4430-9279-4A52D1EFE18D}/x64/6.3.9600.0/0?CH=41&L=en-US&P=&PT=0x8&WUA=7.9.9600.16422
2016-12-2909:04:11:968764244cMiscValidating signature for C:\Windows\SoftwareDistribution\SLS\7971F918-A847-4430-9279-4A52D1EFE18D\sls.cab:
2016-12-2909:04:11:968764244cMiscMicrosoft signed: Yes
2016-12-2909:04:11:968764244cMiscInfrastructure signed: Yes
2016-12-2909:04:11:968764244cMiscValidating signature for C:\Windows\SoftwareDistribution\SLS\7971F918-A847-4430-9279-4A52D1EFE18D\TMP1B2B.tmp:
2016-12-2909:04:11:983764244cMiscMicrosoft signed: Yes
2016-12-2909:04:11:983764244cMiscInfrastructure signed: Yes
2016-12-2909:04:11:983764244cEPGot 7971F918-A847-4430-9279-4A52D1EFE18D redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
2016-12-2909:04:11:983764244cSetupChecking for agent SelfUpdate
2016-12-2909:04:11:983764244cSetupClient version: Core: 7.9.9600.16422  Aux: 7.9.9600.16384
2016-12-2909:04:11:983764244cEPGot 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SelfUpdate URL: "https://fe2.update.microsoft.com/v10/3/windowsupdate/selfupdate"
2016-12-2909:04:12:639764244cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2016-12-2909:04:12:639764244cMiscMicrosoft signed: Yes
2016-12-2909:04:12:639764244cMiscInfrastructure signed: Yes
2016-12-2909:04:12:639764244cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP1DCC.tmp:
2016-12-2909:04:12:639764244cMiscMicrosoft signed: Yes
2016-12-2909:04:12:655764244cMiscInfrastructure signed: Yes
2016-12-2909:04:12:655764244cSetupSkipping SelfUpdate check based on the /SKIP directive in wuident
2016-12-2909:04:12:655764244cSetupSelfUpdate check completed.  SelfUpdate is NOT required.
2016-12-2909:04:15:343764244cPT+++++++++++  PT: Synchronizing server updates  +++++++++++
2016-12-2909:04:15:343764244cPT + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016-12-2909:04:15:343764244cAgentReading cached app categories using lifetime 604800 seconds
2016-12-2909:04:15:343764244cAgentRead 1 cached app categories
2016-12-2909:04:21:484764244cPT + SyncUpdates round trips: 2
2016-12-2909:04:22:265764244cAgentWARNING: Failed to evaluate Installed rule, updateId = {{4DEB7F5F-D14D-43E2-93FA-F81B10846CF7}.200}, hr = 80070057
2016-12-2909:04:22:265764244cAgentWARNING: Failed to evaluate Installable rule, updateId = {{4DEB7F5F-D14D-43E2-93FA-F81B10846CF7}.200}, hr = 80070057
2016-12-2909:04:22:265764244cAgentWARNING: Failed to evaluate Installed rule, updateId = {{22FFD207-0EB5-4FCF-9F6A-67078327D7A3}.200}, hr = 80070057
2016-12-2909:04:22:280764244cAgentWARNING: Failed to evaluate Installed rule, updateId = {{A4ECF96E-FE76-4933-B1A9-FAA712DC2A3B}.200}, hr = 80070057
2016-12-2909:04:22:280764244cAgentWARNING: Failed to evaluate Installable rule, updateId = {{A4ECF96E-FE76-4933-B1A9-FAA712DC2A3B}.200}, hr = 80070057
2016-12-2909:04:22:280764244cAgentWARNING: Failed to evaluate Installed rule, updateId = {{9941EB5F-4953-446D-99A2-C5989C596283}.200}, hr = 80070057
2016-12-2909:04:22:280764244cAgentWARNING: Failed to evaluate Installable rule, updateId = {{9941EB5F-4953-446D-99A2-C5989C596283}.200}, hr = 80070057
2016-12-2909:04:28:015764244cPT+++++++++++  PT: Synchronizing extended update info  +++++++++++
2016-12-2909:04:28:015764244cPT + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016-12-2909:04:32:156764244cAgentUpdate {FF434E78-8B6A-4860-BD0F-4AC472E29063}.101 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {566B95D4-66F6-47BA-8953-02CAEA29022C}.101 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {B932D155-4C7F-4CBC-8527-D5DF17B0A220}.101 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {B6C0F3C6-C368-4A76-A3BF-BE068C7358F0}.101 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgent * Added update {CA46FE98-F4C8-432F-9EB5-192ED4E0E5EE}.200 to search result
2016-12-2909:04:32:156764244cAgentUpdate {0C028E91-F849-476D-94CD-C5CD4CCBAD75}.200 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {5AF4FF91-E9A7-45B3-841F-AE886BB3C658}.201 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {81E92824-528F-4583-B074-406D9ED8701B}.200 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {95B42BE3-50BA-4AD2-908B-AF3F10304827}.201 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {547D2F41-089B-448F-9265-79579EC92F80}.200 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {B9271F09-68F6-4AF6-A188-340D1C9AD7CC}.200 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgentUpdate {29A16CC3-ADC5-45CD-99B0-50398E334137}.200 is pruned out due to potential supersedence
2016-12-2909:04:32:156764244cAgent * Added update {1971370B-AA59-4AD3-8230-2364FD01E334}.200 to search result
2016-12-2909:04:32:156764244cAgent * Found 2 updates and 84 categories in search; evaluated appl. rules of 2688 out of 4336 deployed entities
2016-12-2909:04:32:156764244cAgent*********
2016-12-2909:04:32:171764244cAgent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]
2016-12-2909:04:32:171764244cAgent*************
2016-12-2909:04:32:171764244cIdleTmrWU operation (CSearchCall::Init ID 1, operation # 10) stopped; does use network; is not at background priority
2016-12-2909:04:32:171764244cIdleTmrDecremented PDC RefCount for Network to 0
2016-12-2909:04:32:171764244cIdleTmrDecremented idle timer priority operation counter to 1
2016-12-2909:04:32:171764f50AU>>##  RESUMED  ## AU: Search for updates [CallId = {11098957-A024-4EBD-8656-041770CE9014} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
2016-12-2909:04:32:171764f50AU # 2 updates detected
2016-12-2909:04:32:171764f50AU#########
2016-12-2909:04:32:171764f50AU##  END  ##  AU: Search for updates  [CallId = {11098957-A024-4EBD-8656-041770CE9014} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]
2016-12-2909:04:32:171764f50AU#############
2016-12-2909:04:32:171764f50AUAll AU searches complete.

The attempt to microsoft directly returns only two optional updates. But I know based on security scanning software the server is missing over 100 security patches. Here is a second log ran using my WSUS server:

2016-12-2909:19:13:467764244cAgent * Found 0 updates and 81 categories in search; evaluated appl. rules of 1016 out of 1714 deployed entities
2016-12-2909:19:13:483764244cAgentReporting status event with 0 installable, 43 installed,  0 installed pending, 0 failed and 0 downloaded updates
2016-12-2909:19:13:483764244cAgent*********
2016-12-2909:19:13:483764244cAgent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 2]
2016-12-2909:19:13:483764244cAgent*************
2016-12-2909:19:13:483764244cIdleTmrWU operation (CSearchCall::Init ID 2, operation # 230) stopped; does use network; is not at background priority
2016-12-2909:19:13:483764244cIdleTmrDecremented PDC RefCount for Network to 0
2016-12-2909:19:13:483764244cIdleTmrDecremented idle timer priority operation counter to 1
2016-12-2909:19:13:483764f50AU>>##  RESUMED  ## AU: Search for updates [CallId = {D0C6762B-9FD5-4604-A0E2-07E347A87C06} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2016-12-2909:19:13:483764f50AU # 0 updates detected
2016-12-2909:19:13:483764f50AU#########
2016-12-2909:19:13:483764f50AU##  END  ##  AU: Search for updates  [CallId = {D0C6762B-9FD5-4604-A0E2-07E347A87C06} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2016-12-2909:19:13:483764f50AU#############
2016-12-2909:19:13:483764f50AUAll AU searches complete.
2016-12-2909:19:13:483764f50AUAU setting next detection timeout to 2016-12-29 21:15:21

I have did the normal tricks of deleting and recreating software distribution folder, reset authorization, etc. That is not working. Any advice would be appreciated.





WSUS clients updated on hold status

$
0
0

Hi all, I've set up WSUS in company AD, computers within AD received update patches from WSUS server. However, most computers could not received all download patches from WSUS, the received % kept unchanged more than 30 days, but such computers could feedback status to WSUS servers normally

Another problem...some computers already online status, but WSUS server could not receive their status feedback... how to ensure connection between clients and WSUS server work probably?

Viewing all 12874 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>