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

WSUS 3.0 Service Pack 2 package

$
0
0

Hi Guys,

Could you help me please I need to downloads WSUS 3.0 Service Pack 2 package KB972455 , where I can find it, on Microsoft page doesn't exist anymore

thank you

 



Windows server 2012r2 update err

$
0
0
2019-12-0414:45:10:1129169a4Agent** START **  Agent: Finding updates [CallerId = wusa  Id = 3]
2019-12-0414:45:10:1129169a4Agent*********
2019-12-0414:45:10:1129161e2cAgentWARNING: WU client fails to call back to search call {933646F8-6900-4765-994B-F84CE9C98C3F} with error 0x8024000c
2019-12-0414:45:10:1129169a4Agent  * Online = Yes; Ignore download priority = No
2019-12-0414:45:10:1129169a4Agent  * Criteria = "DeploymentAction='Installation'"
2019-12-0414:45:10:1129169a4Agent  * ServiceID = {E302BA0E-648B-47E0-A5FF-0BA4A2AC13E7} Third party service
2019-12-0414:45:10:1129169a4Agent  * Search Scope = {Machine}
2019-12-0414:45:10:1129169a4Agent  * Caller SID for Applicability: S-1-5-21-1375736893-3079953763-482349640-500
2019-12-0414:45:10:3009169a4Agent  * WARNING: Exit code = 0x8024000B
2019-12-0414:45:10:3009169a4Agent*********
2019-12-0414:45:10:3009169a4Agent**  END  **  Agent: Finding updates [CallerId = wusa  Id = 3]
2019-12-0414:45:10:3009169a4Agent*************
2019-12-0414:45:10:3009169a4AgentWARNING: WU client failed Searching for update with error 0x8024000b
2019-12-0414:45:10:3009169a4IdleTmrWU operation (CSearchCall::Init ID 3, operation # 15) stopped; does use network; is not at background priority
2019-12-0414:45:10:3009169a4IdleTmrDecremented PDC RefCount for Network to 2
2019-12-0414:45:10:3009169a4IdleTmrDecremented idle timer priority operation counter to 1
2019-12-0414:45:10:3009169a4Agent***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdates  Id = 4]
2019-12-0414:45:10:3009169a4Agent*************
2019-12-0414:45:10:3009169a4Agent** START **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 4]
2019-12-0414:45:10:3009169a4Agent*********
2019-12-0414:45:10:3009169a4Agent  * Online = Yes; Ignore download priority = No
2019-12-0414:45:10:3009169a4Agent  * 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"
2019-12-0414:45:10:3009169a4Agent  * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2019-12-0414:45:10:3009169a4Agent  * Search Scope = {Machine & All Users}
2019-12-0414:45:10:3009169a4Agent  * Caller SID for Applicability: S-1-5-18
2019-12-0414:45:10:30070561cd8COMAPI>>--  RESUMED  -- COMAPI: Search [ClientId = wusa]
2019-12-0414:45:10:3009169a4SLSRetrieving SLS response from server using ETAG "16IMgThQPatW3gLvl1IedEpqN3G7onUum7nRv4bGmwI=_1440"...
2019-12-0414:45:10:30070561cd8COMAPI  - Updates found = 0
2019-12-0414:45:10:30070561cd8COMAPI  - WARNING: Exit code = 0x00000000, Result code = 0x8024000B
2019-12-0414:45:10:30070561cd8COMAPI---------
2019-12-0414:45:10:3009169a4SLSMaking request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=50&L=zh-CN&P=&PT=0x8&WUA=7.9.9600.17031
2019-12-0414:45:10:30070561cd8COMAPI--  END  --  COMAPI: Search [ClientId = wusa]
2019-12-0414:45:10:30070561cd8COMAPI-------------
2019-12-0414:45:10:30070561704COMAPI-----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
2019-12-0414:45:10:30070561704COMAPI  - ServiceId = {e302ba0e-648b-47e0-a5ff-0ba4a2ac13e7}
2019-12-0414:45:10:30091639cIdleTmrDecremented idle timer priority operation counter to 0
2019-12-0414:45:10:3629169a4EPGot 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "7971f918-a847-4430-9279-4a52d1efe18d"
2019-12-0414:45:10:36270561704COMAPIIUpdateService removing volatile scan package service, serviceID = {E302BA0E-648B-47E0-A5FF-0BA4A2AC13E7}
2019-12-0414:45:10:3629169a4SLSRetrieving SLS response from server...
2019-12-0414:45:10:3629169a4SLSMaking request with URL HTTPS://sls.update.microsoft.com/SLS/{7971F918-A847-4430-9279-4A52D1EFE18D}/x64/6.3.9600.0/0?CH=50&L=zh-CN&P=&PT=0x8&WUA=7.9.9600.17031
2019-12-0414:45:10:362916230cAgentWARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
2019-12-0414:45:10:36270561704COMAPIWARNING: ISusInternal::RemoveService failed, hr=80248014
2019-12-0414:45:10:7689169a4MiscValidating signature for C:\Windows\SoftwareDistribution\SLS\7971F918-A847-4430-9279-4A52D1EFE18D\sls.cab with dwProvFlags 0x00000080:
2019-12-0414:45:10:8159169a4MiscMicrosoft signed: NA
2019-12-0414:45:10:8159169a4MiscInfrastructure signed: Yes
2019-12-0414:45:10:8159169a4MiscValidating signature for C:\Windows\SoftwareDistribution\SLS\7971F918-A847-4430-9279-4A52D1EFE18D\TMPE0FA.tmp with dwProvFlags 0x00000080:
2019-12-0414:45:10:8159169a4MiscMicrosoft signed: NA
2019-12-0414:45:10:8319169a4MiscInfrastructure signed: Yes
2019-12-0414:45:10:8319169a4EPGot 7971F918-A847-4430-9279-4A52D1EFE18D redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
2019-12-0414:45:10:8319169a4SetupChecking for agent SelfUpdate
2019-12-0414:45:10:8319169a4SetupClient version: Core: 7.9.9600.17031  Aux: 7.9.9600.17031
2019-12-0414:45:10:8319169a4SLSRetrieving SLS response from server using ETAG "16IMgThQPatW3gLvl1IedEpqN3G7onUum7nRv4bGmwI=_1440"...
2019-12-0414:45:10:8479169a4SLSMaking request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=50&L=zh-CN&P=&PT=0x8&WUA=7.9.9600.17031
2019-12-0414:45:10:8789169a4EPGot 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SelfUpdate URL: "https://fe2.update.microsoft.com/v10/3/windowsupdate/selfupdate"
2019-12-0414:45:14:3629169a4MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2019-12-0414:45:14:3789169a4MiscMicrosoft signed: NA
2019-12-0414:45:14:3789169a4MiscInfrastructure signed: Yes
2019-12-0414:45:14:3789169a4MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPEEE6.tmp with dwProvFlags 0x00000080:
2019-12-0414:45:14:3949169a4MiscMicrosoft signed: NA
2019-12-0414:45:14:3949169a4MiscInfrastructure signed: Yes
2019-12-0414:45:14:3949169a4SetupFATAL: GetClientUpdateUrl failed, err = 0x8024D009
2019-12-0414:45:14:3949169a4SetupSkipping SelfUpdate check based on the /SKIP directive in wuident
2019-12-0414:45:14:3949169a4SetupSelfUpdate check completed.  SelfUpdate is NOT required.
2019-12-0414:45:15:6129169a4PT+++++++++++  PT: Synchronizing server updates  +++++++++++
2019-12-0414:45:15:6129169a4PT  + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2019-12-0414:45:15:6129169a4PTWARNING: Cached cookie has expired or new PID is available
2019-12-0414:45:15:8789169a4AgentReading cached app categories using lifetime 604800 seconds
2019-12-0414:45:15:8789169a4AgentRead 2 cached app categories
2019-12-0414:45:24:6919169a4PT  + SyncUpdates round trips: 2
2019-12-0414:45:59:3489169a4PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
2019-12-0414:45:59:3489169a4PT  + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/11/windows8.1-kb4524445-x64_a8a5b5fd641b016e8ee0636c1dde808e98656d3a.msu for file qKW1/WQbAW6O4GNsHd6AjphlbTo= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/c/msdownload/update/others/2019/11/30238212_8fda5e07c0f1a6e8508a95c588cb6d5b3bd934b7.cab for file j9peB8DxpuhQipXFiMttWzvZNLc= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/c/msdownload/update/others/2019/11/30276887_3ce005e0cf0d44d64bd76d68d03998ba6db5c4b5.cab for file POAF4M8NRNZL121o0DmYum21xLU= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/10/windows8.1-kb4525243-x64_841624a268dfee78c7739a4eeccdf50b741ebeb3.msu for file hBYkomjf7njHc5pO7M31C3QevrM= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/d/msdownload/update/others/2019/11/30203376_93dc7b39f5cad76a0cea00a118084c34bd9a336c.cab for file k9x7OfXK12oM6gChGAhMNL2aM2w= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/09/windows8.1-kb4514371-x64_7120ec6194dbc78101a5be0762b04fcd1553cdec.msu for file cSDsYZTbx4EBpb4HYrBPzRVTzew= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/d/msdownload/update/others/2019/11/30276925_c06feae3c8a48290048f73421bb23e48e5666ff6.cab for file wG/q48ikgpAEj3NCG7I+SOVmb/Y= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/c/msdownload/update/others/2019/11/30238241_a0225f6c8c4b90ad0469f0f4612983a79eeacaf4.cab for file oCJfbIxLkK0EafD0YSmDp57qyvQ= when file has not been previously added to the datastore
2019-12-0414:45:59:6459169a4DtaStorWARNING: Attempted to add URL http://download.windowsupdate.com/d/msdownload/update/software/updt/2019/11/windows8.1-kb4525252-x64_696b0978cfef62d04d071ec179c3b8c61e6fde6b.msu for file aWsJeM/vYtBNBx7BecO4xh5v3ms= when file has not been previously added to the datastore
2019-12-0414:47:03:5319161c88IdleTmrIncremented idle timer priority operation counter to 1
2019-12-0414:47:03:5311072208cMisc===========  Logging initialized (build: 7.9.9600.17052, tz: +0800)  ===========
2019-12-0414:47:03:5311072208cMisc  = Process: C:\Windows\Explorer.EXE
2019-12-0414:47:03:5311072208cMisc  = Module: C:\Windows\system32\wucltux.dll
2019-12-0414:47:03:5311072208cCltUIFATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-12-0414:47:03:5311072208cCltUIWARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-12-0414:47:05:8129161c88AUTriggering AU detection through DetectNow API
2019-12-0414:47:05:8129161c88AUAdditional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
2019-12-0414:47:05:8129161c88AUPiggybacking on an AU detection already in progress
2019-12-0414:51:55:29491639cIdleTmrDecremented idle timer priority operation counter to 0
2019-12-0415:07:04:45491621bcAUWARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-12-0415:07:04:45491621bcAUWARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-12-0415:07:13:079916948IdleTmrIncremented idle timer priority operation counter to 1
2019-12-0415:07:13:0791072231cMisc===========  Logging initialized (build: 7.9.9600.17052, tz: +0800)  ===========
2019-12-0415:07:13:0791072231cMisc  = Process: C:\Windows\Explorer.EXE
2019-12-0415:07:13:0791072231cMisc  = Module: C:\Windows\system32\wucltux.dll
2019-12-0415:07:13:0791072231cCltUIFATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-12-0415:07:13:0791072231cCltUIWARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-12-0415:07:16:188916948IdleTmrDecremented idle timer priority operation counter to 0

2012R2 Wsus with SQL server Express.

$
0
0

Hello,

Im planing the installation of WSUS 2012R2 and SQL server express. I know the 10gb limitation of the DB, i dont think our DB exceeds 3 or 4GB.

On my company they prefer to use SQL Express instead WID. 

In the future, we will migrate the SQL express to SQL 2014 or 2016, when we buy it.

Is this a good action plan ? 

Many thanks ;)

Windows Update Error 80092004

$
0
0

I posted this question originally on the consumer site therefore I am posting it here, here is my problem

We had four severs running Server 2k8 SP2 that were all failing in installing Windows Update KB4512499, 4517301.  So we installed patch 4474419, 4490628.  This fixed two of the servers but the other 2 are still failing to install those updates with error code 80092004 which is the same error on all four servers.  Not sure what to do next.

Feature Update to Windows 10 - 1809 using WSUS

$
0
0

Hello,

I am using WSUS  10.0.14393.2007 on windows server 2016 Ent edition. We are running Windows 10 version 1803 enterprise edition. Now i want to upgrade windows 10 1803 enterprise version to 1809 enterprise version. But when i goes to WSUS console updates there is feature update for Business edition and consumer edition.

We are running enterprise edition of windows 10. What should i select now. Can anybody help me in this.

Windows Server 2012R2 patch update error

$
0
0

I am trying to update the following windows patch for my w2012r2 server.

November 19, 2019—KB4525252 (Preview of Monthly Rollup)

It will failed with the following error 0x80070001.

I have tried to reset the WSUS, deleted away the softwaredistribtion folders, download the standalone patch and apply manually but none of it was successful. Can anyone advice what is wrong?

Attached is the windowsupdate.log.

2019-12-05 16:51:45:968 820 a60 DnldMgr Preparing update for install, updateId = {EC6B7369-0A01-4A82-917D-C6E0E3CCD4BF}.501.

2019-12-05 16:51:45:984 2244 6f0 Misc ===========  Logging initialized (build: 7.9.9600.19374, tz: +0800)  ===========

2019-12-05 16:51:45:984 2244 6f0 Misc   = Process: C:\Windows\system32\wuauclt.exe

2019-12-05 16:51:45:984 2244 6f0 Misc   = Module: C:\Windows\SYSTEM32\wuaueng.dll

2019-12-05 16:51:45:984 2244 6f0 Handler :::::::::::::

2019-12-05 16:51:45:984 2244 6f0 Handler :: START ::  Handler: CBS Install

2019-12-05 16:51:45:984 2244 6f0 Handler :::::::::

2019-12-05 16:51:45:984 2244 6f0 Handler Starting install of CBS update EC6B7369-0A01-4A82-917D-C6E0E3CCD4BF

2019-12-05 16:51:45:984 2244 6f0 Handler CBS session identity: 30780233_961581599

2019-12-05 16:51:46:031 2244 6f0 Handler CBS package identity: Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19544.1.6

2019-12-05 16:51:46:031 2244 6f0 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\31cf388f1b68d19a8c21f2f8cd979f64\Windows8.1-KB4525252-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\31cf388f1b68d19a8c21f2f8cd979f64\inst

2019-12-05 16:51:50:953 820 bb4 Report REPORT EVENT: {2817F758-61BF-40D8-AAC4-3DCA82E8B94E} 2019-12-05 16:51:45:952+0800 1 181 [AGENT_INSTALLING_STARTED] 101 {8802FDE5-F00C-4D52-A70D-504BD3E3D8C3} 501 0 wusa Success Content Install Installation Started: Windows has started installing the following update: Update for Windows (KB4525252)

2019-12-05 16:51:50:953 820 bb4 Report CWERReporter finished handling 2 events. (00000000)

2019-12-05 16:54:14:808 2244 514 Handler FATAL: CBS called Error with 0x80070001, 

2019-12-05 16:54:37:419 2244 6f0 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070001

2019-12-05 16:54:43:482 2244 6f0 Handler :::::::::

2019-12-05 16:54:43:482 2244 6f0 Handler ::  END  ::  Handler: CBS Install

2019-12-05 16:54:43:482 2244 6f0 Handler :::::::::::::

2019-12-05 16:54:43:513 820 a60 Agent LogHistory called. idUpdate={8802FDE5-F00C-4D52-A70D-504BD3E3D8C3}.501, resultMapped=80070001, resultUnMapped=80070001

2019-12-05 16:54:43:576 820 a60 Agent *********

2019-12-05 16:54:43:576 820 a60 Agent **  END  **  Agent: Installing updates [CallerId = wusa]

2019-12-05 16:54:43:576 820 a60 Agent *************

2019-12-05 16:54:43:576 2336 834 COMAPI >>--  RESUMED  -- COMAPI: Install [ClientId = wusa]

2019-12-05 16:54:43:576 2336 834 COMAPI   - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)

2019-12-05 16:54:43:576 2336 834 COMAPI   - Reboot required = No

2019-12-05 16:54:43:576 2336 834 COMAPI   - WARNING: Exit code = 0x00000000; Call error code = 0x80240022

2019-12-05 16:54:43:576 2336 834 COMAPI ---------

2019-12-05 16:54:43:576 2336 834 COMAPI --  END  --  COMAPI: Install [ClientId = wusa]

2019-12-05 16:54:43:576 2336 834 COMAPI -------------

2019-12-05 16:54:43:576 820 a60 IdleTmr WU operation (CInstallCall::Init ID 2, operation # 30) stopped; does not use network; is not at background priority

2019-12-05 16:54:43:576 820 a60 IdleTmr Decremented idle timer priority operation counter to 1

2019-12-05 16:54:49:889 2336 2d0 COMAPI -----------  COMAPI: IUpdateServiceManager::RemoveService  -----------

2019-12-05 16:54:49:889 2336 2d0 COMAPI   - ServiceId = {e2a13acd-f27f-4ef1-853e-d9f1433dc4de}

2019-12-05 16:54:49:920 2336 2d0 COMAPI IUpdateService removing volatile scan package service, serviceID = {E2A13ACD-F27F-4EF1-853E-D9F1433DC4DE}

2019-12-05 16:54:49:920 2336 2d0 COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014

WSUS 4 on w2012 server with Replica mode on WSUS 3.2 W2008 server

$
0
0

Hello, 

We need to  put in place a new Upstream WSUS server in W2012 , so with WSUS 4.0.

But I have two downstream servers for replica mode in W2008 with WSUS 3.2

Could the new server in WSUS 4.0 replicate on the 2 servers in W2008 WSUS 3.2  ?

Thanks 

Stephane

windows 10 feature update via WSUS 2012

$
0
0

Hi

I got 90 + computers with collection of windows 7,8,8.1 and 10. I approved few feature updates via WSUS and it is not downloaded. error 0x80d02002

 then i google this and found this link but cannot download the said KB update. 

 https://support.microsoft.com/en-us/help/3095113/update-to-enable-wsus-support-for-windows-10-feature-upgrades

is there any thing i can do to fix this issue


Thank you 


Windows Server 2012 R2 Foundation still reboots after last update

$
0
0
Good morning!
It will not start after yesterday's update and server restart. It only loads, then displays "Install Update 2 of 5", then displays "Notifying services that Windows is shutting down" And the server will restart over and over. Please get advice on how to fix the problem, Thank you.

1909 Machines Reporting to WSUS as Build 18362 Instead of 18363

$
0
0

I'm running WSUS (standalone) on Server 2019.  All of our pilot machines on Windows 10 1909 are reporting to WSUS with build numbers of 18362 (1903) instead of 18363 (1909).

I understand that 1903/1909 share the same baseline and that the difference between them is basically a feature enablement package, but the different build numbers still need to be properly reported in WSUS. Otherwise, a whole bunch of reporting that I do just goes out the window.

Windows 2012 Server stuck in loop

$
0
0

Hello All ,

After installing December month patches, couple of Windows 2012 Server stuck in restart loop. Can anyone confirm is there any known issue with December 2019 patches ?

Does anyone face this issue?

Resolution is already there:

To break the loop you need to press F8 and select safe mode. Server will most likely take another reboot but will come up after that.

Thanks

Baneesh


Regards Baneesh Pal Singh

The server certificate did not comply with the following policy: WindowsUpdateCertificatePolicy

$
0
0

Please explain me this WSUS error:

ErrorWsusService.20ServerCertificateValidator.VerifyServerCertificate
The server certificate did not comply with the following policy: WindowsUpdateCertificatePolicy

   in Microsoft.UpdateServices.Internal.ServerCertificateValidator.VerifyServerCertificate(Object sender, X509Certificate certificate, X509Chain chain, SslPolicyErrors sslPolicyErrors)

I can not find any description. What WSUS certificate must have to comply with WindowsUpdateCertificatePolicy? Where are any description about WSUS WindowsUpdateCertificatePolicy?


Thank you

run offine wsus server

$
0
0

hi,

I have a local domain, my dc os is windows server 2008r2 ,

I want run a offline wsus server in network. but thise errore is show (the update could not be found. there may be a network connection issue)

please help.

Windows 10 machines not pulling approved updates

$
0
0

I have a brand new 2019 WSUS server deployed but my Windows 10 machines are not pulling updates

A manual check for updates reports "You're up to date" while WSUS reports the machine has 290+ updates needed.

Machines are registering to WSUS just fine, and seem to be reporting in, but they can't seem to identify that there are patches available for them.

WSUS Setting

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=dword:00000000
"DisableWindowsUpdateAccess"=dword:00000000
"DisableDualScan"=dword:00000001
"WUServer"="http://wsus2019:8530"
"WUStatusServer"="http://wsus2019:8530"
"UpdateServiceUrlAlternate"="http://wsus2019:8530"
"TargetGroupEnabled"=dword:00000001
"TargetGroup"="Computers"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RebootRelaunchTimeout"=dword:000001b8
"RebootWarningTimeoutEnabled"=dword:00000001
"RebootWarningTimeout"=dword:0000001e
"AutoInstallMinorUpdates"=dword:00000000
"UseWUServer"=dword:00000001
"DetectionFrequencyEnabled"=dword:00000001
"DetectionFrequency"=dword:0000000c
"NoAutoUpdate"=dword:00000000

2019/12/14 10:45:37.0474453 5804  11408 ComApi          * START *   Federated Search ClientId = UpdateOrchestrator (cV: nRDIbm1v0k2E3P2d.1.1.0)
2019/12/14 10:45:37.0507151 11588 12228 IdleTimer       WU operation (SR.UpdateOrchestrator ID 5) started; operation # 20; does use network; is not at background priority
2019/12/14 10:45:37.0535179 11588 11940 IdleTimer       WU operation (SR.UpdateOrchestrator ID 5, operation # 20) stopped; does use network; is not at background priority
2019/12/14 10:45:37.0541495 5804  4264  ComApi          Federated Search: Starting search against 1 service(s) (cV = nRDIbm1v0k2E3P2d.1.1.0)
2019/12/14 10:45:37.0543877 5804  4264  ComApi          * START *   Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7, Flags: 0X40010410 (cV = nRDIbm1v0k2E3P2d.1.1.0.0)
2019/12/14 10:45:37.0571995 11588 1432  IdleTimer       WU operation (CSearchCall::Init ID 6) started; operation # 23; does use network; is not at background priority
2019/12/14 10:45:37.0654719 11588 1432  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 6]
2019/12/14 10:45:37.0654986 11588 1432  Agent           Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
2019/12/14 10:45:37.0655099 11588 1432  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
2019/12/14 10:45:37.0655208 11588 1432  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
2019/12/14 10:45:37.0656967 11588 11820 Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
2019/12/14 10:45:37.0700457 11588 10868 Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 6]
2019/12/14 10:45:37.0751100 11588 10868 Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 6 (cV = nRDIbm1v0k2E3P2d.1.1.0.0.2)
2019/12/14 10:45:37.0751253 11588 10868 Agent           Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = No
2019/12/14 10:45:37.0751354 11588 10868 Agent           Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsInstalled=0 and DeploymentAction='OptionalInstallation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
2019/12/14 10:45:37.0751442 11588 10868 Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019/12/14 10:45:37.0751477 11588 10868 Agent           Search Scope = {Machine}
2019/12/14 10:45:37.0751602 11588 10868 Agent           Caller SID for Applicability: S-1-5-21-3156452373-2460497579-2355296147-500
2019/12/14 10:45:37.0751628 11588 10868 Agent           ProcessDriverDeferrals is set
2019/12/14 10:45:37.2100562 11588 10868 Misc            Got WSUS Client/Server URL: http://wsus2019:8530/ClientWebService/client.asmx""
2019/12/14 10:45:37.2188540 11588 10868 Driver          Skipping printer driver 5 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
2019/12/14 10:45:38.0594723 11588 10868 ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus2019:8530/ClientWebService/client.asmx
2019/12/14 10:45:38.0598619 11588 10868 ProtocolTalker  OK to reuse existing configuration
2019/12/14 10:45:38.0598950 11588 10868 ProtocolTalker  Existing cookie is valid, just use it
2019/12/14 10:45:38.0599029 11588 10868 ProtocolTalker  PTInfo: Server requested registration
2019/12/14 10:45:39.8280010 4016  5472  Misc            *FAILED* [80010106] ReadPolicy: failed
2019/12/14 10:45:48.2159840 11588 10868 Misc            Update B32E464F-2E4A-4109-9018-33583A079A8A is sticky.
2019/12/14 10:45:48.3850582 11588 10868 IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 24; does use network; is at background priority
2019/12/14 10:45:48.3851510 11588 10868 WebServices     Auto proxy settings for this web service call.
2019/12/14 10:45:48.7734683 11588 10868 IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 24) stopped; does use network; is at background priority
2019/12/14 10:45:48.8932102 11588 10868 Misc            Update B32E464F-2E4A-4109-9018-33583A079A8A is sticky.
2019/12/14 10:45:49.0357711 11588 10868 IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 25; does use network; is at background priority
2019/12/14 10:45:49.0886584 11588 10868 IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 25) stopped; does use network; is at background priority
2019/12/14 10:45:49.0886866 11588 10868 ProtocolTalker  SyncUpdates round trips: 2
2019/12/14 10:47:28.2021201 11588 10868 Agent           Found 0 updates and 102 categories in search; evaluated appl. rules of 3966 out of 5580 deployed entities
2019/12/14 10:47:28.2236935 11588 10868 Agent           * END * Finding updates CallerId = UpdateOrchestrator, Id = 6, Exit code = 0x00000000 (cV = nRDIbm1v0k2E3P2d.1.1.0.0.2)


Update for Windows Server 2012 R2 (KB3172614)

$
0
0

Hi All,

I am trying to install Windows update on Windows Server 2012 R2 (KB3172614) unable to install, instalation failing. could you please help me on this.

Installation status: Failed

Error details: Code 800F0831

Thanks,

Venkat.


Ramana rao


WIndows Server 2019 will not Update

$
0
0

Hello,

We rolled out server 2019 in our environment recently and most of our Domain Controllers will not update. Is there a settings or configuration that we need to turn on for this? Thank you.

Windows 10 machines not picking up any patches from WSUS on SUP?

$
0
0
We're running WSUS service on a software update point (SUP) on SCCM server.

And this is our configuration:

Product category:

windows 10
windows 10 LTSB
windows 10, version 1903 and later

Patch Classification:

Critical
Security

Windows 10 machines check the updates from WSUS running under SUP on SCCM, and say no patch missing or applicable in the logs.
Although, there are many patches which are not installed, so there's a conflict.

And we're able to deploy patches for office using this setup, so communication and configuration is all good at the server and client end.

Now, my question is do we need to enable "Update Rollups" as well in Classifications for WSUS or what could possibly the reason behind for patches not getting qualified for installation while it says that patch is for that particular OS on windows update catalog?
Maybe that's why the new patches are not getting eligible for installation.

Wsus employees moving to branch offices

$
0
0

Hello,

1# We are having some problems with the deployment of updates:

ISSUE:  We have deployed the GPO for WSUS on Computers of the Central Office, but we have visualized that some employees move to branch offices with his c and this causes them to update from those offices, causing slowness in the networks of that office.

We havr 5mb mpls, I imagine they will understand,.

We want to know what do yoy do to solved this situation so that computera not going to update outside their local network?

Question 2 We have not yet deployed wsus in branches

What is the best way? Replica or Downstream?

WSUS Backup Server

$
0
0

Hi Guys,

One of my customer wants Secondary Server for WSUS Server Similar to Secondary ( Backup ) Active Directory in case of Failure.       

Consider a scenario : There are two WSUS Server on same network One is active and other is Redundant(Cold Spare or Backup). Widows Update Patches are received from Upstream Server. Both will be synchronized simultaneously . When Active Fails due to Power or Server Failure then Redundant as to come in to action until other is recovered. 

Can we provide such solution . If yes can anyone explain how and If not tell me best solution like WSUS Database backup etc.

Note : All are physical servers no virtualization.

How does Orchestrator determine which updates should apply to my computer?

$
0
0

I found this post "How Windows Update works"(https://docs.microsoft.com/en-us/windows/deployment/update/how-windows-update-works#downloading-updates), It really helped me a lot, but I still have some questions about it.

1.How does Orchestrator(or might be Arbiter) determine which updates should apply to my computer? According to what? The manifest files? And what's inside the manifest files?

2.Is there any "sequence" of updating windows patches from WU or WSUS? Will it run automatically in sequence?

3.Are there any "dependency" issues between Bundle update and Child update? If WU client has already downloaded/installed one of Bundle update, but hasn't done reboot yet, will it's Children(Child update) be downloaded/installed?

I would appreciate any help.

 

Viewing all 12874 articles
Browse latest View live


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