Hi,

I'm struggling to figure out why my wsus clients aren't reporting in on a regular basis. They seem to only report in if I execute a manual check for updates on the device itself. I have the following GPO set, I'm not sure what else I'm missing.

Computer Configuration/Policies/Administrative Templates/Windows Components/Windows updates/Policy

- Automatic Updates detection frequency --> 22hours

- Configure Automatic Updates --> 3 - Auto download and notify for install

- Specify intranet Microsoft update service location

   - Set the intranet update service for detecting updates (http://[internalwsus]:8530)

   - Set the intranet statistics server (http://[internalwsus]:8530)

I know my intranet settings are valid since the servers to register initially but for whatever reason none of them check within the 22 hour interval. I've left some devices go for several days with no update so I don't think it's a matter of me not letting WSUS do it's thing....

Client: Windows 2016

WSUS Server: Windows 2016

Any advice would be appreciated!

please find the error code which have been coming frequently...if any one have resolution please help me out.

Hello,

When you install the update from Windows update KB4489878 fails and installs it. (Windows server 2008 R2)

The error is:

2019-04-02 10:20:05:242  860 1a10 DnldMgr Asking handler to generate non-range requests.
2019-04-02 10:20:05:242  860 1a10 Handler Generating request for CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E in sandbox C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc
2019-04-02 10:20:05:242  860 1a10 Handler Selecting self-contained because update does not have express payload.
2019-04-02 10:20:05:242  860 1a10 Handler Selected payload type is ptSelfContained
2019-04-02 10:20:05:242  860 1a10 Handler Detected download state is dsStart
2019-04-02 10:20:05:242  860 1a10 Handler Adding Windows6.1-KB4489878-x64.cab (entire file) to request list.
2019-04-02 10:20:05:242  860 1a10 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019-04-02 10:20:06:272  860 1a10 Misc Validating signature for C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc\Windows6.1-KB4489878-x64.cab with dwProvFlags 0x00000080:
2019-04-02 10:20:07:723  860 1a10 Misc  Microsoft signed: Yes
2019-04-02 10:20:07:723  860 1a10 DnldMgr Asking handler to generate non-range requests.
2019-04-02 10:20:07:723  860 1a10 Handler Generating request for CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E in sandbox C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970_ctc
2019-04-02 10:20:07:723  860 1a10 Handler Selecting self-contained because update does not have express payload.
2019-04-02 10:20:07:723  860 1a10 Handler Selected payload type is ptSelfContained
2019-04-02 10:20:07:723  860 1a10 Handler Detected download state is dsHavePackage
2019-04-02 10:20:07:723  860 1a10 Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2019-04-02 10:20:07:723  860 265c AU Launched new AU client for directive 'Download Approval', session id = 0x2
2019-04-02 10:20:07:738 5040 3014 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:07:738 5040 3014 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:07:738 5040 3014 AUClnt Launched Client UI process
2019-04-02 10:20:07:754 5040 3014 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:07:754 5040 3014 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:07:754 5040 3014 Misc   = Module: C:\Windows\system32\wucltux.dll
2019-04-02 10:20:07:754 5040 3014 CltUI AU client got new directive = 'Download Approval', serviceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, return = 0
2019-04-02 10:20:07:816 11848 27a0 COMAPI -------------
2019-04-02 10:20:07:816 11848 27a0 COMAPI -- START --  COMAPI: Install [ClientId = wusa]
2019-04-02 10:20:07:816 11848 27a0 COMAPI ---------
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Allow source prompts: Yes; Forced: No; Force quiet: No
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Updates in request: 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - ServiceID = {6A498F13-AD63-44DA-A31F-39ADA0DDC6AF} Third party service
2019-04-02 10:20:07:816  860 1da4 Agent *************
2019-04-02 10:20:07:816  860 1da4 Agent ** START **  Agent: Installing updates [CallerId = wusa]
2019-04-02 10:20:07:816  860 1da4 Agent *********
2019-04-02 10:20:07:816  860 1da4 Agent   * Updates to install = 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI   - Updates to install = 1
2019-04-02 10:20:07:816 11848 27a0 COMAPI <<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]
2019-04-02 10:20:07:816  860 1da4 Agent   *   Title = Security Update for Windows (KB4489878)
2019-04-02 10:20:07:816  860 1da4 Agent   *   UpdateId = {00B91A79-94CE-4E82-BA5F-5E8CE88C0F64}.501
2019-04-02 10:20:07:816  860 1da4 Agent   *     Bundles 1 updates:
2019-04-02 10:20:07:816  860 1da4 Agent   *       {1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E}.501
2019-04-02 10:20:08:362  860 1da4 Agent WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point
2019-04-02 10:20:08:362  860 1da4 Agent WARNING: LoadLibrary failed for srclient.dll with hr:8007007e
2019-04-02 10:20:08:362  860 1da4 Handler Attempting to create remote handler process as MADAP8017\Administrator in session 3
2019-04-02 10:20:08:378  860 1da4 DnldMgr Preparing update for install, updateId = {1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E}.501.
2019-04-02 10:20:08:393 10192 2618 Misc ===========  Logging initialized (build: 7.6.7601.24085, tz: +0100)  ===========
2019-04-02 10:20:08:393 10192 2618 Misc   = Process: C:\Windows\system32\wuauclt.exe
2019-04-02 10:20:08:393 10192 2618 Misc   = Module: C:\Windows\system32\wuaueng.dll
2019-04-02 10:20:08:393 10192 2618 Handler :::::::::::::
2019-04-02 10:20:08:393 10192 2618 Handler :: START ::  Handler: CBS Install
2019-04-02 10:20:08:393 10192 2618 Handler :::::::::
2019-04-02 10:20:08:409 10192 2618 Handler Starting install of CBS update 1F0F864B-6410-41CB-BC6D-A06BEF6AFE7E
2019-04-02 10:20:08:799 10192 2618 Handler CBS package identity: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24385.1.9
2019-04-02 10:20:08:815 10192 2618 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\Windows6.1-KB4489878-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\98fb16fa475dbcd684e862b511a27970\inst
2019-04-02 10:20:13:370  860 195c Report REPORT EVENT: {66649B29-CBDF-4DAA-B3EE-6F969812A173} 2019-04-02 10:20:08:362+0100 1 181 101 {00B91A79-94CE-4E82-BA5F-5E8CE88C0F64} 501 0 wusa Success Content Install Installation Started: Windows successfully started the following update: Security Update for Windows (KB4489878)
2019-04-02 10:20:33:619  860 2bbc AU Getting featured update notifications.  fIncludeDismissed = true
2019-04-02 10:20:33:619  860 2bbc AU No featured updates available.
2019-04-02 10:23:17:309 10192 2790 Handler FATAL: CBS called Error with 0x80070002,
2019-04-02 10:23:21:365 10192 2618 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070002

I wanted to try out a test 2019 WSUS server. Everything seemed to go smoothly, however when I go look at All Computers, I get a system node crash.

I looked at the possibility of it being the same as the bad BIOS name, but I do not seem to see any errors.

The error is as follows:

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, 

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


System.InvalidCastException -- Unable to cast object of type 'System.Guid' to type 'System.String'.

Source
Microsoft.UpdateServices.BaseApi

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchComputers(String computerTargetScopeXml)
   at Microsoft.UpdateServices.Internal.BaseApi.ComputerTarget.SearchComputerTargets(ComputerTargetScope searchScope, UpdateServer updateServer)
   at Microsoft.UpdateServices.UI.AdminApiAccess.ComputerTargetManager.GetComputerTargets(ComputerTargetScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkComputerPropertiesCache.GetAndCacheComputers(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()

Has anyone come across this error before?

Thanks.

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

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

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

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!

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

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

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,

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

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

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

I have server 2012 R2 STDwith 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

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?