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

Windows server update checking for update forever ! 2012

$
0
0

Hi All, 

I am having issue to get windows server update on my DC (windows server 2012 standard), it's checking for update for ever!

so I ran the following commands 

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

chkdsk /f /r /x

no change then I ran script below

https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78

and reboot the server no change , I took advise to get the last cumulative update from Microsoft update catalog website, but when I am running this standalone installer again also checking forever ! I totally remove AV I have restart the server again no luck 

it's a virtual machine running in Hyperv



KB890830 doesn't install via WSUS but can be installed manually

$
0
0

Hi,

 Windows Malicious Software Removal Tool x64 - April 2019 (KB890830) doesn't install via WSUS but can be installed manually on some of our servers. This has increased our workload by having to install this tool manually and running it on affected servers to get a 100% completion report. I have looked at the logs and have not found anything unusual. The client simply reports back to WSUS as it requires this update but doesn't install it even if I have set a deadline against it on WSUS. I would appreciate if anyone can help.

Thanks

WSUS with SSL || Error: 0x8024401f - 0x8024401c

$
0
0

Followed this: https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus

and this http://jackstromberg.com/2013/11/enabling-ssl-on-windows-server-update-services-wsus/ for setup SSL on WSUS.

Assigned/Bind a cert in IIS which was issued by our in house Microsoft Enterprise Root CA.  Currently only one server to which I am trying to deploy updates/patches Server 2016.  Our RootCA certificate is present in the Local Computer Trusted Root CA Store on the test server 2016 and also in the same location on WSUS server.

Client server 2016 is visible/reporting in the WSUS Unassigned Computers Group under Status "Not yet reported"  but not moving to the WSUS Group I created for WSUS_TestServers.  The GPO is setup correctly for client side targeting.

This is what I see in the windowslog file on the client/server 2016:

https://fqdn.local:8531/ClientWebService/client.asmx'.
2019/04/05 09:21:08.3073227 1364  1836  WebServices     WS error: The server returned HTTP status code '500 (0x1F4)' with text 'System.ServiceModel.ServiceActivationException'.
2019/04/05 09:21:08.3073232 1364  1836  WebServices     WS error: The server was unable to process the request.
2019/04/05 09:21:08.3073335 1364  1836  WebServices     Web service call failed with hr = 8024401f.
2019/04/05 09:21:08.3073338 1364  1836  WebServices     Current service auth scheme=0.
2019/04/05 09:21:08.3073341 1364  1836  WebServices     Current Proxy auth scheme=0.
2019/04/05 09:21:08.3073422 1364  1836  ProtocolTalker  PTError: 0x8024401f
2019/04/05 09:21:08.3073425 1364  1836  ProtocolTalker  SyncUpdates_WithRecovery failed. 0x8024401f
2019/04/05 09:21:08.3073467 1364  1836  ProtocolTalker  SyncUpdates round trips: 1
2019/04/05 09:21:08.3073471 1364  1836  ProtocolTalker  Sync of Updates 0x8024401f
2019/04/05 09:21:08.3073530 1364  1836  ProtocolTalker  SyncServerUpdatesInternal failed 0x8024401f
2019/04/05 09:21:08.3106381 1364  1836  Agent           Failed to synchronize, error = 0x8024401F
2019/04/05 09:21:08.3244305 1364  1836  Agent           Exit code = 0x8024401F
2019/04/05 09:21:08.3244314 1364  1836  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 1
2019/04/05 09:21:08.3327902 1364  1584  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
2019/04/05 09:21:08.3334744 1364  1584  ComApi          Updates found = 0
2019/04/05 09:21:08.3334751 1364  1584  ComApi          Exit code = 0x00000000, Result code = 0x8024401F
2019/04/05 09:21:08.3334755 1364  1584  ComApi          * END *   Search ClientId = UpdateOrchestrator
2019/04/05 09:21:08.3340164 1364  7288  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
2019/04/05 09:28:39.2998832 1364  8100  Agent           Refreshing global settings cache
2019/04/05 09:28:39.2998843 1364  8100  Agent           WSUS server: https://fqdn.local:8531 (Unchanged)
2019/04/05 09:28:39.2998849 1364  8100  Agent           WSUS status server: https://fqdn.local:8531 (Unchanged)
2019/04/05 09:28:39.2998852 1364  8100  Agent           Alternate Download Server: NULL (Changed)
2019/04/05 09:28:39.2998855 1364  8100  Agent           Fill Empty Content Urls: No (Unchanged)
2019/04/05 09:28:39.2998858 1364  8100  Agent           Target group: WSUS_TestServers(Unchanged)
2019/04/05 09:28:39.2998861 1364  8100  Agent           Windows Update access disabled: No (Unchanged)
2019/04/05 09:29:08.3558987 1364  8128  Misc            Got WSUS Client/Server URL: https://fqdn.local:8531/ClientWebService/client.asmx""
2019/04/05 09:29:08.3559563 1364  8128  ProtocolTalker  OK to reuse existing configuration

------

Thank you


The clients are not getting updated from WSUS server.

$
0
0

Hi,

We have Windows 2016 WSUS server and windows 10 64 bit clients.

I made a group policy on an ou to update all the pc's in that ou. Even after approving the updates in WSUS, none of the updates are getting installed. Please let me know how to resolve this issue.

[Windows Server 2016]: Error when I trying logon with accout domain controller

$
0
0

Hi Everyone!

My Company run OS Windows Server 2016. Today, when I Login with accout join domain, receive error:

""the truth relationship between this workstation and the primary domain failed"

Can you help me? Fix error

Thanks!

Windows Server 2016 - WSUS Clients - WindowsUpdateFailure3, 1001, 0x8024500c

$
0
0
I've looked at everything I know to look at.

The WSUS Server itself is running Windows Server 2016 DataCenter.

The clients on our network are Windows 7 Enterprise, Windows 7 Professional, Windows 10 Professional, Windows 10 Enterprise, Windows Server 2016 Standard, Windows Server 2016 DataCenter and Windows Server 2008 R2 DataCenter.

Only my Windows Server 2016 clients are having this issue.

I've tried clearing the SoftwareDistrib folder, reregistering DLLs, re-indexing the SQL database, rebooting several times, etc.

Our AD Group Policies are as such that INTERnet-based WSUS are prohibited as we want all updates to come from the local server.

The WSUS server itself shows no signs of sync issues or issues downloading the actual updates.  I am at an absolute loss here.

****

Fault bucket 127883099475, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.14393.1198
P2: 8024500c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 8024500b
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.14393.1198_802d6847332aebf619279c14e8638fd2125bcdcc_00000000_1bf75f67

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2aeac304-5ab2-11e7-90f5-70106fbf9c86
Report Status: 0
Hashed bucket: d1dff83bf57fb9291a38c9f8b68fde52


****

WER File Output

Version=1
EventType=WindowsUpdateFailure3
EventTime=131416677960233426
Consent=1
UploadTime=131429845363147214
ReportIdentifier=f50bdb53-4eb8-11e7-90ef-70106fbf9c86
AppSessionGuid=00000594-0000-0010-960c-34eea1cdd201
TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!00000dac68816ae7c09efc24d11c27c3274dfd147dee!svchost.exe
TargetAppVer=2016//07//16:02:25:32!d1ac!svchost.exe
BootId=4294967295
Response.type=4
Sig[0].Name=ClientVersion
Sig[0].Value=10.0.14393.1066
Sig[1].Name=Win32HResult
Sig[1].Value=8024402f
Sig[2].Name=UpdateID
Sig[2].Value=00000000-0000-0000-0000-000000000000
Sig[3].Name=Scenario
Sig[3].Value=Scan
Sig[4].Name=RevisionID
Sig[4].Value=0
Sig[5].Name=IsManaged
Sig[5].Value=0
Sig[6].Name=LastError
Sig[6].Value=801901f6
Sig[7].Name=CallerAppID
Sig[7].Value=UpdateOrchestrator
Sig[8].Name=ServiceUsed
Sig[8].Value={7971F918-A847-4430-9279-4A52D1EFE18D}
Sig[9].Name=MiscField2
Sig[9].Value=0
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Windows Update installation problem
ConsentKey=WindowsUpdateFailure3
AppName=Host Process for Windows Services
AppPath=C:\Windows\System32\svchost.exe
ReportDescription=A Windows update did not install properly. Sending the following information to Microsoft can help improve the software.
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=410089339


Windows Server 2012 cannot update

$
0
0

I am running an Exchange server (VM ware) on my SB server.  I have tried everything I could find in the forums but cannot get Windows updates on the Exchange server.  Updates on the the SBS and using WSUS are fine.  Updates on the R2 server are fine.

After renaming the update file Windows update just show updates never installed and just searches endlessly.

I have used the Windows troubleshooter.

Stephen

WSUS on win server 2016 cannot download feature updates

$
0
0

Hallo Microsoft,

i am working at company in Berlin


10 days ago i face a problem with WSUS 

WSUS is installed on windows server 2016 and updated already

i cannot install the feature update for windows 10 v1709 or 1803 ... 

and then distribute it to the PCs

in the event viewer i see always this message (Event ID: 364 Content file download failed. Reason: CRC verification failure.)

 i checked a lot of thing : 

- the internet connection with update catalog (Microsoft servers ) is okay

- no proxy server between WSUS and internet

- MIME Types in iis is (File name extension “.esd”, and MIME type is “application/octet-stream”)

- i choose  “Updates are in a specific classification”

- i tried a lot of things with no success

please help me



Server 2016 Servers not auto installing updates

$
0
0

Although I have a GPO set with Auto Updating set to 4- Auto download and schedule the install, the 2016 servers are not auto installing these update or if they do install, they are not rebooting, so I am force to logon and kick off the install.

The WSUS Server is a Windows 2012 R2 Server and all other clients seem in install and reboot per the GPO.

Please advise,

 

Machine not reporting - WSUS on Win2k12R2 Std

$
0
0

Hello fellas !

I have done some research before posting and I am looking for other POV and insights on some stuff that I might miss.

  • Server : Windows Server 2012 R2 Std
  • Issue : Some machines aren't reporting.
  • Method : Using GPO.

I have tried to remove the machine from the WSUS, forcing gpupdate on the computers and run a command that detects the WSUS. Results, they are still not reporting. I have 3 guess at this stage :

  1. Firewall, UAC or Anti-Virus is preventing the process.
  2. Machine does not apply correctly the GPO.
  3. Connection between the server and the machine is broken.

GPUpdate does work. I did a GPResult and it does show that the WSUS GPO is enabled and applied. Other machines with the same configurations are doing fine. Test-Connection from the server to the machine is ok. I do see their IP Addresses on the WSUS Panel.

Thanks,

Nevets24


WSUS - MMC.exe continues to crash

$
0
0

Hello,

My Windows Sevrer 2016 WSUS keeps crashing when I try to view large reports.

Below are the errors:

Faulting application name: mmc.exe, version: 10.0.14393.2608, time stamp: 0x5bd1383b
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2848, time stamp: 0x5c7f626e
Exception code: 0xc000041d
Fault offset: 0x0000000000034078
Faulting process id: 0x1730
Faulting application start time: 0x01d4f46c3eb767c0
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 2b91e4c6-da5d-4191-9b22-aa011d664b43
Faulting package full name: 
Faulting package-relative application ID: 

Application: mmc.exe

Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
   at Microsoft.UpdateServices.UI.SnapIn.Dialogs.BaseReportDialog.RenderingComplete()
   at Microsoft.UpdateServices.UI.SnapIn.Dialogs.BaseUpdateComputerReportDialog.RenderingComplete()
   at Microsoft.Reporting.WinForms.ReportViewer.OnRenderingComplete(System.Object, System.ComponentModel.AsyncCompletedEventArgs)
   at Microsoft.Reporting.WinForms.AsyncReportOperation.EndAsyncExecution(System.Exception)
   at Microsoft.Reporting.WinForms.ReportViewer+<>c__DisplayClass1.<OnBackgroundThreadCompleted>b__0()
   at Microsoft.Reporting.WinForms.ReportViewer.ProcessAsyncInvokes()
   at Microsoft.Reporting.WinForms.ReportViewer.Reset()
   at Microsoft.UpdateServices.UI.SnapIn.Dialogs.BaseReportDialog.FormClose(System.Windows.Forms.FormClosingEventArgs)
   at System.Windows.Forms.Form.OnFormClosing(System.Windows.Forms.FormClosingEventArgs)
   at System.Windows.Forms.Form.WmClose(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

Exception Info: System.Reflection.TargetInvocationException
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.OnThreadException(System.Object, System.Threading.ThreadExceptionEventArgs)
   at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)
   at System.Windows.Forms.Control.WndProcException(System.Exception)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

Has anyone seen this issue and aware of a solution? Thanks

WSUS - Report only - approve update for uninstall

$
0
0

Hello,

I currently have a WSUS server that is set to autodownload and approve updates.

I am considering using WSUS for reports only and letting my win10 machines go to the internet for updates.

I have a few questions hopefully I can get answered.

1) If I use WSUS for reporting only, Can I Mark updates for removal and will the machines uninstall once they report into WSUS?

2) If so, can I mark specific device's (one or two machines) as "approved for removal" or is it a one and done..

Approve update for removal and it removed it from all systems?


Please advise.


Thanks

WSUS 2019 Not Syncing

$
0
0
I Built a server 2019 WSUS Server and it synced up but then stopped with no real error codes that gave answers. Anyone have this issue with Server 2019 WSUS?

Win8.1 Pro Clients not reporting to WSUS

$
0
0

I have server 2012 R2 with WSUS role and need to update windows 8.1 Pro clients.

Client was showing with not yet reported status so I have deleted same from console but after same it has not showing again in unassigned computers.

Above mentioned client was added in domain also.

Please help me...


Durgesh Palav

Wsus on server 2019

$
0
0

Hi, I'm have installed WSUS on server 2019 and everything seems to be running fine, except I'm getting a warning "Feature Unavailable" The Microsoft Report Viewer 2012 Redistributable is required for this feature.

I have installed ReportBuilder, ReportViewer and SQLSysCLrTypes as suggesting in a solution to get WSUS Working on server 2016, but on server 2019 the message keeps popping up.

Has anybody got it working on server 2019?


WSUS suddenly can't communicate with Servers on a different Subnet

$
0
0

All of sudden, I have some servers that cannot communicate with WSUS that are on a different subnet.  This hasn't been an issue in the past and seems to have started 12 days ago or so.

Here is an excerpt of WindowsUpdate.log from one of the servers:

 

2019-04-1105:27:07:13784436b0AgentWARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2019-04-1105:27:07:13784436b0Agent  * Base directory: C:\Windows\SoftwareDistribution
2019-04-1105:27:07:13784436b0Agent  * Access type: No proxy
2019-04-1105:27:07:13784436b0ServiceUpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-1105:27:07:13784436b0ServiceUpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-1105:27:07:13784436b0Agent  * Network state: Connected
2019-04-1105:27:07:13784436b0ServiceUpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-1105:27:07:13784436b0ServiceUpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-1105:27:07:15284436b0MiscWARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2019-04-1105:27:07:15284440a4Agent***********  Agent: Initializing global settings cache  ***********
2019-04-1105:27:07:15284440a4Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2019-04-1105:27:07:15284440a4Agent  * WSUS server: <NULL>
2019-04-1105:27:07:15284440a4Agent  * WSUS status server: <NULL>
2019-04-1105:27:07:15284440a4Agent  * Target group: (Unassigned Computers)
2019-04-1105:27:07:15284440a4Agent  * Windows Update access disabled: No
2019-04-1105:27:07:16884436b0WuTaskWuTaskManager delay initialize completed successfully..
2019-04-1105:27:07:16884436b0AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-11 15:56:36, not idle-only, not network-only
2019-04-1105:27:07:16884436b0AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2019-04-12 02:28:01, not idle-only, not network-only
2019-04-1105:27:07:16884436b0AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-04-12 02:27:59, not idle-only, not network-only
2019-04-1105:27:07:16884436b0ReportCWERReporter::Init succeeded
2019-04-1105:27:07:16884436b0Agent***********  Agent: Initializing Windows Update Agent  ***********
2019-04-1105:27:07:16884436b0DnldMgrDownload manager restoring 0 downloads
2019-04-1105:27:07:16884436b0AU###########  AU: Initializing Automatic Updates  ###########
2019-04-1105:27:07:16884436b0AUAdditional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
2019-04-1105:27:07:16884436b0AUAIR Mode is disabled
2019-04-1105:27:07:16884436b0AU  # Approval type: Scheduled (User preference)
2019-04-1105:27:07:16884436b0AU  # Auto-install minor updates: Yes (Policy)
2019-04-1105:27:07:16884436b0AU  # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-download notify)
2019-04-1105:27:07:16884436b0AU  # Will interact with non-admins (Non-admins are elevated (User preference))
2019-04-1105:27:07:16884436b0MiscWARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 6, GetLastError=2250
2019-04-1105:27:07:18384436b0AUWARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2019-04-1105:27:07:18384436b0AUWARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-1105:27:07:18384436b0AUAU finished delayed initialization
2019-04-1105:27:07:18384436b0AUCurrently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-1105:27:07:18384436b0AUWARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-1105:27:07:18384436b0AUWARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-1105:27:07:183844518cDnldMgrAsking handlers to reconcile their sandboxes
2019-04-1105:37:07:19484446b8AUEarliest future timer found: 
2019-04-1105:37:07:19484446b8AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-11 15:56:36, not idle-only, not network-only
2019-04-1105:37:08:19484436b0AU###########  AU: Uninitializing Automatic Updates  ###########
2019-04-1105:37:08:21084436b0WuTaskUninit WU Task Manager
2019-04-1105:37:08:22684436b0AgentSending shutdown notification to client
2019-04-1105:37:08:22643887ecCOMAPIWARNING: Received service shutdown/self-update notification.
2019-04-1105:37:08:22684436b0AUEarliest future timer found: 
2019-04-1105:37:08:22684436b0AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-11 15:56:36, not idle-only, not network-only
2019-04-1105:37:08:24184436b0AUEarliest future timer found: 
2019-04-1105:37:08:24184436b0AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-11 15:56:36, not idle-only, not network-only
2019-04-1105:37:08:28884436b0Service*********
2019-04-1105:37:08:28884436b0Service**  END  **  Service: Service exit [Exit code = 0x240001]
2019-04-1105:37:08:28884436b0Service*************
2019-04-1105:57:07:1918445b0cMisc===========  Logging initialized (build: 7.9.9600.19164, tz: -0400)  ===========
2019-04-1105:57:07:1918445b0cMisc  = Process: C:\Windows\system32\svchost.exe
2019-04-1105:57:07:1918445b0cMisc  = Module: c:\windows\system32\wuaueng.dll
2019-04-1105:57:07:1918445b0cService*************
2019-04-1105:57:07:1918445b0cService** START **  Service: Service startup
2019-04-1105:57:07:1918445b0cService*********
2019-04-1105:57:07:2078445b0cIdleTmrNon-AoAc machine.  Aoac operations will be ignored.
2019-04-1105:57:07:2078445b0cAgent  * WU client version 7.9.9600.19164
2019-04-1105:57:07:2078445b0cAgentWARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2019-04-1105:57:07:2078445b0cAgent  * Base directory: C:\Windows\SoftwareDistribution
2019-04-1105:57:07:2078445b0cAgent  * Access type: No proxy
2019-04-1105:57:07:2078445b0cServiceUpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-1105:57:07:2078445b0cServiceUpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-1105:57:07:2078445b0cAgent  * Network state: Connected
2019-04-1105:57:07:2078445b0cServiceUpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-1105:57:07:2078445b0cServiceUpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-1105:57:07:2238445b0cMiscWARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2019-04-1105:57:07:223844403cAgent***********  Agent: Initializing global settings cache  ***********
2019-04-1105:57:07:223844403cAgent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2019-04-1105:57:07:223844403cAgent  * WSUS server: <NULL>
2019-04-1105:57:07:223844403cAgent  * WSUS status server: <NULL>
2019-04-1105:57:07:223844403cAgent  * Target group: (Unassigned Computers)
2019-04-1105:57:07:223844403cAgent  * Windows Update access disabled: No
2019-04-1105:57:07:2238445b0cWuTaskWuTaskManager delay initialize completed successfully..
2019-04-1105:57:07:2238445b0cAU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-11 15:56:36, not idle-only, not network-only
2019-04-1105:57:07:2238445b0cAU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2019-04-12 02:28:01, not idle-only, not network-only
2019-04-1105:57:07:2238445b0cAU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-04-12 02:27:59, not idle-only, not network-only
2019-04-1105:57:07:2238445b0cReportCWERReporter::Init succeeded
2019-04-1105:57:07:2238445b0cAgent***********  Agent: Initializing Windows Update Agent  ***********
2019-04-1105:57:07:2238445b0cDnldMgrDownload manager restoring 0 downloads


Windows server 2016 WSUS not downloading updates

$
0
0

Good day,

Just set up WSUS for the first time on a windows 2016 server, I am new to this,

the installation went through with no problems, did selection for which updates I wanted, created the group policies,

made sure that the exceptions are set in the servers firewall, it loaded the computers from my network, but it downloaded 18.36 mb of 6,534 Mb of downloads and stopped... for the past two days. and 

From time to time i the wsus app crashes and asks to be reset

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The operation has timed out

Source
System.Web.Services

Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, UpdateScope updatesToInclude, ComputerTargetScope computersToInclude, UpdateServerStatusPropertiesToGet propertiesToGet)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetReplicaStatus(UpdateSources updateSources)
   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache()
   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

I went as far as setting the private memory limit to 0 in the IIS manager for the wsus pool, it doesnt crash as often but still crashes though the server has 32gigs of ram.

Are there any suggestions on what I may be doing wrong and how i can go about resolving this issue. i am mostly concerned about not being able to download the updates though they have already been set in the wizard.

Thanks in advance for your time.

Is there any necessity there to install older updates if it had already superseded ?

$
0
0

Client says their compliance tools says following 

Apply Security Only update KB4343888 or Cumulative Update KB4343898 as well as refer to the KB article for additional information. 
* Apply Security Only update KB4471322 or Cumulative Update KB4471320. 
* Apply Security Only update KB4480964 or Cumulative Update KB4480963.

But I had already installed latest Patch (2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)) and MS Catalog says KB4493446 replace all above.

Not sure why would some tool says the machine needs some old updates though the latest patches are installed.

Is there any necessity there to install older updates if it had already superseded ?

Can I ask them to ignore?

An error occurred trying to connect the WSUS Server

$
0
0

Hello

We using WSUS server for client and Server patching. We facing one error. Find attachment of the same. 

An error occurred trying to connect the WSUS Server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

Newly Migrated W2016 WSUS Client Connection Fail

$
0
0

Hello,

I installed WSUS/IIS roles on a W2016 server and had it sync to our soon to be retired W2008 WSUS server as it's upstream server, where computer groups and update history populated correctly.  I then set W2016 WSUS to get updates from microsoft and not an upstream server.  I changed the GPO to point to the new server (e.g. http:\\my.server.com:8530).  I'm getting (0x8024401c) no connection error from clients. 

I tested access to the server via a W10 client with URL http://my.server.com:8530/selfupdate/wuident.cab and I am not prompted to accept the download.  I can initiate the download prompt when calling that URL from the server's browser, and I see Wireshark TCP and TLS1.2 traffic between my test client and the Server but only SYN packets and no SYN/ACK.  Windows firewall is deactivated by a GPO and Symantec Firewall is used instead.  However, I've deactivated it while testing.  I've also uninstalled WSUS and reinstalled it through the server management console (it retained the computer groups and update info).

We are behind an Enterprise Firewall and I requested an exception that was set to allow inbound TCP traffic to the server on port 8530 from the client subnet object.  I read someone else's stack exchange post that "The IANA/RFC specifies ephemeral ports TCP 49152 through 65535 open for WSUS to be able to connect back to clients from a W2016 Server, so open that port range from the WSUS server to the client subnet object".  Is this true?  If this is not the issue, I could use some good troubleshooting tips that go beyond the MS Technet Survival guide https://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx and the IIS setting modifications, e.g. https://ininformationtechnologyworld.blogspot.com/2017/06/fixed-wsus-2016-error-code-0x8024401c.html. 

Thanks

Viewing all 12874 articles
Browse latest View live


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