Hi experts
I am facing issue on two windows servers 2012 R2 and two windows servers 2016, We are using WSUS, and i am not able to update Microsoft patches through WSUS on these servers, i am getting error 80244019 on window server 2012 R2 and error 0x80244019 on windows server 2016.
i have stopped windows update service on windows server 2012 R2, deleted software distribtuion folder and started windows update service, i have restarted BITS service, issue is the same. Experts guide me on this
Hi Team,
i am getting the below error on post installation of WSUS server.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
i am using WID
the log files gives the below error.
2019-01-10 23:46:08 Postinstall started
2019-01-10 23:46:08 Detected role services: Api, UI, WidDatabase, Services
2019-01-10 23:46:08 Start: LoadSettingsFromParameters
2019-01-10 23:46:08 Content local is: True
2019-01-10 23:46:08 Content directory is: sccmsrvhamdbs11.abc.com
2019-01-10 23:46:08 SQL instname is:
2019-01-10 23:46:08 End: LoadSettingsFromParameters
2019-01-10 23:46:08 Start: Run
2019-01-10 23:46:08 Fetching WsusAdministratorsSid from registry store
2019-01-10 23:46:08 Value is S-1-5-21-4268575216-2807771012-2215709554-1012
2019-01-10 23:46:08 Fetching WsusReportersSid from registry store
2019-01-10 23:46:08 Value is S-1-5-21-4268575216-2807771012-2215709554-1013
2019-01-10 23:47:07 Configuring content directory...
2019-01-10 23:47:07 Configuring groups...
2019-01-10 23:47:07 Starting group configuration for WSUS Administrators...
2019-01-10 23:47:07 Found group in regsitry, attempting to use it...
2019-01-10 23:47:10 Writing group to registry...
2019-01-10 23:47:10 Finished group creation
2019-01-10 23:47:10 Starting group configuration for WSUS Reporters...
2019-01-10 23:47:10 Found group in regsitry, attempting to use it...
2019-01-10 23:47:10 Writing group to registry...
2019-01-10 23:47:10 Finished group creation
2019-01-10 23:47:10 Configuring permissions...
2019-01-10 23:47:10 Fetching content directory...
2019-01-10 23:47:10 Fetching ContentDir from registry store
2019-01-10 23:47:10 Value is sccmsrvhamdbs11.abc.com
2019-01-10 23:47:10 Fetching group SIDs...
2019-01-10 23:47:10 Fetching WsusAdministratorsSid from registry store
2019-01-10 23:47:10 Value is S-1-5-21-4268575216-2807771012-2215709554-1012
2019-01-10 23:47:10 Fetching WsusReportersSid from registry store
2019-01-10 23:47:10 Value is S-1-5-21-4268575216-2807771012-2215709554-1013
2019-01-10 23:47:10 Creating group principals...
2019-01-10 23:47:10 Granting directory permissions...
2019-01-10 23:47:10 Granting permissions on content directory...
2019-01-10 23:47:10 Granting registry permissions...
2019-01-10 23:47:10 Granting registry permissions...
2019-01-10 23:47:10 Granting registry permissions...
2019-01-10 23:47:10 Configuring shares...
2019-01-10 23:47:10 Configuring network shares...
2019-01-10 23:47:10 Fetching content directory...
2019-01-10 23:47:10 Fetching ContentDir from registry store
2019-01-10 23:47:10 Value is sccmsrvhamdbs11.abc.com
2019-01-10 23:47:10 Fetching WSUS admin SID...
2019-01-10 23:47:10 Fetching WsusAdministratorsSid from registry store
2019-01-10 23:47:10 Value is S-1-5-21-4268575216-2807771012-2215709554-1012
2019-01-10 23:47:10 Content directory is local, creating content shares...
2019-01-10 23:47:10 Creating share "UpdateServicesPackages" with path "sccmsrvhamdbs11.abc.com\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually
applications) published on this WSUS system."
2019-01-10 23:47:10 Deleting existing share...
2019-01-10 23:47:10 Creating share...
2019-01-10 23:47:10 Share successfully created
2019-01-10 23:47:10 Creating share "WsusContent" with path "sccmsrvhamdbs11.abc.com\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2019-01-10 23:47:10 Deleting existing share...
2019-01-10 23:47:10 Creating share...
2019-01-10 23:47:10 Share successfully created
2019-01-10 23:47:10 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2019-01-10 23:47:11 Deleting existing share...
2019-01-10 23:47:11 Creating share...
2019-01-10 23:47:11 Share successfully created
2019-01-10 23:47:11 Finished creating content shares
2019-01-10 23:47:11 Stopping service WSUSService
2019-01-10 23:47:11 Stopping service W3SVC
2019-01-10 23:47:11 Configuring WID database...
2019-01-10 23:47:11 Configuring the database...
2019-01-10 23:47:11 Establishing DB connection...
2019-01-10 23:48:11 Re-Establishing Connection to execute Multi User Query ...
2019-01-10 23:48:11 System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is
correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDBConnection()
at Microsoft.UpdateServices.Administration.ConfigureDB.TryEnsureDatabaseIsInMultiUserMode()
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:2,State:0,Class:20
2019-01-10 23:48:11 System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is
correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDBConnection()
at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
at Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal)
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:2,State:0,Class:20
TechGUy,System Administrator.
Hello,
We have WSUS server and being used to deploy patches for set of machines to which WSUS server is joined to through GPO. We have one more set of machines in different domain in same forest\network but we cannot deploy GPO on that domain due to some restrictions.
In this scenario, does modifying the registry settings on client will work? or Is there any other alternative way to redirecting the client to our WSUS?
Appreciate any comments
Regards,
Sunil
Hi,
Are the Updates for the tools "Enterprise WDK (EWDK)" provided by WSUS?
(https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk)
If yes, which products and classifications should be activated under "OPTIONS > Products and Classification" to download the updates?
Best regards
Birdal
So I'm currently trying to get my 2016 WSUS server to update manually, via "Start>Settings>Windows Update" I have gone through a plethora of google searches attempting to figure out why I cannot download updates. Currently the error I'm getting is this:
"There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for more information, this may help:"
Then it gives me two of the updates I'm trying to install (which were approved via WSUS but not installing automatically or manually) and Error 0x80244019.
On top of that, ALL of my 2016 servers are not pulling updates from WSUS. All approved updates are showing "Install" under status and yet none of them are actually installing. I'm assuming it has something to do with the above. As I've tried manually updating some other test servers and get similar errors, but same end result of no updates.
Only thing that seemed to work on the test machines was to add the following to the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Update
DisableWindowsUpdateAccess
DoNotConnectToWindowsUpdateInternetLocations
Both keys set to 0 allowed me to manually download updates.
Any help would be appreciated and hopefully save my hair from being ripped out further.
Jeremiah
Hello,
Although the original Windows server 2016 machine is updating fine, all clones fail.
We made sure to:
point to WSUS server in registry key
run these commands to
i. wuauclt /detectnow
ii. wuauclt /reportnow
iii. wuauclt /resetauthorization
i. net stop wuauserv
ii. reg delete HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate /f /va
iii. net start wuauserv
the machine appears in wsus just fine, but the error :
"There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024401c)"
keeps happening
Windowsupdate Log:
2019/01/17 10:39:44.7450158 832 8048 Agent Bundles 11 updates:
2019/01/17 10:39:44.7450183 832 8048 Agent 53A45ED8-E0CC-4FE6-8FC4-7856A50DDFFF.200
2019/01/17 10:39:44.7450209 832 8048 Agent 99BC9D62-70F6-445C-AE78-8E5E1B3CDCC0.200
2019/01/17 10:39:44.7450234 832 8048 Agent 082A52A7-3F21-4542-B466-CAFB775F8A13.200
2019/01/17 10:39:44.7450255 832 8048 Agent 0A477C63-2F34-4CAF-881D-BEAED5B8AAE9.200
2019/01/17 10:39:44.7450276 832 8048 Agent B99682A6-F04C-40E6-9538-FC5069E28518.200
2019/01/17 10:39:44.7450301 832 8048 Agent 457B663C-CD1F-4883-8521-48BBBC3BD3AB.200
2019/01/17 10:39:44.7450322 832 8048 Agent C991041B-03EF-40C8-BCC8-1F6F037DA523.200
2019/01/17 10:39:44.7450342 832 8048 Agent 2B49FA5E-6437-4AC6-AA10-37C30E41FD62.200
2019/01/17 10:39:44.7450363 832 8048 Agent AAAA5ECE-9563-485A-ACDC-78046AF71AAD.200
2019/01/17 10:39:44.7450383 832 8048 Agent C10EE456-DC04-4D46-8FF2-5B8B1776D94E.200
2019/01/17 10:39:44.7450404 832 8048 Agent 85C78675-8E5C-4A25-AD75-F6BED75F8885.200
2019/01/17 10:39:45.0542502 832 8048 DownloadManager Preparing update for install, updateId = {85C78675-8E5C-4A25-AD75-F6BED75F8885}.200.
2019/01/17 10:39:45.1746883 832 8048 DownloadManager ExtractUpdateFiles: 0x00000000
2019/01/17 10:39:45.1837157 8052 8064 Handler * START * Command Line Install Updates to install = 1
2019/01/17 10:41:07.2862035 832 6360 ComApi * START * Init Search ClientId = UpdateOrchestrator
2019/01/17 10:41:07.2862081 832 6360 ComApi * START * Search ClientId = UpdateOrchestrator
2019/01/17 10:41:07.3112070 832 6360 Agent * START * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 10]
2019/01/17 10:41:07.3112131 832 6360 Agent Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
2019/01/17 10:41:07.3112167 832 6360 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2019/01/17 10:41:07.3114199 832 6360 ComApi Search ClientId = UpdateOrchestrator
2019/01/17 10:41:07.3206670 832 7928 Agent * END * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 10]
2019/01/17 10:41:07.3275360 832 7928 Agent * START * Finding updates CallerId = UpdateOrchestrator Id = 10
2019/01/17 10:41:07.3275371 832 7928 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2019/01/17 10:41:07.3275381 832 7928 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""
2019/01/17 10:41:07.3275412 832 7928 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2019/01/17 10:41:07.3275417 832 7928 Agent Search Scope = {Machine}
2019/01/17 10:41:07.3275448 832 7928 Agent Caller SID for Applicability: S-1-5-21-918298546-3840771252-42394364-14312
2019/01/17 10:41:07.3275453 832 7928 Agent ProcessDriverDeferrals is set
2019/01/17 10:41:07.3275453 832 7928 Agent RegisterService is set
2019/01/17 10:41:07.3391484 832 7928 Misc Got WSUS Client/Server URL: http://172.x.x.1/ClientWebService/client.asmx""
2019/01/17 10:41:07.5294156 832 7928 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://172.x.x.1/ClientWebService/client.asmx
2019/01/17 10:41:07.5295224 832 7928 ProtocolTalker OK to reuse existing configuration
2019/01/17 10:41:07.5295260 832 7928 ProtocolTalker Existing cookie is valid, just use it
2019/01/17 10:41:07.5295270 832 7928 ProtocolTalker PTInfo: Server requested registration
2019/01/17 10:41:08.1358093 832 7928 WebServices Auto proxy settings for this web service call.
2019/01/17 10:42:05.5178166 8052 8064 Handler Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2019/01/17 10:42:05.5181830 8052 8064 Handler * END * Command Line Install 0x0
2019/01/17 10:42:05.5449893 832 8048 Agent LogHistory called. idUpdate={16BA3C3E-76A5-4E3E-A380-72D36188650F}.200, resultMapped=0, resultUnMapped=0
2019/01/17 10:42:05.5542528 832 8048 Agent Installing updates CallerId = Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
2019/01/17 10:42:05.5591429 5748 6692 ComApi Install ClientId = Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
2019/01/17 10:42:05.5591440 5748 6692 ComApi Install call complete (succeeded = 1, succeeded with errors = 0, failed = 0, unaccounted = 0
2019/01/17 10:42:05.5591542 5748 6692 ComApi Reboot required = False
2019/01/17 10:42:05.5591542 5748 6692 ComApi * END * Install ClientId = Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
2019/01/17 10:42:05.5591727 832 5884 Agent WU client calls back to install call {7483F897-135C-4BE5-B879-F44AABF020B5} with code Call complete and error 0
2019/01/17 10:42:05.5734177 5748 7020 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2019/01/17 10:42:05.5832139 5748 7020 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2019/01/17 10:42:05.6122028 5748 7020 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2019/01/17 10:42:07.8900487 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:42:07.8900498 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:42:07.8900503 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:42:07.8901165 832 7928 WebServices WS error: The operation timed out
2019/01/17 10:42:07.8901247 832 7928 WebServices Web service call failed with hr = 8024401c.
2019/01/17 10:42:07.8901252 832 7928 WebServices Current service auth scheme=0.
2019/01/17 10:42:07.8901252 832 7928 WebServices Current Proxy auth scheme=0.
2019/01/17 10:42:09.9057378 832 7928 WebServices Auto proxy settings for this web service call.
2019/01/17 10:43:12.0999376 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:43:12.0999386 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:43:12.0999392 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:43:12.0999402 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:43:12.0999412 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:43:12.0999417 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:43:12.0999422 832 7928 WebServices WS error: The operation timed out
2019/01/17 10:43:12.0999438 832 7928 WebServices Web service call failed with hr = 8024401c.
2019/01/17 10:43:12.0999438 832 7928 WebServices Current service auth scheme=0.
2019/01/17 10:43:12.0999443 832 7928 WebServices Current Proxy auth scheme=0.
2019/01/17 10:43:14.1949627 832 7928 WebServices Auto proxy settings for this web service call.
2019/01/17 10:43:47.1218188 832 2532 Misc Got WSUS Client/Server URL: http://172.x.x.1/ClientWebService/client.asmx""
2019/01/17 10:43:47.1218481 832 2532 ProtocolTalker OK to reuse existing configuration
2019/01/17 10:43:47.1218517 832 2532 ProtocolTalker Existing cookie is valid, just use it
2019/01/17 10:43:47.1218527 832 2532 ProtocolTalker PTInfo: Server requested registration
2019/01/17 10:43:51.0393771 832 2532 Misc Got WSUS Reporting URL: http://172.x.x.1/ReportingWebService/ReportingWebService.asmx""
2019/01/17 10:43:51.0394094 832 2532 WebServices Auto proxy settings for this web service call.
2019/01/17 10:44:15.8910982 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:44:15.8910992 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:44:15.8910997 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:44:15.8911008 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:44:15.8911018 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:44:15.8911023 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:44:15.8911033 832 7928 WebServices WS error: There was an error communicating with the endpoint at 'http://172.x.x.1/ClientWebService/client.asmx'.
2019/01/17 10:44:15.8911038 832 7928 WebServices WS error: There was an error receiving the HTTP reply.
2019/01/17 10:44:15.8911044 832 7928 WebServices WS error: The operation did not complete within the time allotted.
2019/01/17 10:44:15.8911049 832 7928 WebServices WS error: The operation timed out
2019/01/17 10:44:15.8911059 832 7928 WebServices Web service call failed with hr = 8024401c.
2019/01/17 10:44:15.8911064 832 7928 WebServices Current service auth scheme=0.
2019/01/17 10:44:15.8911480 832 7928 WebServices Current Proxy auth scheme=0.
2019/01/17 10:44:15.8911608 832 7928 ProtocolTalker PTError: 0x8024401c
2019/01/17 10:44:15.8911613 832 7928 ProtocolTalker SyncUpdates_WithRecovery failed. 0x8024401c
2019/01/17 10:44:15.8911670 832 7928 ProtocolTalker SyncUpdates round trips: 1
2019/01/17 10:44:15.8911680 832 7928 ProtocolTalker Sync of Updates 0x8024401c
2019/01/17 10:44:15.8911803 832 7928 ProtocolTalker SyncServerUpdatesInternal failed 0x8024401c
2019/01/17 10:44:15.8982535 832 7928 Agent Failed to synchronize, error = 0x8024401C
2019/01/17 10:44:15.9339082 832 7928 Agent Exit code = 0x8024401C
2019/01/17 10:44:15.9339092 832 7928 Agent * END * Finding updates CallerId = UpdateOrchestrator Id = 10
2019/01/17 10:44:15.9533805 832 2024 ComApi *RESUMED* Search ClientId = UpdateOrchestrator
2019/01/17 10:44:15.9537705 832 2024 ComApi Updates found = 0
2019/01/17 10:44:15.9537710 832 2024 ComApi Exit code = 0x00000000, Result code = 0x8024401C
2019/01/17 10:44:15.9537715 832 2024 ComApi * END * Search ClientId = UpdateOrchestrator
2019/01/17 10:44:15.9540604 832 6360 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
I installed the latest cumulative update but it did not solve the problem,
renamed SoftwareDistribution and catroot2 folders but no luck
I changed the settings on the wsuspool (httplevel to tcplevel, limit to 0 aka no limit, queue to 25000 and such ) no luck either
What else can I try please?
Is this expected behavior ?
Accoring to https://msdn.microsoft.com/en-us/library/cc251937.aspx "Reporting Web Service WSDL" this is not optional
Hi,
Can anyone help? Since 16th July 2018, my windows updates are no longer being installed on my Windows 2008 R2 server. This seems to correspond since KB890830 was installed in Jully, however the August KB890830 update did install. Screenshot below of updates which are failing. Any ideas how I resolve?
Updates failing to install are
KB4339093
KB4338818
KB4340556
KB4339093
Plus a whole host more.
Kind regards
Daf
We have a 2016 WSUS server functioning well for all clients except some of our 2016 servers. We have GPO setup up to auto download and notify for install.
I have verified Group Policy is applying to these servers and validated the correct registry entries are present. If i run SCONFIG, I see option 5 set as Download only.
The issue is when I go into the windows update settings on the affected server(s). It shows the server has checked in but no updates are available. It also says updates will be downloaded and installed automatically. If I click Check for updates, it checks and automatically installs the updates then tells me it will reboot outside of active hours.
Some other 2016 servers in the same OU with the exact same policies work like they should. They download the updates automatically but tell me I need to install them.
I have done everything possible to try and resolve this issue from stopping the Windows update service, deleted all windows update registry entries, deleted the software distribution folder and rebooted
I have compared registry entries on good\bad servers and they are identical
I have removed and re-added them to the domain with no luck
There are no local group policies applied only domain level policies
This seems like a bug but I can't confirm it. Any thoughts?
If this is not a bug, is there a fix?
Russ
We have a 50/50 mix of Win7 Pro/Win10 Pro clients in our environment and are running WSUS 6.3.9600.18324 on Server 2012 R2. After updates have been pushed to clients the Win7 machines prompt the use to reboot their machine however the Win10 machines do not and instead the Windows Update screen advises "Your device is scheduled to restart outside of active hours."
How do I override this setting in the GPO? We need the Win10 machines to automatically prompt the user to restart similar to the Win7 clients.
Hank Vare
Hi,
My WSUS is reporting that all my servers (2012, 2012 R2, 2016) do not need KB4476698. I have checked that at least 5 servers have the directory path that contains the vulnerable visual studio exe file. Nessus scan have confirmed the servers require that patch.
Hi All,
I have a few Windows 2008 R2 SP1 64-BIT nodes in my environment which are reporting to WSUS which is also running in the same OS. In the windowsupdate.log it seems all are reporting 2 missing patches. And all of them are only able to receive KB4471318 which keeps failing and understand that I would need to install KB3177467 as a prerequisite before KBB4471318 can be installed.
It appears in the WSUS and have been approve to install, but end nodes is not displaying it on the Window update. How do I make it appear via windows update.
Thanks
Hello,
In my organization we started using wsus. The local environment was no problem and all the client computers connected and picking up updates with no problem, the location of the wsus is provided through a GPO. On a staging level (all vm's) the windows machines are not finding the wsus server. The GPO is applied on the machines and in rsop i can see that the right location is provided on the update rule.
Until now only on VM has reported to the wsus. All the machines are running server 2016 or higher.
I'm a little bit stuck now. Anyone some advice where I can look?
Kind regards,
Rick Kuiper.
Hi all !
I installed and configured a WSUS Service in my organization and it will be used to deploy all security and critical updates for all clients (users computers)
These pc clients are composed of Windows 7 and windows 10 product with little bit of everything (1703,1709,1803 versions.)
But I don't know what to choose from the list of windows 10 product in WSUS.
Knowing that I don't want to download unnecessary update to my organization and avoid overloading the wsus server.
Currently, I checked only Windows 7 and Windows 10...
Is it enough or I forget a lot of update ???
I looked the differences of each version listed but I do not quite understand what they mean
Many thanks for your help.
Julien.
Connecting the WSUS server with the hostname is unsuccessful. But what is the reason for the success of using IP connections?
Hi all,
We have a Server 2016 which has been installed Q4 2018 with all latest updates approved from WSUS.
Now when a Nessus scan was run, it came back with a missing KB4343887 update. Now when I checked from Windows Catalog the update issuperseded byKB4471321 and that the KB is irreverent due to the latest cumulative update. Nessus got back to us that we are still vulnerable and need to create a registry key to close the vulnerability like so:
This registry key is required to enable the fix for cve-2017-8529:
SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX\iexplore.exe "
Is this a false positive? or do I need to create the key?
Greetings,
Doing some testing on our test environment with the 1809 update. After the update the systems will not check the WSUS server for updates but instead will try to reach the internet. This system is not internet connected so it fails. Here is the log from the last run. Can anyone tell me where to start looking?
I have tried to stop the services and rename the SoftwareDistribution folder but that didn't help either.
Any ideas?
2018/11/27 08:22:00.8405505 6132 8772 Shared InitializeSus
2018/11/27 08:22:00.8410335 6132 8772 IdleTimer Non-AoAc machine. Aoac operations will be ignored.
2018/11/27 08:22:00.8411397 6132 8772 Agent WU client version 10.0.17763.107
2018/11/27 08:22:00.8414541 6132 8772 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker
disabled.
2018/11/27 08:22:00.8415346 6132 8772 Agent Base directory: C:\WINDOWS\SoftwareDistribution
2018/11/27 08:22:00.8451521 6132 8772 Agent Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore
\DataStore.edb
2018/11/27 08:22:00.8461652 6132 8772 DataStore JetEnableMultiInstance succeeded - applicable param count: 5,
applied param count: 5
2018/11/27 08:22:01.3599102 6132 8772 DataStore Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
2018/11/27 08:22:01.4069797 6132 8772 DataStore Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
2018/11/27 08:22:01.4292586 6132 8772 DataStore Data store successfully created
2018/11/27 08:22:01.4344485 6132 8772 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/11/27 08:22:01.4350496 6132 8772 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/11/27 08:22:01.4396549 6132 8772 Shared Network state: Connected
2018/11/27 08:22:01.8532419 6132 8772 Misc *FAILED* [8024000C] LoadHistoryEventFromRegistry completed
2018/11/27 08:22:01.8534011 6132 8772 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/11/27 08:22:01.8534088 6132 8772 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/11/27 08:22:01.8534180 6132 8772 Shared Power status changed
2018/11/27 08:22:01.8580060 6132 8772 Agent WU client refresh cache for DisableWUAccess policy: 1
2018/11/27 08:22:01.8580098 6132 8772 Agent Initializing global settings cache
2018/11/27 08:22:01.8580112 6132 8772 Agent WSUS server: http://WSUSSERVER:8530
2018/11/27 08:22:01.8580127 6132 8772 Agent WSUS status server: http://WSUSSERVER:8530
2018/11/27 08:22:01.8580140 6132 8772 Agent Alternate Download Server: http://WSUSSERVER:8530
2018/11/27 08:22:01.8580152 6132 8772 Agent Fill Empty Content Urls: No
2018/11/27 08:22:01.8580163 6132 8772 Agent Target group: Update Testing
2018/11/27 08:22:01.8580174 6132 8772 Agent Windows Update access disabled: Yes
2018/11/27 08:22:01.8580187 6132 8772 Agent Do not connect to Windows Update Internet locations: No
2018/11/27 08:22:01.8802420 6132 8772 Agent Initializing Windows Update Agent
2018/11/27 08:22:01.8804247 6132 8772 Agent CPersistentTimeoutScheduler | GetTimer, returned hr = 0x80248007
2018/11/27 08:22:01.8804356 6132 8772 Agent CPersistentTimeoutEvent | Resubscribe, no existing/cached timer
for Id=29A863E7-8609-4D1E-B7CD-5668F857F1DB.
2018/11/27 08:22:01.8804472 6132 8772 Agent Adding timer:
2018/11/27 08:22:01.8804538 6132 8772 Agent Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-11-
28 13:22:01, not idle-only, not network-only
2018/11/27 08:22:01.8821476 6132 8772 IdleTimer IdleTimer::NetworkStateChanged. Network connected? Yes
2018/11/27 08:22:01.9130973 6132 3044 DownloadManager Received power state change notification: Old: <unknown>; New: AC.
2018/11/27 08:22:01.9130995 6132 3044 DownloadManager Power state changed from <unknown> to AC.
2018/11/27 08:22:32.1551466 6068 644 ComApi IUpdateServiceManager::AddService2
2018/11/27 08:22:32.1551509 6068 644 ComApi Service ID = {7971f918-a847-4430-9279-4a52d1efe18d}
2018/11/27 08:22:32.1551547 6068 644 ComApi Allow pending registration = Yes; Allow online registration = Yes;
Register service with AU = Yes
2018/11/27 08:22:32.1695762 6132 5316 Agent *FAILED* [80248014] GetServiceObject couldn't find service
'117CAB2D-82B1-4B5A-A08C-4D62DBEE7782'.
2018/11/27 08:22:32.1695836 6132 5316 Agent *FAILED* [80248014] Method failed
[CAgentServiceManager::GetServiceObject:1902]
2018/11/27 08:22:32.1695913 6132 5316 Agent *FAILED* [80248014] GetServiceObject couldn't find service
'855E8A7C-ECB4-4CA3-B045-1DFA50104289'.
2018/11/27 08:22:32.1695958 6132 5316 Agent *FAILED* [80248014] Method failed
[CAgentServiceManager::GetServiceObject:1902]
2018/11/27 08:22:32.1696030 6132 5316 Agent *FAILED* [80248014] GetServiceObject couldn't find service
'7971F918-A847-4430-9279-4A52D1EFE18D'.
2018/11/27 08:22:32.1696072 6132 5316 Agent *FAILED* [80248014] Method failed
[CAgentServiceManager::GetServiceObject:1902]
2018/11/27 08:22:32.2112812 6132 5316 SLS Get response for service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 -
forceExpire[False] asyncRefreshOnExpiry[False]
2018/11/27 08:22:32.2113895 6132 5316 SLS Retrieving SLS response from server...
2018/11/27 08:22:32.2122669 6132 5316 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/
{117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 and send SLS events.
2018/11/27 08:22:43.2776497 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:22:43.2778084 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:22:54.3387187 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:22:54.3388610 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:0
2018/11/27 08:23:05.4082514 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:23:05.4082755 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:23:16.4895818 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:23:16.4896129 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:1
2018/11/27 08:23:27.5883974 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:23:27.5884365 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:23:38.6812111 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:23:38.6812414 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:2
2018/11/27 08:23:49.7840964 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:23:49.7841295 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:24:00.8383570 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:00.8383975 6132 5316 SLS Complete the request URL HTTPS://sls.update.microsoft.com/SLS/
{117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 with [8024402C] and http status code[0] and send SLS events.
2018/11/27 08:24:00.8384340 6132 5316 SLS *FAILED* [8024402C] GetDownloadedOnWeakSSLCert
2018/11/27 08:24:00.8385510 6132 5316 SLS *FAILED* [8024402C] Method failed [CSLSClient::GetResponse:622]
2018/11/27 08:24:00.8385767 6132 5316 Agent Failed to retrieve SLS response data for service 117cab2d-82b1-
4b5a-a08c-4d62dbee7782, error = 0x8024402c
2018/11/27 08:24:00.8386132 6132 5316 Agent *FAILED* [8024402C] Caller Service Recovery failed to opt in to
service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 (cV: 06PYBxxVUUCkfiBT.1)
2018/11/27 08:24:00.9255258 6132 5316 SLS Get response for service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 -
forceExpire[False] asyncRefreshOnExpiry[False]
2018/11/27 08:24:00.9256829 6132 5316 SLS Retrieving SLS response from server...
2018/11/27 08:24:00.9263204 6132 5316 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/
{855E8A7C-ECB4-4CA3-B045-1DFA50104289}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 and send SLS events.
2018/11/27 08:24:12.0005654 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:12.0005943 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:24:23.0594036 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:23.0594343 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:0
2018/11/27 08:24:34.1679051 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:34.1679337 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:24:45.2300423 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:45.2300919 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:1
2018/11/27 08:24:56.2883156 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:24:56.2883299 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:25:07.3589530 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:25:07.3589838 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:2
2018/11/27 08:25:18.4192188 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:25:18.4193169 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:25:29.4799506 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:25:29.4799969 6132 5316 SLS Complete the request URL HTTPS://sls.update.microsoft.com/SLS/
{855E8A7C-ECB4-4CA3-B045-1DFA50104289}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 with [8024402C] and http status code[0] and send SLS events.
2018/11/27 08:25:29.4800215 6132 5316 SLS *FAILED* [8024402C] GetDownloadedOnWeakSSLCert
2018/11/27 08:25:29.4801658 6132 5316 SLS *FAILED* [8024402C] Method failed [CSLSClient::GetResponse:622]
2018/11/27 08:25:29.4801887 6132 5316 Agent Failed to retrieve SLS response data for service 855e8a7c-ecb4-
4ca3-b045-1dfa50104289, error = 0x8024402c
2018/11/27 08:25:29.4802182 6132 5316 Agent *FAILED* [8024402C] Caller Service Recovery failed to opt in to
service 855e8a7c-ecb4-4ca3-b045-1dfa50104289 (cV: 06PYBxxVUUCkfiBT.2)
2018/11/27 08:25:29.5743735 6132 5316 SLS Get response for service 7971F918-A847-4430-9279-4A52D1EFE18D -
forceExpire[False] asyncRefreshOnExpiry[True]
2018/11/27 08:25:29.5745969 6132 5316 SLS Retrieving SLS response from server...
2018/11/27 08:25:29.5758309 6132 5316 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/
{7971F918-A847-4430-9279-4A52D1EFE18D}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 and send SLS events.
2018/11/27 08:25:40.6231711 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:25:40.6231954 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:25:51.6776217 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:25:51.6777224 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:0
2018/11/27 08:26:00.1852773 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:00.1853026 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:26:11.2338180 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:11.2338557 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:1
2018/11/27 08:26:22.3356747 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:22.3356988 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:26:33.4030335 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:33.4030651 6132 5316 Misc *FAILED* [8024402C] Library download error. Will retry. Retry
Counter:2
2018/11/27 08:26:44.5042011 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:44.5043573 6132 5316 Misc *FAILED* [8024402C] WinHttp: SendRequestToServerForFileInformation
(retrying with default proxy)
2018/11/27 08:26:55.5571490 6132 5316 Misc *FAILED* [80072EE7] Send request
2018/11/27 08:26:55.5571883 6132 5316 SLS Complete the request URL HTTPS://sls.update.microsoft.com/SLS/
{7971F918-A847-4430-9279-4A52D1EFE18D}/x64/10.0.17763.107/0?CH=765&L=en-US&P=&PT=0x30&WUA=10.0.17763.107&MK=Dell+Inc.&MD=Latitude+E5540 with [8024402C] and http status code[0] and send SLS events.
2018/11/27 08:26:55.5572060 6132 5316 SLS *FAILED* [8024402C] GetDownloadedOnWeakSSLCertHi all,
I added windows 2016 server in wsus . It is showing as Windows Server 2008 standard installation .Is there any patch available to update WSUS server . Im running wsus on windows server 2008 R2